views:

327

answers:

2

I have a load generator that appends a ASP.NET_SessionId to the Cookie when making a Soap test call from Machine A to Machine B.

Cookie: ASP.NET_SessionId=gf0ouay24sdneiuicpiggn45;

However, when I'm running the soap test hitting my local server it doesn't have an ASP.NET_Session variable in the cookie.

Why is this happening?

UPDATE:

I'm getting this issue now on the server:

Forms authentication failed for the request. Reason: The ticket supplied was invalid.

I've followed this: http://msmvps.com/blogs/omar/archive/2006/08/20/108307.aspx

But to no avail.

A: 

If you're piggybacking on the built-in ASP.NET Session Id, ensure your web app isn't running in cookieless mode. Sessionless pages do not send session ID cookies.

Try explicitly modifying the web.config sessionState element on your local server For example:

<sessionState mode="InProc" cookieless="false"

Explicitly setting this in web.config will override anything from the machine.config file or other web.config files, to ensure the configuration is correct. The reason you want to try this is because MSDN states:

Multiple configuration files, all named Web.config, can appear in multiple directories[..] Each Web.config file applies configuration settings to its own directory and all child directories [..] The root configuration file named systemroot\Microsoft.NET\Framework\versionNumber\CONFIG\Machine.config provides ASP.NET configuration settings for the entire Web server.

John K
A: 

Are you using WCF or ASMX?

Have you monitored the conversation with Fiddler or WireShark to see if the Set-Cookie header is being provided by the server side?

RickNZ
WCF... I am monitoring it. See update.
LB
WCF... yes, it's what I use to see what the request/response is.The SessionId is appended to the cookie when hitting cross servers.. hitting the tests locally do not send the sessionId... why???
LB
Cookies are only sent to the same domains from which they are set. In your local setup, are you seeing a Set-Cookie header from the server before you expect to see a Cookie header from the client? If so, is the Set-Cookie header properly formed?
RickNZ