Re: HTTP/HTTPS differentiation (General questions)
Hi,
When SSL -> non-SSL transition occurs, the Client (browser) also treats it as a new session, and won't even send the same request to server again, but will treat it as a new connection.
So, basically in order to achieve this, when the transition occurs, you should provide server with some ID of the user (use QueryString perhaps).
You should try creating an external Session collection for each user, and then when user logs in, create a new entry, let's say IsLoggedIn . Now, when user switches to SSL or non-SSL, you can use QueryString to locate the User in your database, and check your collection if that user is logged in or not.
Hope this helps.
Regards,
Damba
Complete thread:
- HTTP/HTTPS differentiation - amirsky, 2010-03-17, 17:49
- Re: HTTP/HTTPS differentiation - woddrazen, 2010-03-17, 18:12
- Re: HTTP/HTTPS differentiation - amirsky, 2010-03-17, 18:25
- Re: HTTP/HTTPS differentiation - woddrazen, 2010-03-17, 19:14
- Re: HTTP/HTTPS differentiation - amirsky, 2010-03-21, 15:56
- Re: HTTP/HTTPS differentiation - wodDamir, 2010-03-21, 19:20
- Re: HTTP/HTTPS differentiation - amirsky, 2010-03-21, 15:56
- Re: HTTP/HTTPS differentiation - woddrazen, 2010-03-17, 19:14
- Re: HTTP/HTTPS differentiation - amirsky, 2010-03-17, 18:25
- Re: HTTP/HTTPS differentiation - woddrazen, 2010-03-17, 18:12