Cookies.txt cookie session overflow results with page not accessable, cookie was sent from




Networking: Cookies
10 years ago
2 years ago


(Reporter: pusher, Unassigned)


1.8 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)




(1 attachment)



10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv: Gecko/20080404 Firefox/
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv: Gecko/20080404 Firefox/

unaware of when it exactly happend, but the cookie was sent to be by aftonbladet
i noticed i was't able to enter the page, i checked with others if they had contact with the site (aftonbladet) so i had to check everything.. i narrowed it down to cookies.. deleted every cookie but aftonbladet.. (kept that cookie) and it kept giving me access problems, so i removed that cookie too.. and then it worked
i kept a backup of that session cookie if you guys are intressted.
How it happend.. i guess the server sends "Cookie: *LOADS of data here* "
and FireFox was't able to handle it.. thats how i figured it happend.

Reproducible: Always

Steps to Reproduce:
1.Start up firefox enter
2. Fail to Access the site

//backup of cookies: (ask for superbuggy_cookies.txt)

Comment 1

10 years ago
Created attachment 318473 [details]
The Cookies file

The cookies file.
Component: Search → Networking: Cookies
Product: Firefox → Core
QA Contact: search → networking.cookies
Version: unspecified → 1.8 Branch
Attachment #318473 - Attachment mime type: application/octet-stream → text/plain
That cookie file didn't cause any problems for me, in Firefox or in IE (after translating the cookie to the right format, of course).

What sort of errors were you getting? It's a pretty long cookie, by itself about a third to half the length at which a lot of servers start returning "500 Internal Error" due to excessive header length. Not long enough on its own to cause that kind of error, but if your client were sending additional long cookies to the same site they might add up to the limit.

Comment 3

10 years ago
did you try to enter when using that cookie file ?
because its trying to load the session of aftonbladet or something when entering the site (swedish newspaper)

so.. iam guessing.. maybe if you change site url.. it will block another site.

i tested the same file on another computer.. caused the same problem..
both times i used FireFox v2.0.0.14 (swedish) but the language by itself shouldt cause the trouble.. iam just adding info.

Comment 4

10 years ago
hey ive googled abit more about the content of the overflow cookie
because i notice its not replicateable everytime.. but it has something todo with the: "net.instadia.clientstep.persist.1" content.. so i googled.. and found some more overflowing cookies.. ex:

COOKIE: net.instadia.clientstep.persist.1=1@321@u/c01f7f1eab5c7f69dfcfee7973300c02e68fea3d&e/0%7C7c012JS%26%26%261198600004%26Fragbite%2520-%2520Anv%25C3%25A4ndarprofil%261198600005%26http%2 users.msgs%261024%26768%2632%261024%26740%26sv-SE%261024%26609%267%26http%253A%252F%252Fwww.fragb***;%20votedOnPoll316 66=1;%20votedOnPoll31055=1;%20votedOnPoll32098=1;% 20votedOnPoll31848=1;%20votedOnPoll32128=1;%20vote dOnPoll31667=1;%20votedOnPoll26990=1;%20votedOnPol l30574=1;%20votedOnPoll31046=1;%20ITXT_TTV=1;%20vo tedOnPoll31892=1;%20votedOnPoll30548=1;%20pass=ee3 10e928d1b*8237543c19e63d24408;%20userID=15*445;%20 timeadjuster=0;%20key=be54e4e2e69462478e*24c6099f0 2281;%20votedOnPoll32080=1;%20__utmz=4941924.11965 15505.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=( none);%20__utma=4941924.1436206423.1196515505.1198 580813.1198598187.49;%20__utmb=4941924;%20__utmc=4 941924;%20net.instadia.clientstep.session.1=1@18@p /1&i/933540690659;%20u_87242=1

something tells me the cookie would overflow firefox..
that content was taken from:
but ive seen it elsewhere... and it was on aftonbladet it happend for me
wich it blocked itself somehow.

Comment 5

10 years ago
I just want to confirm that I have been seeing this issue a couple of times too. Removing the net.instadia.* cookie for the domain "fixes" this temporarily.

I almost instantly saw this issue when trying out a late 3.0beta. I guessed it had something to do with the cookies and when I removed the net.instadia.* cookie the site started to work as normal again. It has then happened a few times more.

I guess this issue could lead users away from the Firefox browser since is one of the biggest sites in Sweden and should "just work".

When I got this issue could not be accessed at all until the cookie was removed. (Tried multiple times from different sessions.)

I have never seen this issue when running FF2.0, only in FF3.0.

I did not take any notes of the actual error shown...

Comment 6

10 years ago
Just to clarify; I have seen this issue in FF3.0 (non-beta) too.
Is this still an issue with recent builds ?
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.