Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

cannot use a full or relative URL in a 401 - how to fix this or not have it write

Discussion in 'General Discussion' started by WebHostPro, Dec 10, 2003.

  1. WebHostPro

    WebHostPro Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,651
    Likes Received:
    15
    Trophy Points:
    318
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    Twitter:
    I get thousands of these that just take up space on the apache error file.

    If nothing else it takes disk resource, is there a way to ignore this error or find where the error is to fix it?

    cannot use a full or relative URL in a 401 ErrorDocument directive --- ignoring!

    As you can see it never shows what page/domain is causing the error.

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. perlchild

    perlchild Well-Known Member

    Joined:
    Sep 1, 2002
    Messages:
    279
    Likes Received:
    0
    Trophy Points:
    166
    it means the 401 customerror needs special handling and shouldn't just be treated as a 403 under another name
    the http spec has more details about why the 401 cannot be an absolute path

    http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
    because the 401 error is parth of the auth process, it needs to be more complex(and isn't normally seen by users) they normally see the 403 that happens when they mess up the username, not the 401 that asks them for one... except in very special cases(like wget, I believe, and even then, wget doesn't see the page, just the error code)

    http://httpd.apache.org/docs/mod/core.html#errordocument
    and
    http://httpd.apache.org/docs/custom-error.html
    have more details about errordocuments
     
  3. WebHostPro

    WebHostPro Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,651
    Likes Received:
    15
    Trophy Points:
    318
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    Twitter:
    Is there any way to find the pages causing this error and fix them?

    Maybe a find command or a script?

    Or can I tell apache that it's alright to have this this?

    Thanks, Charles
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. WebHostPro

    WebHostPro Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,651
    Likes Received:
    15
    Trophy Points:
    318
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    Twitter:
    I found it thanks:

    find . -name ".htaccess" -type f -print | xargs grep -e '.*401.*http' /dev/null
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice