On 2016-05-25 14:23, Paul Eggert wrote:
> On 05/24/2016 09:47 AM, Paul Eggert wrote:
>> this question should be resolvable easily the next time you fix a blocking bug, by trying out Firefox on the bug in question.
> 
> I just now tested this with Firefox and it worked as I expected. I closed Bug#23612 (a blocking bug) and then visited this web page:
> 
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19759
> 
> Firefox showed the bug as still blocking. I refreshed the web page by left-clicking with the mouse on the refresh icon just to the right of the URL in the menu bar. Firefox still showed the bug as blocking. I then did a shift-left-click on the same icon (a full refresh). Firefox updated the web page properly.
> 
> So, a full-refresh appears to be enough to work around the problem, at least for me (Firefox, Fedora 23 x86-64).

Doesn't this indicate a bug in debbugs?

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).

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.

Or am I misunderstanding something?
Clément.