The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

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 DWHS.net, Dec 10, 2003.

  1. DWHS.net

    DWHS.net Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,569
    Likes Received:
    6
    Trophy Points:
    38
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    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
     
  2. perlchild

    perlchild Well-Known Member

    Joined:
    Sep 1, 2002
    Messages:
    279
    Likes Received:
    0
    Trophy Points:
    16
    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. DWHS.net

    DWHS.net Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,569
    Likes Received:
    6
    Trophy Points:
    38
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    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
     
  4. DWHS.net

    DWHS.net Well-Known Member
    PartnerNOC

    Joined:
    Jul 28, 2002
    Messages:
    1,569
    Likes Received:
    6
    Trophy Points:
    38
    Location:
    LA, Costa RIca
    cPanel Access Level:
    Root Administrator
    I found it thanks:

    find . -name ".htaccess" -type f -print | xargs grep -e '.*401.*http' /dev/null
     
Loading...

Share This Page