Hi Dmitry, This sounds more something like a subject for dev-tech-network.
Regards, Martijn On 2/18/08, Dmitry Dartz <[EMAIL PROTECTED]> wrote: > Hello all, > > As far as I see, if FireFox has a partial cache for a file and you click on > the link once again, it may request with Range header and server will > respond with HTTP 206 response. It may result in wrong content if file has > been modified since FF got initial content to the cache. > A clear inidiation that file is changed is Last-Modified and/or ETag > headers, but FF ignores (at least Last-Modified) and combines cached content > with new one. In other words it violates this recommendation from RFC2616: > > A cache MUST NOT combine a 206 response with other previously cached > content if the ETag or Last-Modified headers do not match exactly, > see 13.5.4. > > In order to replicate: > You need a web server that does not issue ETag header, only Last-Modified. > Click on a link that leads to a very large file download. > FF will show save as dialog. > Wait for some seconds and close with Cancel. It's enough to get some content > cached. > Change the file content. Start downloading again and complete the download. > Compare what you got with what is on the server. You will see file beginning > from the 1st content (before modification) followed by 2nd content (after > modification). > > > _______________________________________________ > dev-apps-firefox mailing list > [EMAIL PROTECTED] > https://lists.mozilla.org/listinfo/dev-apps-firefox > -- Martijn Wargers - Help Mozilla! http://weblogs.mozillazine.org/qa/ http://wiki.mozilla.org/Mozilla_QA_Community irc://irc.mozilla.org/qa - /nick mw22 _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
