Closed
Bug 156142
Opened 22 years ago
Closed 22 years ago
Web page rendering slows to a crawl.
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 146884
People
(Reporter: GregBorter, Assigned: darin.moz)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530 BuildID: 2002053012 I read that if I check marked the Enable Piplining in Preferences, Advanced, HTTP networking that it would speed up the display of web pages. If I try to load the URL listed above with Enable Piplining check marked the page rendering slows down to a crawl. If I deselect the Enable Pipelining, close the browser, and restart it with a fresh session the above URL displays normally. When I go to this web page the lock icon on the bottom right hand side of the screen always displays a normal, locked status. Reproducible: Always Steps to Reproduce: 1.Check and uncheck Enable Piplining in Preferences, Advanced, HTTP networking. 2. Close and restart browser. 3. Try to load the above URL. Actual Results: Web page rendering slows down to a crawl when Enable Pipelining is check marked. Expected Results: Screen should display at normal speed. I have a plain vanilla Mozilla installation on a fully patched Windows 98 SE OS installation on an Athalon class PC.
Comment 1•22 years ago
|
||
I noticed the same issue too, trying to access this URL: https://www.mac.com/WebObjects/iLogin.woa/wa/loginISWO1001001SOSeSaqKzTqImAIFNWL?aff=consumer&cty=US&lang=en I'm beginning to think it's a general problem with https for Mozilla. I was using Build 2002052918 on Mac OS X 10.1.5. I was able to get the same link to open much faster on IE, either Mac or Windows. (I haven't set up Mozilla on my Windows system yet.)
Reporter | ||
Comment 2•22 years ago
|
||
I tried the link and IE displays it about twice as fast as Mozilla.
*** This bug has been marked as a duplicate of 146884 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•