A
Axel
Hi
I am trying to redirect from some (login) pages from https to http by
using >>Response.Redirect<< but it seems to always end up on https pages
anyway. The only way I get the users back to http is by them clicking on
my (explicit) links but I want to drop them back to http as soon as they
are logged in.
The other way around (http to https) works fine. What could cause such a
behavior? Maybe some global switch in global.asa? Or cookies set by the
secure page? Its really weird.
I am considering doing the redirect client side but I don't want the
whole page to load and then to the redirect as its slooow. OTOH I am
scared of cutting the page short server site in case the client redirect
method fails (e.g. due to ignoring javascript or meta headers). Is there
a sure fire way to redirect to non-secure after successful login?
thanks in advance
Axel
I am trying to redirect from some (login) pages from https to http by
using >>Response.Redirect<< but it seems to always end up on https pages
anyway. The only way I get the users back to http is by them clicking on
my (explicit) links but I want to drop them back to http as soon as they
are logged in.
The other way around (http to https) works fine. What could cause such a
behavior? Maybe some global switch in global.asa? Or cookies set by the
secure page? Its really weird.
I am considering doing the redirect client side but I don't want the
whole page to load and then to the redirect as its slooow. OTOH I am
scared of cutting the page short server site in case the client redirect
method fails (e.g. due to ignoring javascript or meta headers). Is there
a sure fire way to redirect to non-secure after successful login?
thanks in advance
Axel