Bug#352141: firefox: can't prevent new request

2006-02-12 Thread Eric Dorland
tags 352141 moreinfo thanks * Philipp Kern ([EMAIL PROTECTED]) wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Dan Jacobson wrote: > > Browsing a page with those headers causes a new HTTP request (as shown > > by wwwoffle logs here offline) to the server for the page to be sent. > >

Bug#352141: firefox: can't prevent new request

2006-02-12 Thread Dan Jacobson
[ Phil: http://bugs.debian.org/352141 ] E> What do you mean by new request? What's the problem with those E> headers? Preventing a new request in what context? Browsing a page with those headers causes a new HTTP request (as shown by wwwoffle logs here offline) to the server for the page to be sen

Bug#352141: firefox: can't prevent new request

2006-02-12 Thread Philipp Kern
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Jacobson wrote: > Browsing a page with those headers causes a new HTTP request (as shown > by wwwoffle logs here offline) to the server for the page to be sent. > Whereas, with lynx and w3m no new request is sent. Even with > javascript turned off,

Bug#352141: firefox: can't prevent new request

2006-02-09 Thread Eric Dorland
* 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 ca

Bug#352141: firefox: can't prevent new request

2006-02-09 Thread Dan Jacobson
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 cer