Thanks for responding, Paul, Carlos and Michael.
Unfortunately, my situation is a catch 22. I will give you more background
to help understand my position.
Here's the current situation:
- homepage is http which leads to an https form-based login page.
Here's what we want to achieve:
- Make the https form-based login page be the actual homepage to eliminate
an extra click-thru with a way to silently redirect to http page in the case
of non-SSL capapble browser.
How do other people deal with this scenario? Is there always an http page
which leads to the https page to cover the possibility that the user is
coming in with non-SSL lynx and at least you could warn them about that on
the http page. Any other way out?
Thanks,
--
Haroon Rafique <[EMAIL PROTECTED]>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
