The problem is pipelining turned on. I can't reproduce with pipelining off, with pipelining on i can
Component: Browser-General → Networking: HTTP
Assignee: general → darin
QA Contact: general → httpqa
Status: UNCONFIRMED → NEW
Ever confirmed: true
Pipelining hmmm. Is that feature shared with the other affected Gecko-using browsers? Also, just for my reference, before toggling pipelining did you clear your cache?
Brad: with missing parts I meant what the page source shows, not what the page on the server is like. Pipelining seems to affect the probability of this happening after several tests with clearing cache each time, but I usually have pipelining disabled and I saw the problem when I first loaded the page, so it cannot be the only problem. All current browsers support at least optionally HTTP 1.1 pipelining, not just Gecko-based ones...
For missing parts, the answer is no. A locally saved correctly renedered page (regardless of browser) acceptably passes file comparison (windows: fc, linux: diff) with a badly rendered one. By acceptably, I mean no structural differences and only different sessionID's in the links. Even the whitespace is the same.
Clearing cache gives this error in the JS console: Error: uncaught exception: [Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsICacheService.evictEntries]" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: chrome://communicator/content/pref/pref-cache.js :: prefClearCache :: line 89" data: no] So my testing with and without pipelining (see above) might be worthless... additionally I am using a proxy. Of course I pressed Shift-Reload all the time, but if that works as well as clearing the cache does... :-/ With a new profile clearing cache works. First I loaded the page several times (with and without shift) using HTTP 1.0 to make sure the correctly display version is at the proxy. Then, using a new profile and there using HTTP 1.1 with pipelining, I loaded the page again, had the error; switched off pipelining: no error. However, after re-enabling pipelining, clearing the cache and reloading several times, I coud not reproduce it... weird...
FWIW I a not using a HTTP proxy at all, if that helps any debuggers.
I don't have pipelining enabled, and if I go to the link it looks fine. If I hit the back button and then go forward to the page it happens every single time.
Reporter, this might be fixed in the latest trunk-version, now that bug 282441 is fixed. Can you test again, please ? The fix will be in the forthcoming Firefox1.1 alpha.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.