Closed Bug 80845 Opened 23 years ago Closed 23 years ago

Page returns a Cookie, but status reads "Transferring data from..." forever

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 98
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 39310

People

(Reporter: mdimitrio, Assigned: neeti)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (Win98; U)
BuildID:    2001051004

This link returns this header:

HTTP/1.1 204
Server: Microsoft-IIS/5.0
Date: Tue, 15 May 2001 01:46:53 GMT
Connection: Keep-Alive
Content-Length: 0
Content-Type: text/html
Set-Cookie: Tim=Gray; path=/
Set-Cookie: ASPSESSIONIDGGGGQHNC=GLDMOFLAJHPFDEIHMBGJDMGF; path=/
Cache-control: private

The browser should set the cookie, and it sets the cookie, but never updates the 
status bar, which reads "Transferring data from 216.62.61.218".

If you access the site again, then you'll see "AHA!".

Reproducible: Always
Steps to Reproduce:
1. Go to URL

Actual Results:  The cookie is set fine. Which is good, but status bar doesn't 
change accordingly

Expected Results:  Status bar say: "Document: Done"
> Content-Length: 0

We probably never update because we don't get any data....


Assignee: asa → neeti
Component: Browser-General → Networking: HTTP
QA Contact: doronr → tever
Yes, we get, it's the setting of the cookie. Every other browser tested (IE5.0,
Opera 5.11, NS 4.77) sets the cookie and stops. Mozilla seems to still look for
something (by not updating the status). Although it sets the cookie correctly,
it doesn't seem finished (status bar indicates still working state), so the user
feels he should wait, when he actually doesn't have to.
Oops, sorry, I didn't see the "> Content-lenght".

You're right, there's no content. Mozilla should be prepared to this.
This is a dupe of bug 68811  which in turn is a dupe of bug 39310

*** This bug has been marked as a duplicate of 39310 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Verified dupe.
Status: RESOLVED → VERIFIED
QA Contact: tever → junruh
You need to log in before you can comment on or make changes to this bug.