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.

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

2.1.2 Fresh receipts may be requested through the resource identified in the Location header. #21

Open
roywill opened this issue Jul 25, 2024 · 1 comment
Assignees

Comments

@roywill
Copy link

roywill commented Jul 25, 2024

Since this section is talking about registration, why is refresh paradigm left dangling at the end. Is it thought to use this same method to ask for a refresh? I can see getting a new receipt, but that may fail due to the time validity of the signed statement. If you expect it to be based on previous data on the log, then it needs to be indexed based on the previous receipt.

@JAG-UK
Copy link
Contributor

JAG-UK commented Jul 26, 2024

Sounds sensible. Something like '/reissue?receiptid=xyzy

Where 'xyzy' is the durable ID of a receipts that is already included in the log (I'm being deliberately obtuse with the ID format since that's under question in a separate Issue).

Please submit a PR that matches your use case needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants