* Dan Jacobson ([EMAIL PROTECTED]) wrote: > 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)
What do you mean by new request? What's the problem with those headers? Preventing a new request in what context? -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ ------END GEEK CODE BLOCK------
signature.asc
Description: Digital signature
