Bug 22991 - Login sessions are not working
Summary: Login sessions are not working
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.5
: P2 Major
Assignee: Nobody
URL: http://facebook.com/
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-25 00:54 PST by George Marshall
Modified: 2008-12-28 22:36 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George Marshall 2008-12-25 00:54:25 PST
For a few of the resent nightly builds there has been an issue with PHP sessions. I can confirm that this exists in revision 39469 of the nightly build. I am also on a MacBook Pro (4,1) OS X 10.5.6.

When logging into a PHP powered website such as http://facebook.com/ I'm consistently having to re-authenticate with the site after any action such as viewing a picture or a users profile page. This is not a intended functionality of the site nor does this occur when using Safari 3.2.

I have found this to also happen on http://digg.com/ but has not been as reproducible as the facebook bug.

I am also using the following Safari plugins, which are all current versions.
Glims
Safari AdBlock
1Password
Comment 1 Alexey Proskuryakov 2008-12-25 05:48:55 PST
Please verify if this happens without any Safari enhancers.

This functionality (cookies) isn't actually in WebKit, but in lower level system frameworks, so it's quite surprising that a nightly has a different behavior, and I suspect a bug in one of those "enhancers".
Comment 2 Mr Dana Rich 2008-12-28 14:49:19 PST
I too was having this problem, also most notably with Facebook, but I eventually traced it down to the Safari Adblock plugin, try removing that. 
Comment 3 George Marshall 2008-12-28 16:38:33 PST
So I figured out the root cause behind the issue, I went through and removed a few 3rd party plugins. The main two I removed was google gears since it didn't work and Flip4Mac. As the prior post suggest I did remove Safari AdBlock but then reinstalled it to see if it cause issues which it did not.

After me thinking I found the real culprit to be Adium when using it to login into facebook chat services. I was oblivious to this due to the fact I always leave Adium open in the background not thinking about it. Once I closed Adium the problems had disappeared. I've also found this to occur in Safari 3.2.

As a side note this problem does not occur in firefox when I do have Adium open, which is odd because as soon as I login into the site via another source it deauths the last place that was signed in. I guess what it really comes down to is what Adium uses for its back end for facebook of which I am unsure of at the moment. I'm going to do a little more research and file a bug with Adium about the issue and to find out if Adium does WebCore or not. If my assumption is correct there would be no deauths because WebCore shares cookies and other such information between applications that use it such as in the sense if I login to a site via Safari I can then goto the site in WebKit and be logged in already.
Comment 4 George Marshall 2008-12-28 16:47:31 PST
I've found the bug listed in the adium bug tracker so I am listing it here for reference.

http://trac.adiumx.com/ticket/11473

I think the only reason this issue has come about is because facebook changed something on their back end within the past 2 weeks because this issue has never happened until recently.

(In reply to comment #3)
> So I figured out the root cause behind the issue, I went through and removed a
> few 3rd party plugins. The main two I removed was google gears since it didn't
> work and Flip4Mac. As the prior post suggest I did remove Safari AdBlock but
> then reinstalled it to see if it cause issues which it did not.
> 
> After me thinking I found the real culprit to be Adium when using it to login
> into facebook chat services. I was oblivious to this due to the fact I always
> leave Adium open in the background not thinking about it. Once I closed Adium
> the problems had disappeared. I've also found this to occur in Safari 3.2.
> 
> As a side note this problem does not occur in firefox when I do have Adium
> open, which is odd because as soon as I login into the site via another source
> it deauths the last place that was signed in. I guess what it really comes down
> to is what Adium uses for its back end for facebook of which I am unsure of at
> the moment. I'm going to do a little more research and file a bug with Adium
> about the issue and to find out if Adium does WebCore or not. If my assumption
> is correct there would be no deauths because WebCore shares cookies and other
> such information between applications that use it such as in the sense if I
> login to a site via Safari I can then goto the site in WebKit and be logged in
> already.
> 

Comment 5 Mr Dana Rich 2008-12-28 20:52:08 PST
I don't know if I buy this solution though. I still experience the issue and I do not use Adium for FB-Chat, I have even closed adium just incase.

Obviously I was wrong about adblock causing the issue, but now I am beginning to suspect that it is Glims, as I too have that installed.
Comment 6 Mr Dana Rich 2008-12-28 20:53:20 PST
I'm sorry, it's clearly not glims either,

(In reply to comment #5)
> I don't know if I buy this solution though. I still experience the issue and I
> do not use Adium for FB-Chat, I have even closed adium just incase.
> 
> Obviously I was wrong about adblock causing the issue, but now I am beginning
> to suspect that it is Glims, as I too have that installed.
> 
Comment 7 George Marshall 2008-12-28 22:36:49 PST
Reading through the apple forums this issue has been tracked down to the OS X 10.5.6 update. The only resolution to the problem thus far is to reinstall safari and it seems to solve the issue.

http://apple.com/safari