You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should restangular make the etag it receives a strong etag when it sends it as if-None-Match http header
(i.e strip the W/ from received etag when it uses it as if-None-Match)
MDN says that <etag_value>
may be prefixed by W/ to indicate that the weak comparison algorithm should be used (This is useless with If-None-Match as it only uses that algorithm).
I'm trying to handle weak etags problem with nginx
If I send a weak etag (with W/"<etag>"), nginx will not recognize the etag, and will send 200 OK http response
But If I send it as strong etag (without W/"<etag>") then nginx will respond correctly with 304 Not Modified response
The text was updated successfully, but these errors were encountered:
https://tools.ietf.org/html/rfc7232#section-2.3.2
"Weak comparison: two entity-tags are equivalent if their opaque-tags match character-by-character, regardless of either or both being tagged as "weak"."
Should restangular make the etag it receives a strong etag when it sends it as
if-None-Match
http header(i.e strip the
W/
from received etag when it uses it asif-None-Match
)MDN says that <etag_value>
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/If-None-Match
for more context: https://stackoverflow.com/questions/47995118/nginx-doesnt-match-weak-etags
I'm trying to handle weak etags problem with nginx
If I send a weak etag (with
W/"<etag>"
), nginx will not recognize the etag, and will send200 OK
http responseBut If I send it as strong etag (without
W/"<etag>"
) then nginx will respond correctly with304 Not Modified
responseThe text was updated successfully, but these errors were encountered: