Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Location header in HTTP 409 response does not include treeID #1649

Closed
bobcallaway opened this issue Aug 29, 2023 · 0 comments · Fixed by #1650
Closed

Location header in HTTP 409 response does not include treeID #1649

bobcallaway opened this issue Aug 29, 2023 · 0 comments · Fixed by #1650
Assignees
@bobcallaway
Labels
bug Something isn't working

Comments

@bobcallaway
Copy link
Member

Description

If a duplicate entry is proposed, Rekor returns an HTTP 409 Conflict response with a response header indicating the UUID of the existing entry. Currently we only return the leaf hash, without the shard-specific treeID. This causes inefficient lookups (which have to span all shards).

Version

rekor-server 1.2.2
@bobcallaway bobcallaway added the bug Something isn't working label Aug 29, 2023
@bobcallaway bobcallaway self-assigned this Aug 29, 2023
@bobcallaway bobcallaway mentioned this issue Aug 29, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bobcallaway bobcallaway

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

return full entryID on HTTP 409 responses bobcallaway/rekor
1 participant
@bobcallaway