[AOLSERVER] Custom server error page crash
William Scott Jordan
I've recently added a custom server error message using a redirect in
AOLserver's config file. Since then, I've been occasionally seeing the
following error in the logs:
[09/Jul/2008:18:04:08][30505.1690512][-conn:1-] Error: return: failed to
redirect 'PROPFIND /500.html': exceeded recursion limit of 3
There will be several thousand of those entries in a row, followed by a
server crash. I don't see anything in the logs to indicate what may
have initiated the error in the first place. And the entries continue
even after the server reboots.
At first, I thought there might be an error in the server error page
itself, so I switched it from being a dynamically generated page to
being a static HTML file, which goes through no filtering, but that
didn't solve the problem.
Does anyone have any thoughts on what might be going on?
Thanks!
-Scott
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <list...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Don Baccus
> Hey all!
>
> I've recently added a custom server error message using a redirect
> in AOLserver's config file. Since then, I've been occasionally
> seeing the following error in the logs:
>
> [09/Jul/2008:18:04:08][30505.1690512][-conn:1-] Error: return:
> failed to redirect 'PROPFIND /500.html': exceeded recursion limit of 3
I've seen the exceeded recursion limit error when the server receives
WebDAV operators and no filter is registered to handle them.
There are bots out there that probe sites ...
----
Don Baccus
http://donb.photo.net
http://birdnotes.net
http://openacs.org
Juan José del Río
In the configuration file, you must give the ABSOLUTE path to the error
page. After changing that, restart the server and test it out.
Regards,
Juan José
-
Juan José del Río |
(+34) 616 512 340 | juan...@simpleoption.com
Simple Option S.L.
Tel: (+34) 951 930 122
Fax: (+34) 951 930 122
http://www.simpleoption.com
Fenton, Brian
Exactly how did you add the custom error page?
And do you know what PROPFIND refers to?
Brian
Don Baccus
> Hi Scott,
>
> Exactly how did you add the custom error page?
>
> And do you know what PROPFIND refers to?
As I said earlier, probing by WebDAV ops causes this error ... and
googling PROPFIND yields, unsurprisingly:
The WebDAVPROPFIND Method retrieves properties for a resource
identified by the request Uniform Resource Identifier (URI). The
PROPFIND Method can be used on collection and property resources.
4.01 didn't die with this. 4.10 + does AFAIK
Tom Jackson
that could be part of the problem. Also, does /500.html exist?
Do you have any other debugging turned on? What other handlers do you
have setup?
tom jackson
On Wed, 2008-07-09 at 19:15 -0700, William Scott Jordan wrote:
Don Baccus
> Is anything registered to handle the PROPFIND method? I'm just
> guessing
> that could be part of the problem. Also, does /500.html exist?
The problem comes about when *nothing* is registered for these
methods. I've known this for quite a long time but have never tried
tracking it down internally within AOLserver.
Be nice if someone wanted to do that ...
William Scott Jordan
registered to handle the PROPFIND method. And yes, 500.html exists as a
plain HTML file.
So how would we register something for the PROPFIND method? Would it be
something like:
ns_register_proc PROPFIND /500.html something
...where "something" points to a TCL proc? It sounds like there isn't a
way to point directly to a static HTML file for PROPFIND requests. Is
that correct?
-Scott
Tom Jackson
method.
I would use a filter, since it can fire very early in the request cycle.
proc ::reject_propfind { what why } {
return filter_$what
}
ns_register_filter preauth PROPFIND /* ::reject_propfind return
ns_register_filter trace PROPFIND /* ::reject_propfind break
tom jackson
William Scott Jordan
Yup, that seemed to do the trick.
Thanks!
-Scott