Skip to content Skip to sidebar Skip to footer

Why Is Firefox Ignoring Cache Control On Range-based Queries?

Web servers have the ability to stream media (audio in this example) to browsers. Browsers use HTML5 controls to play the media. What I'm discovering, however, is that Firefox is

Solution 1:

Your Firefox is implementing Section 13.8 of rfc2616. So this behavior is alright.

13.8 Errors or Incomplete Response Cache Behavior

A cache that receives an incomplete response (for example, with fewer bytes of data than specified in a Content-Length header) MAY store the response. However, the cache MUST treat this as a partial response. Partial responses MAY be combined as described in section 13.5.4; the result might be a full response or might still be partial. A cache MUST NOT return a partial response to a client without explicitly marking it as such, using the 206 (Partial Content) status code. A cache MUST NOT return a partial response using a status code of 200 (OK).

Partial responses may(or maynot) be stored. So Chrome and Firefox both follow the rules.

Post a Comment for "Why Is Firefox Ignoring Cache Control On Range-based Queries?"