* Ambrose Li ([EMAIL PROTECTED]) wrote: > Package: iceweasel > Version: 2.0.0.3-1 > Severity: normal > > > This has been a problem for some years already so this is not new. > > After an indeterminate amount of time (usually several days, sometimes shorter > but sometimes longer), firefox/iceweasel will suddenly stop processing 304 > HTTP redirects correctly. It will see the 304, attempt to load the redirected > page, but instead of loading it from the origin server or the configured > proxy, > will (apparently) attempt to load it from the local file system. The result is > this error message: > > File not found > > Iceweasel can't find the file at (path to the page excluding protocol and > server name). > > * Check the file name for capitalization or other typing errors. > * Check to see if the file was moved, renamed or deleted. > > (Try Again) > > (Note: This conclusion is drawn from the following observations: > 1. Both the proxy and the origin server sees and logs the initial request for > the > page; both logs the 304 reply > 2. The error message contains the path to the redirected page, so the browser > sees > the 304 reply with the correct path > 3. However, the origin server does not see (log) any request for the > redirected > page, so the browser has stopped contacting the server after seeing the > 304) > > At this point firefox/iceweasel will respond to reloads as follows: > > - Regular Reload - no effect (continues to display the above error) > > - Shift-Reload - This seems to reset firefox/iceweasel's internal state and > cause it to contact the origin server or configured proxy again
Do you have any recipe to reproduce this? -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6
signature.asc
Description: Digital signature
