Your message dated Fri, 17 Feb 2006 07:31:00 +0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352141: firefox: can't prevent new request
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: firefox
Version: 1.5.dfsg-1
Severity: wishlist
Tags: upstream
There is no way in Preferences to override the following header
causing a new request to be sent. Javascript on or off. Maybe in
about:config one can toggle it, but I can't tell. Anyway certainly
one couldn't toggle it for certain hosts.
In contrast, lynx and w3m don't make a new request by default.
HTTP/1.0 200 OK
Date: Wed, 08 Feb 2006 00:01:59 GMT
Set-Cookie: PHPSESSID=...
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=ISO-8859-1
Connection: close
Proxy-Connection: close
(http://blog.philkern.de/archives/87-SSH-control-connections.html)
--- End Message ---
--- Begin Message ---
OK, sorry. Maybe firefox is doing the right thing and I'm just unhappy
that I can't make it do the wrong thing. Anyway "if not, then someone
reopen this bug".
--- End Message ---
