Safari keeps logging me out...

I have had this problem ever since the update. I log into my websites and within 10 mins I am logged out and have to keep logging back in.

Anyone else have this problem?

I am using Leopard 10.6.3... Safari 4.0.5... Macbook Pro.

Help!?!?!

Mac OS X (10.6.3)

Posted on Apr 5, 2010 2:42 AM

Reply
242 replies

Sep 13, 2010 1:49 PM in response to rushproject

rushproject, you're correct. The session cookie drop problem is completely different and not related to the 4096 byte cookie header limit. The cookie header limit believe it or not was added to work around poorly implemented networking hardware (such as proxies or cheap load-balancer hardware) as well as many webapps written with the Twisted framework for Python that go belly up when a header exceeds 4k. This is likely due to RAM constraints.

In any case, I should certainly hope that google analytics changes it's tack because they're just wasting bandwidth right now (at 4k per resource load). They could just as easily have a 16 byte number that would allow for tracking of a user and that would save them bandwidth by two orders of magnitude. I can't possibly imagine why someone would want to store 4k of data in an HTTP cookie. Imagine if you had to spend 10 minutes explaining who you were to every single person you met on the street. Only a small fraction of those people care about you and where you've been, to the rest it's just wasteful.

Sep 13, 2010 3:47 PM in response to NP Complete

NP Complete wrote:
rushproject, you're correct. The session cookie drop problem is completely different and not related to the 4096 byte cookie header limit. The cookie header limit believe it or not was added to work around poorly implemented networking hardware (such as proxies or cheap load-balancer hardware) as well as many webapps written with the Twisted framework for Python that go belly up when a header exceeds 4k. This is likely due to RAM constraints.




Not sure that I follow your logic here: the Python applications and web sites behind poorly implemented hardware will go belly up either way, be it corrupt (due to stripped out cookies) headers or their inability to process the 4K+ cookie headers. So, you do not add safety or value here while hit hard the majority of web sites that handle "forbidden" headers without any problems. All in all, Safari users are victims of attempt to save some Python apps and users of noncompliant hardware.

I see no wisdom here...

In any case, I should certainly hope that google analytics changes it's tack because they're just wasting bandwidth right now (at 4k per resource load). They could just as easily have a 16 byte number that would allow for tracking of a user and that would save them bandwidth by two orders of magnitude. I can't possibly imagine why someone would want to store 4k of data in an HTTP cookie. Imagine if you had to spend 10 minutes explaining who you were to every single person you met on the street. Only a small fraction of those people care about you and where you've been, to the rest it's just wasteful.


Hmm. I do not buy it. I used 56K modem for the last time more than 10 years ago. Now I use 25Mbit per second Verizon FiOS connection and it takes about 1.25 milliseconds to transmit these 4Kb. Even on my iPhone with 3G internet and incredible expensive bandwidth (especially in tethering mode), I believe that bandwidth wasting talks are nothing, but waste of time

Anyway, this is just my humble opinion. If Apple is in crusade against bandwidth wasting and for the "green internet", be it so :o) I believe that most Safari users experience random logouts due to random drops of session cookies, which do not relate to 4096 problem. Just let me know if you need any assistance in reproducing the session cookie issue. The latest 5.0.2 release still does not include the fix for the 6 months old problem...

Sep 21, 2010 6:36 AM in response to Whatsup97

Hey everybody, looks like this is a long-standing issue, going back to April 2010. Now up to 12 pages of comment, Q&A, possible solutions, testing, etc. And still no fix.

I began noticing this same problem a few weeks ago, following a System-and-Safari update. Noticed I was being unexpectedly logged out of multiple web sites, always in tabs (my normal way of web browsing) sometimes logged out of multiple sites simultaneously. One site in particular I was being logged out of reliably every 100 pages viewed. At other sites, logged out spontaneously even after just one or two pages viewed after logging in.

Since I upgraded to Mac OS X v10.6.4 and Safari v5.0.2 both at the same time, I don't know if the problem is caused by system or browser. But it appears to be a long-standing issue with as yet no solution, just lousy workarounds (frequently emptying cache, clearing cookies, etc.)

It appears to me that Safari is dropping undated session cookies prematurely. Undated cookies should be retained at least until the Safari application is intentionally Quit by user. Other posts in this thread also point to an issue Safari may be having with parsing cookies containing commas.

Can anybody here at Apple let us know if this issue is being actively investigated by Apple engineers, in search of a source of the problem and a good solution? Four months is a long time for a serious problem like this to go unsolved. How many people do you suppose have abandoned Safari because of this, without understanding the problem well enough to describe it here in the forums?

I will repost this message at the top of the Safari/Mac forum topic, in hopes it gets greater attention from Apple engineers.

- Tame

Nov 11, 2010 4:46 PM in response to JJakucyk

Amazingly, 10.6.5 seems to have solved the issue for me as well. FINALLY! I've been using Safari all day to test it out, and no premature logouts so far.

The stars on pages on Top Sites seems to be a little better than it was, though still not exactly accurate. Honestly, that's the least of my concerns with Safari.

Speaking of Safari running better, has anyone else noticed it seems more responsive and snappier than before? I'm glad this bug seems to have been ironed out. I missed using Safari as my go-to browser.

Now if I can figure out how to get Safari to go full-screen, I'll be a happy camper. Why did they remove the feature in the tool bar?

Dec 18, 2010 11:21 AM in response to krisgrant

I was having this issue on my iMac, but not on my MacBook Pro. Typically, when Safari is having issues, it is a Plug-in problem. However, I did the usual checks just to be sure - made sure OSX and Safari had the newest updates, cleared cache, etc. - but the problem still persisted. I then uninstalled my VideoBox Plug-in, and the problem was solved.

Now, I know this is not necessarily a legitimate, permanent fix if you have many plug-ins installed and use them all. However, if you only have a few and don't use them (or can get by without using any) then it should work.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Safari keeps logging me out...

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.