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
StaticFile.fromFile will return early with a 302 if the resource has not modified since, ignoring the request ETag. If the ETag provided in the If-None-Match header is different from that of the resource, a 302 should not be returned, regardless of the not modified since check.
As far as I understand from the spec, both conditions need to be checked before returning a 302:
If both an entity tag and a Last-Modified value have been
provided by the origin server, SHOULD use both validators in
cache-conditional requests.
This makes more sense if you consider rolling back a file to an older version, where the modification date is taken as when the version was authored, rather than when it was rolled back. Maybe this is unusual, although the above suggests it's covered in the spec and I just encountered it in the wild.
The text was updated successfully, but these errors were encountered:
StaticFile.fromFile will return early with a 302 if the resource has not modified since, ignoring the request ETag. If the ETag provided in the If-None-Match header is different from that of the resource, a 302 should not be returned, regardless of the not modified since check.
As far as I understand from the spec, both conditions need to be checked before returning a 302:
This makes more sense if you consider rolling back a file to an older version, where the modification date is taken as when the version was authored, rather than when it was rolled back. Maybe this is unusual, although the above suggests it's covered in the spec and I just encountered it in the wild.
The text was updated successfully, but these errors were encountered: