Found the problem, and I wanted to send out a warning to those of you who
might be in a similar situation.  Many of the urls on our site are
registered procs, and we registered them to handle only GET requests, not
knowing about HEAD requests.  So when a browser does a conditional get of
your content, and the request comes across as a HEAD request, and the user
gets a not found response.

What made the situation worse in our case was that our 404 page was itself
a registered proc with the same problem (only handling GET requests) ...

-T

On Fri, 31 May 2002 21:41:17 -0400, Todd Volkert <[EMAIL PROTECTED]> wrote:

>Has anyone ran into problems with AOLServer's handling of HEAD http
>requests?  We're getting the following error every time a HEAD request
>comes through:
>
>Error: return: failed to redirect '404': exceeded recursion limit of 3
>(While serving HEAD / HTTP/1.0)
>
>Thanks,
>-T
>
>AOLServer 3.4 / Linux

Reply via email to