Forum Moderators: phranque
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
GET /.well-known/acme-challenge/SDV9AWZOOOUQUCCK67ETOFMCTRS4X4FO HTTP/1.1
NOBODY edits my htaccessSame basic thing is taking place at your server just up a level out of visibility, it's how the cert updates.
Your host provider is running vulnerability checks on your site... On Tuesday you can contact your host provider and verify.I certainly will.
In your raw access log will probably see something like:And I did (from 20 August, I had missed it). Significantly the GET request apparently originated from my site's own IP address, pointing (I think) to my hosting provider as the culprit.
In order for the certificate to automatically update either by your host or the issuing agency, permission is needed via htaccess if on a shared server.I guess that would now apply to me as I recently upgraded my service which now includes auto-updates for the certificate.
The “commands” you quote are Conditions. Are they attached to an existing RewriteRuleYes, for each RewriteRule that I had in my file, the three new conditions were added immediately preceding the rule.
Just how many people have access to your site files?Just me, that I know of, and of course the folks at my hosting provider.
My work is done.In order for the certificate to automatically update either by your host or the issuing agency, permission is needed via htaccess if on a shared server.
I guess that would now apply to me as I recently upgraded my service which now includes auto-updates for the certificate.
Still, I am puzzled by the necessity of inserting the same three new conditions for *every* occurrence of a RewriteRule in my htaccess file.
I would *not* remove any rules or conditions generated by your host.
Still, I am puzzled by the necessity of inserting the same three new conditions for *every* occurrence of a RewriteRule in my htaccess file.
they want to avoidStill, it's overkill. They're saying over and over again
RewriteCond %[REQUEST_URI} !^/dir1/filename.html
RewriteRule ^dir2/othername.html /do-stuff-here [L]
Still, it's overkill. They're saying over and over again
At least 95% of the time, the body of a RewriteRule--the pattern that is first tested--will already exclude the condition.
[edited by: lucy24 at 4:39 am (utc) on Sep 4, 2018]
the server has to waste time and effort evaluating superfluous conditions.
the preceding RewriteCond directives won't fire unless the pattern in the following RewriteRule matches.
Please note that cPanel now automatically updates .htaccess files to exclude DCV checks from HTTP redirections so that the DCV checks complete successfully. This resolves issues that some users reported with AutoSSL and cPanel Market purchases.
