-
Notifications
You must be signed in to change notification settings - Fork 1
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
RFC 9175 - Request Tag - List or Set? #30
Comments
The server treats each Request Tag as opaque. RFC7252 does refer to "The set of request options that is used for matching the cache entry However, certainly the Uri-Host option has to be calculated in order for the cache-key, so I would be doing the same for any options that are repeated. But, at the end of the day, it is up to the server as to how it builds the cache-key, what matters is that it always does it the same way. |
sure. I also do not assume, that it will be too frequently more than one. |
Should a server distinguish requests with multiple
Request Tag
processing them as list (obey order) or set (no order)?RFC9175 3.3 uses
list
, but I want to ensure, that the interpretation is right.The text was updated successfully, but these errors were encountered: