-
Notifications
You must be signed in to change notification settings - Fork 51
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
ETags marked as weak may be the same across different content encodings #109
Comments
Thanks for the report. It's a good question. I've raised this for discussion in the HTTPbis WG - see http://www.w3.org/mid/7D2A809E-F3E0-4128-AFEA-8EEEBF3AC26E@mnot.net Based on that, I'll make changes here as necessary. |
Isn't this the same as #113? |
Probably, although if I am not mistaken I filed this one first. I think
On 10/29/2012 11:04 AM, Nicolás Alvarez wrote:
|
When an ETag is marked weak with "W/", it need not change across different content encodings. "Weak" means the entity is semantically equivalent but not bit-equivalent. But Redbot complains that it doesn't change with different content encodings.
The text was updated successfully, but these errors were encountered: