Hi all,

This is a PSA that we have made a minor change to how opaque responses are
stored in cache_storage.  This change shipped in M96.

The spec requires that we reject a cache.put() that would store a response
with a status code of 206.  This status code refers to partial responses
from a range request.

The spec, however, only does this for non-opaque responses.  We were
previously incorrectly rejecting opaque 206 responses in this situation as
well.

The main risk for this change is that sites may accidentally store partial
responses when previously they could not.  This risk seems small, however,
since sites already cannot tell if they are storing a 404 or 500 error for
an opaque response either.  There is generally no way for a site to know if
an opaque response is valid or not.  This is a big downside to opaque
responses, but not a new one.

Please let me know if there are questions or concerns about this change.

Thank you.

Ben

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK7rkMhMN1tiB7k5evG6FirJuU%2BSkrMrZ2VjyNDFwAxdSx4%3D6Q%40mail.gmail.com.

Reply via email to