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

[DWHS.net]

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

[perlchild]

Originally posted by DWHS.net
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

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/cor...#errordocument
and
http://httpd.apache.org/docs/custom-error.html
have more details about errordocuments

[DWHS.net]

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

[DWHS.net]

I found it thanks:

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