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

There's nothing actually "wrong" with the config/directives you've posted, but it seems you don't have a valid SSL cert that covers the www subdomain so you can't redirect from https://www.example.com/ without the user accepting the invalid cert (this is the "error") - which they should never do. When requesting HTTPS, the browser ...


2

There's no magic bullet here, if you are blocking "bad bots" based on the User-Agent string then you need to match on a sufficiently unique substring as to not conflict with other bots and users. But will such an approach unintentionally block good ones as well? Not if you've chosen a sufficiently unique substring to match against. HOWEVER, "...


1

What is "duplicate content"? "Duplicate content" is simply where you have two or more different URLs referencing essentially the same resource and are not canonicalising this in some way (eg. with a rel="canonical" element or external redirect). https://example.com/foo/bar and https://www.example.com/foo/bar are two different ...


1

I don't think this is possible with the two examples you posted since there is no way to "search" for an arbitrary file based on a URL pattern AFAIK, without perhaps using a custom module. However, if your files were named like the following instead, then it's possible to do this using MultiViews (mod_negotiation): 001.some-sort-of-description.html ...


1

Your RewriteRule applied to http://example.org/about/ redirects to http://example.org/var/www/example/public_html/about/.php and result in a 404 Not Found response. /var/www/example/public_html, or something similar, is the absolute path of the directory that contains the files of the website on the server. This type of path shows up because you did not ...


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

This is most certainly due to MultiViews (part of mod_negotiation) being enabled at the shared host. It is disabled by default on Apache (so your directives "work" on your dedicated server), but some shared hosting platforms do explicitly enable this for some reason. (It makes extensionless URLs "just work" out of the box but can ...


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