9: invalid cookie supplied Unknown status code: 9

Well, there was something strange going on and I'm assuming it was with Apple's server(s) because while I was having the problem, I kept seeing the "connecting to" followed by "daw.apple.com" on the status line (bottom) of Firefow. And, there was absolutely nothing showing in the address box at the top. Normally, that changes to "https://discussions.....etc..." right after you hit return/enter. But it remained blank even with the cookie error.

I didn't start troubleshooting (deleting cookies etc) until after about 10 minutes of no response whatsoever. At one point, I even checked to make sure I was actually online by going to a different site - that worked.

I had the same problem logging in, for a while. Server problem for sure.

Hello babowa, (and others)

I'm not sure why, but from 22 to 24 May I was having this problem and this (for whatever reason) fixed it for me:

Re: 9: invalid cookie supplied Unknown status code: 9

May 24, 2011 9:37 AM ( in response to buz)

Experimenting. FWIW I never log out 'specifically' - I'll Quit Safari or whatever.

So I'm signed in and the invalid cookie is back in the list. I delete the cookie. I sign out. I Quit Safari. Relaunch Safari. Go to apple.com/support and click the Communities link. I sign in no problem. I sign out. I bookmark the page I'm signed out to (Main ASC page). Restart Safari. Use my bookmark and sign in .... no problem .... myacinfo INVALID cookie nowhere, for that matter there isn't a myacinfo cookie at all.

Hope I'm not hallucinating again. 😉

EDIT ... Yup, seems to be fixed. I even quit Safari without signing out, relaunched, used the bookmark .... np .... still no myacinfo cookie.

Have had zero issue since.

Ronda Wilson wrote:

In my opinion, the cookie dumping, the cache clearing is all for nought. You'd just as well find a book of spells and start casting them; it would do as much good.

I agree. I had no problems signing in when the supposedly bad/invalid cookie was present & on the few occasions I had any problems, none of the suggested fixes made any difference. The issues are most likely caused by server side problems, ISP caching issues, etc.

I don't agree.

As I already wrote in my previous post (see May 23, where I tracked the discussions.apple.com cookies in both cases) when I could not sign in I consistently had the INVALID cookie, and removing it allowed me to sign in; instead there is no INVALID cookie whenever signing in works...

So in my experience there is a strict relationship between the INVALID cookie and the ability to sign in.

Still it is not clear to me why sometimes the problem occurs and in other cases it does not.

BTW the last weeks I had no problems at all (not even now)

Piero

(the problem occurs in 10.5.8, not in 10.6.x, and using Safari 5.0.5)

That invalid cookie has shown up for many of us in 10.6.x.

Just waiting awhile to try to login again has been sufficient for me, whether you agree with that or not.

When this topic was started, I checked my cookies. I had the myacinfo cookie with a value of INVALID, yet I had no trouble signing in & never saw the error message. I tried deleting the cookie but back then every time I signed in the cookie was set once again. At some point that behavior changed & the cookie was no longer set if it wasn't already present, but at no time did its presence or absence ever affected my ability to sign in.

I don't know what to make of this, other than it doesn't seem that the cookie's presence or its value of INVALID is, by itself, sufficient to trigger the error message.

OK, the case is trickier than I thought...

Piero

I could use my old forum software login bookmark after the software change over. Two or three weeks ago this link stopped working. I created a new bookmark in TenFourFox to the signin page. The new bookmark works when I use it.

Now that I think of it, I have had to "refresh" some of my other links when the went "west".

Robert

I think Apple changed the logout time out to something between 47 [ still logged in ] minutes & 63 minutes [ logged out ] .

I been testing with one window logged in to the forums. I refreshed the session at the above times.

Robert

I think Apple changed the logout time out to something between 47 [ still logged in ] minutes & 63 minutes [ logged out ] .

I had wondered if that was the case, Robert. I've been getting more symptoms of server sync troubles in recent times. ("Faux" sign outs which are resolved by refreshing the page.) Those had stopped after the login restrictions had been brought in, but had been creeping back lately.

b noir wrote:

I think Apple changed the logout time out to something between 47 [ still logged in ] minutes & 63 minutes [ logged out ] .

I had wondered if that was the case, Robert. I've been getting more symptoms of server sync troubles in recent times. ("Faux" sign outs which are resolved by refreshing the page.) Those had stopped after the login restrictions had been brought in, but had been creeping back lately.

That's a good observation. I run with multiple tabs opened. When one tab goes kaput, I trash the tab window & go on. Now that I think more about it, I observed the "forum is down message" ( when other windows were working), and pages never loading in some tabs but other tabs working. This happened on Thursday & Friday of last week for me. I have also observed that when picture upload fails, the forums crash soon after. Happened to me twice.

Apple could be experiencing load problems & took the drastic step of reducing session length. Of course, that don't work for me. The slow response time forces me to run more sessions to get any work done. In the old forum, I mostly ran with one session.

It seems for me, I get the best results running one window into the forums with five or six tabbed windows.

Robert

We can dispose of two birds with one stone… Improve performan and reduce clutter.

How useful are these dynamic side bars? Are they worth the price?

Apple Support Communities > Using Apple Support Communities > Discussions

9: invalid cookie supplied Unknown status code: 9

rccharles wrote:

The slow response time forces me to run more sessions to get any work done. In the old forum, I mostly ran with one session.

AFAIK, you can't run multiple sessions concurrently unless you use multiple browser apps with separate cookie files since sessions are defined by the "JSESSIONID" cookie value.

Great to see Apple still hasn't fixed this problem after a month. Well done.