I have a scenario with a VB ASP.NET application where the calling application must send a session identifier in as a Parameter within the URL. I do not have control of the calling legacy applications (which are not web pages but automated server applications).
So for example, it must be similar to:
http://.../Default.aspx?SessionID=12345
It is acceptable that VB generates the initial session ID, but for ongoing responses I must be able to identify them by a Parameter and not the unique URL method that appears default in ASP.NET.
Simplest method appeared to be changing the SessionID on subsequent requests so that it matches up and can access stored variable data.
These systems are on a closed loop so there is no security risk.
Thanks for any/all ideas!