Closed
Bug 783195
Opened 14 years ago
Closed 14 years ago
Cookies causing Problems in Firefox (Shows Network interrupted Error)
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: ganeshsace, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.75 Safari/537.1
Steps to reproduce:
When the cookie size gets Large about 48B I am getting this error.
I am trying to submit a Request with this cookie to the server
Actual results:
Firefox shows Network connection interrupted.
Firebug shows Connection Status as Aborted.
This is very similar to https://bugzilla.mozilla.org/show_bug.cgi?id=510985
Expected results:
The results should be displayed correctly.
After removing the selected cookie the page loads fine without any issues.
Comment 1•14 years ago
|
||
It would know your used Firefox version if you had used it for filing this bug. The selected version (3.5) is unsupported and very old and I guess it's not the right one.
Your report is incomplete.
What are the steps to reproduce ?
Does this also occur with other browsers ?
What makes you think that this is a browser issue and not a server problem ?
With 48B you mean 48Bytes for the whole cookie ?
We are still using Firefox 3.5 as our customers on working on Prism. We use Firefox 3.5 for development and testing. The issue is reproducible in Prism and Firefox. There are huge no of web pages that needs migrating to Firefox 4. (We tried and failed to upgrade to FF4 as some pages started breaking)
Our application does not run on other browsers pretty well so I haven't checked it.
I am pretty sure the request does not hit the server. There are no access logs in the server for this request.
Yes the size of the large cookie giving problems is is 48 Bytes. Once I remove this cookie from the browser application works fine with out issues.
Comment 3•14 years ago
|
||
3.5 support ended on April 28, 2011.
Proposing INVALID as 3.5 is not supported anymore and as there are no indicators provided that the problem still happens in a currently supported version.
Comment 4•14 years ago
|
||
I'm pretty sure that a 48bit cookie is not a general issue even in 3.5.
I can only guess that you hit the http header limit of IIRC 1024bytes.
Are there other additional http headers in the request or other cookies that are send in the same request ?
anyway, i have to mark this report invalid due to the EOL of 3.5
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•