IE 9 losing session cookie

Using IE 9
User logs into site #1.
Site #1  redirects user to  site#2  using a
URL with  query parameters  ( ASP)  that are all correct.
 Site #2  executes login script, it's all good.
I can see the login happening correctly in profiler.

Site #2 then  rejects user because of no Session variable containing  the user_id.

Yet,  directly logging  in to site #2 with IE 9 works with no problem for the user.  

Same steps above using Chrome,  logged into site #1, then get successfully redirected to site #2.  

IE9 direct login to site #2 works.
Chrome redirect from site # to site #2 works
Only IE9 with redirect from #1 to #2 fails.

Some issue with  IE session sharing?  
Something about a redirect not accepting  session cookie?

Anyone have an idea why IE 9 with redirect fails?

Who is Participating?
awalkintheparkAuthor Commented:
I tried various individual changes with out any luck.
Finally resolved by simply reset of security setting to default.
I don't know what specific setting resolved it.
Hard to say without looking.  Reduce the security on IE and see what happens (or set it all to 'prompt')

If you can grab the HTTP logs (with status codes) of the entire process that would make it a bit easier to tell.

Is it possible to set the cookie on the top-level domain from site#1 (i.e. are #1 and #2  sub-domains of the same parent?)
awalkintheparkAuthor Commented:
Tried reducing security on IE,  turned off Macafee add-on's

Cannot set the cookie from site #1. That's someone else's web server.

We have many users doing this exact thing with out issue.
IEX  -> site#1 to site#2  and so I believe it's a setting somewhere on this users machine.

Tomorrow I can try the looking at the logs.  Will have to get the users IP first.

This implies that session  merging can be disabled:
"One of the best solution for your case is Registry fix for the IE.
Add the following KEY if it is not there, set 0 to disable frame merging.
HKCU\Software\Microsoft\Internet Explorer\Main
DWORD: FrameMerging
Value: 0"

Having user look for this in his registry tomorrow.

The  parent browser pops up a new browser that is logging in.
So the new browser "should" have be starting a new session and have the session cookie.

This "user timing out" issue has always resolved with enabling session cookies in the past.
Which of course  we have tried with this user.  
The fact that directly logging in works  rules out the enable session cookies issue.

Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

Dave BaldwinFixer of ProblemsCommented:
If the domain names of the sites are different, then they will have different session cookies.  It is a pretty strong security rule in all browsers that one domain can not see the cookies of another domain.  Also, a session cookie is active as long as any window of the browser is still open.  Each browser has only one 'cookie jar' that is shared by all windows.

Things like 'in private' browsing are supposed to 'sandbox' the different sites from each other.
awalkintheparkAuthor Commented:
Yes, that's understood.
Still, the problem is that the new browser connects to site#2,  should have a session cookie, but when it's done as a redirect, it fails. Done directly, doesn't fail.
Other browser work when done as a redirect.  
Some IE setting other than "allow session cookies" ?
Dave BaldwinFixer of ProblemsCommented:
I honestly don't think it is working the way you think it is.  Different domains do not share cookies or sessions.  They just don't.  It's against all the security rules that I know of.

"Session cookies" are those with no expiration.  They expire when the browser is closed meaning All browser windows, not just the one where the site was being viewed.  The session cookies for Site #1 and Site #2 are two separate cookies if Site #1 and Site #2 are different domains.  When you open your browser and go to Site #1, it will get a session cookie from Site #1.  It will Not have a session cookie from Site #2 Until it goes to Site #2.
Here's what I think you're saying...

You visit site#1
Site 1 returns a 302 status code, redirecting to
The browser does as it's told, and makes a request to
In Chrome, this will automatically log user 1234 in (or at least recognise them)
In IE9, you see an error message instead

Is that correct ?

Thinking about this, I guess this might qualify as a third-party cookie.
Open Advanced Privacy Settings (Internet Options -> Privacy -> Advanced) and see if that's responsible.
Dave BaldwinFixer of ProblemsCommented:
At least you got it working, that's what counts.
If having "Third party cookies = blocked" ticked in
  Internet Options -> Privacy -> Advanced

causes the problem, and your system is used by a range of users, it might be wise to rework the code a little bit (since some users will have it set this way)
awalkintheparkAuthor Commented:
It worked but true cause not identified.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.