RE: Maintain Session State Across Domains
- From: "Rich" <Rich@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 29 Apr 2005 08:56:05 -0700
To my knowledge, this should not be an issue unless you are linking
application pages accross non-secure (port 80) and secure (port 443) ports on
your webserver. If you are linking between secure and non-secure, the session
var's will not be maintained.
For example, are you collection the session vars on a secure page, directing
to PayPal, and having PayPal redirect to a non-secure page?
Hope this helps... Rich
"Robert Bur*** [eMVP]" wrote:
> Hello All:
>
> I am writing an ASP.NET application that will take the user to PayPal to
> make some payments. Before going to PayPal, I collect relevant user
> information and store it in a session state slot. I'm using InProc session
> state. After the user goes through the paypal site, the session information
> I collected / saved is gone.
>
> Is there a way to maintain state across domains without resorting to
> ugliness like saving the session info to temporary files on the server, etc.?
>
> Robert
>
.
- References:
- Maintain Session State Across Domains
- From: Robert Bur*** [eMVP]
- Maintain Session State Across Domains
- Prev by Date: probably wont get a response on this, tab question
- Next by Date: Re: Error only on production server
- Previous by thread: Maintain Session State Across Domains
- Next by thread: Background processes and session timeout
- Index(es):