If you're stuck with .htaccess, then mod_rewrite is likely your only
recourse.
I would recommend debugging mod_rewrite on your development / staging
server with the rewrite log, too.
Lastly, look up the "http2https" recipe on the httpd wiki.
On Sat, 2 Feb 2019 at 12:51, R. Diez
wrote:
> First o
First of all, thanks for your answer.
[...]
Htaccess is only used for clients on a host server (such as a godaddy.com
website)
where the client does NOT have access to configuration files of the server…
That is exactly my case.
HSTS does not seem suitable either.
I hope someone can help me
As a small side note,
Using an .htaccess file is NOT recommended when a sysadmin has access to the
server. Htaccess is only used for clients on a host server (such as a
godaddy.com website) where the client does NOT have access to configuration
files of the server… Although it DOES work, apache
You’ll want to look into HSTS
https://https.cio.gov/hsts/
Basically it will let the user’s browser know “in advance” to always connect
via HTTPS, eliminating the vulnerability of first connecting to a site over
HTTP before being redirected.
> On Feb 1, 2019, at 8:09 AM, R. Diez wrote:
>
> H
Hi all:
I have very little Apache experience. I just occasionally help with a couple of websites on 2 different hosting companies of the
"inexpensive" variety. I want to automatically redirect from somesite.com to www.somesite.com, and from http to https.
With difficulty, I have managed to put
