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
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
The current ETag caching works well for the public registry; however, some nginx and other load-balancer and proxy implementations might have different behavior, and only respond with a 304 if an if-modified-since header is sent with the request.
The header shoud be created the same way the if-none-match header is currently created, but instead of the cached etag header, it should send the value of the last-modified header.
I believe most browsers currently operate in this fashion as well.
What do you think?
The text was updated successfully, but these errors were encountered:
lxe
changed the title
Add 'if-modified-since' date-based caching and request cache header.
Add 'last-modified'/'if-modified-since' date-based caching.
Nov 25, 2014
The current ETag caching works well for the public registry; however, some nginx and other load-balancer and proxy implementations might have different behavior, and only respond with a 304 if an
if-modified-since
header is sent with the request.The header shoud be created the same way the
if-none-match
header is currently created, but instead of the cachedetag
header, it should send the value of thelast-modified
header.I believe most browsers currently operate in this fashion as well.
What do you think?
The text was updated successfully, but these errors were encountered: