-
Notifications
You must be signed in to change notification settings - Fork 139
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
How to handle cache in signatures #2134
Comments
Still needs input from the WG to make sure current text is ok. |
@jricher you mentioned that there's already text for this -- can you point to it? |
We've got this paragraph in §5 about Accept-Signature:
But apart from that and an oblique mention of lazy caching in the security considerations, we remain pretty silent about what to do about cache for both request and response. Maybe that's ok, but I want to make sure we don't need to say something more specific. For example:
|
I think the current text works fine; it should be OK for responses to be cacheable as long as that advice is followed. Your questions are a bit malformed -- we can't create special rules for caches regarding signatures, because they're generic software that's already widely deployed. |
OK, closing the issue based on that feedback. |
What should the requirements for cache be in signatures?
See some context:
Originally posted by @jricher in #2105 (comment)
The text was updated successfully, but these errors were encountered: