Title: Unsupported ErrorDocument URL
Last modified: August 21, 2016

---

# Unsupported ErrorDocument URL

 *  Resolved [atomizer](https://wordpress.org/support/users/atomizer/)
 * (@atomizer)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/unsupported-errordocument-url/)
 * Unsupported ErrorDocument URL: default, must start with ‘/’ or ‘http’
 * seeing the above in my logs – this is from BPS setting in .htaccess…
    ErrorDocument
   401 default
 * [https://wordpress.org/plugins/bulletproof-security/](https://wordpress.org/plugins/bulletproof-security/)

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/unsupported-errordocument-url/#post-4582033)
 * 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](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/unsupported-errordocument-url/#post-4582038)
 * 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](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/unsupported-errordocument-url/#post-4582040)
 * Taking a wild guess I assume the acronym APVH stands for A? P? Virtual Host???
 *  Thread Starter [atomizer](https://wordpress.org/support/users/atomizer/)
 * (@atomizer)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/unsupported-errordocument-url/#post-4582048)
 * 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](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/unsupported-errordocument-url/#post-4582049)
 * 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.
 *  Thread Starter [atomizer](https://wordpress.org/support/users/atomizer/)
 * (@atomizer)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/unsupported-errordocument-url/#post-4582175)
 * i did as you suggested using the custom code
    thanks

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Unsupported ErrorDocument URL’ is closed to new replies.

 * ![](https://ps.w.org/bulletproof-security/assets/icon-128x128.png?rev=1731938)
 * [BulletProof Security](https://wordpress.org/plugins/bulletproof-security/)
 * [Support Threads](https://wordpress.org/support/plugin/bulletproof-security/)
 * [Active Topics](https://wordpress.org/support/plugin/bulletproof-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bulletproof-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bulletproof-security/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [atomizer](https://wordpress.org/support/users/atomizer/)
 * Last activity: [12 years, 4 months ago](https://wordpress.org/support/topic/unsupported-errordocument-url/#post-4582175)
 * Status: resolved