[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-sw

From: Paul Eggert
Subject: Re: Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-switch
Date: Wed, 25 May 2016 14:51:32 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0

On 05/25/2016 11:51 AM, Clément Pit--Claudel wrote:
Presumably when you did the simple refresh Firefox queried the server to know if a more up-to-date version of the page was available (using the X-Modified-Since header); it should have received a positive answer, but instead received a negative one (that would be the bug).

Yes, in this case the request headers include "Cache-Control: max-age=0" and "If-Modified-Since: |Tue, 24 May 2016 17:50:01 GMT". Firefox is using If-Modified-Since because the HTTP response from debbugs.gnu.org for <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19759> contains a header line "Last-Modified: Tue, 24 May 2016 17:50:01 GMT". This Last-Modified time is the|time that Glenn added Bug#23612 as a blocker for Bug#|19759|. However, that's the wrong time value: the Last-Modified time should be at least Wed, 25 May 2016 17:45:21 GMT, which is when I fixed the blocking bug #23611, as this fix caused a change to the contents of <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19759>.

Doing a hard refresh forces Firefox to bypass its cache; but ideally, debbugs should respond correctly to Firefox' queries and indicate that the page was in fact modified.

Yes, the bug is clearly on the debbugs side here. That being said, the workaround is to use a shift-reload, which causes Firefox to specify "cache-control: no"in its request, which in turn causes debbugs to recalculate the page.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]