Force a new session in ASP.NET when calling via MSXML2.XMLHTTP

I've got an asp page which calls an aspx page via MSXML2.XMLHTTP and processes the xml which is send back by the aspx page. The problem is that when the aspx page is called, always the same session is used. If two users call the asp page at the same time, the aspx page uses the same session for both users. This is probably because the MSXML2.XMLHTTP object does not support session cookies. Setting a cookie with .setRequestHeader "Cookie", "ASP.NET_SessionId=" & SessionID to link the session of the asp page to the aspx page does not work. The header is ignored by the aspx page, it just uses the same sessionid again. How do I force the aspx page to use a different session each time the aspx page is called?

Background: The aspx page creates an object which uses its own cache object the cache object is stored in the session object. Two or more requests to the aspx page are not allowed to share the same cache object. But they do now because the same session is used.
BreedjAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

iboutchkineCommented:
What if you concatenate SessionID with Session UserID?
0
meet_zorrerCommented:
Hi !

if you can solve the problem of session then cache or any other ASPX technique will not matter

Here is the article from MSDN that gives your answer:
http://msdn.microsoft.com/library/en-us/dnaspp/html/converttoaspnet.asp

Regards
Farrukh
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BreedjAuthor Commented:
I found out the answer myself. I now use the HttpContext.Current.Items instead of HttpContext.Current.Session.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.

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.