P
Pete
I'm writing a web site for a friend. The site is going to have to
consist of two ASP.NET applications: one running over HTTP and one
over HTTPS. The problem is that the domains will be different, so how
do I maintain state between the public area (http://www.mydomain.com)
and the secure area (https://secure.myisp.com/mydomain)?
What I'm trying to achieve here is for the site user to login to the
site in the secure area, and then have a GUID that identifies the
user's "session" that can be accessed by pages from either
application. When I've done this in the past I've just stored a value
in a cookie, but that's always been on sites where both applications
are on the same domain - that's not the case this time.
Any suggestions?
Any help will be gratefully received.
Pete
consist of two ASP.NET applications: one running over HTTP and one
over HTTPS. The problem is that the domains will be different, so how
do I maintain state between the public area (http://www.mydomain.com)
and the secure area (https://secure.myisp.com/mydomain)?
What I'm trying to achieve here is for the site user to login to the
site in the secure area, and then have a GUID that identifies the
user's "session" that can be accessed by pages from either
application. When I've done this in the past I've just stored a value
in a cookie, but that's always been on sites where both applications
are on the same domain - that's not the case this time.
Any suggestions?
Any help will be gratefully received.
Pete