Hot answers tagged

3

I agree with Stephen's comment: HTTPS will not break the QR code itself. There might be some hosting reasons to keep your QR-encoded URL untouched. I guess you may want to avoid any HTTPS issue (old browsers, etc.) with this URL (and its children). Here are Apache directives which, in an .htaccess file, will redirect all requests to HTTPS, except http://(www....


2

Moving to a system using acme (or DNS if your systems have the hooks) and using Letsencrypt will likely the way to go. Certbot makes this easy. Total cost for certs is your time setting it up as a one off - no ongoing costs or manual cert installs and wide acceptance. Letsencrypt/Certbot doing ACME challenges is the way to go, is viable for 1 cert upwards - ...


2

Once you use point the NS (name server) records to Bluehost, Google domains has no way of implementing the redirect. The steps for implementing the redirect are: Add a DNS entry for the host being redirected pointing to the web server that will do the redirect. Configure the web server to redirect requests for that domain to the desired location. Obtain ...


1

Your first code has 2 errors in the RewriteRule directive: ^$ does not capture anything, so $1 is always empty here. A slash is missing before $1, because if it could have captured something like Foo.html, the substitution URL would be of the form https://example.comFoo.html. Your second code seems valid to me, although the RewriteBase directive is useless ...


1

Check your wordpress (or whatever you are using) general settings that the domain is set with https in the editor/admin options.


Only top voted, non community-wiki answers of a minimum length are eligible