Quote:
Originally Posted by AlucardZero
What's this info on forcing people to go to secure connections that you found then?
Also you need to say what version of what HTTP daemon you are trying to configure.
|
I'm finding apache rewrite rulse for directing non https requests to a specific page, like this:
Code:
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.example.com/$1 [R,L]
Would something like this work?
Code:
RewriteCond %{SERVER_PORT} !^443$
RewriteRule (.*) http://www.mydomain.com/$1 [R=301,L]
To clarify, the optimal situation for me would be for users going to
https://www.mysite.com or any address beginning with that to be served the exact same files as a user going to
http://www.mysite.com.
It doesn't need to actually be secure, just allow people to access the site the same as they would through http through https.
Do you think this is possible at all? If not, a rewrite rule that would redirect anyone coming through https to the main site's index page would be good enough. Would the rule above do that?
Sorry, I find apache very confusing.
