Plugin Author
AITpro
(@aitpro)
That’s a new one. If your particular Server does not like this format or does not allow “default” then just comment out (put a # sign in front of that line of code) or delete the ErrorDocument 401 default code in your root .htaccess file.
Plugin Author
AITpro
(@aitpro)
Or I guess you could create a 401.html file and change the code to this: ErrorDocument 401 /401.html
it looks like this is specific to LiteSpeed and whatever APVH is.
That line of code is a helper line of code that prevents problems with Directory Password Protection and does not do anything else.
HTTP Status Response 401 Unauthorized
The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP access authentication is explained in “HTTP Authentication: Basic and Digest Access Authentication”
Plugin Author
AITpro
(@aitpro)
Taking a wild guess I assume the acronym APVH stands for A? P? Virtual Host???
the site runs on a shared server, so i guess that’s considered a virtual server
and yes, they do run LightSpeed
i can out the line as you suggested, but then i assume the next update will re-add it… and i’m sure i’ll forget about it 🙂
Plugin Author
AITpro
(@aitpro)
Actually I forgot that a Custom Code text box was created for this section of code so you can add your code modification to BPS Custom Code and it will be saved permanently.
Copy the ErrorDocument section of code to this BPS Custom Code text box: CUSTOM CODE ERROR LOGGING AND TRACKING: Add/Modify Error logging code here
Example:
ErrorDocument 400 /wp-content/plugins/bulletproof-security/400.php
#ErrorDocument 401 default
ErrorDocument 403 /wp-content/plugins/bulletproof-security/403.php
ErrorDocument 404 /404.php
Click the Save Root Custom Code button.
Go to the Security Modes page, click the Create secure.htaccess File AutoMagic button and activate Root folder BulletProof Mode again.
i did as you suggested using the custom code
thanks
