httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 46615] New: Apache returns 501 on unknown method; can't guarantee this is correct
Date Tue, 27 Jan 2009 23:16:48 GMT

           Summary: Apache returns 501 on unknown method; can't guarantee
                    this is correct
           Product: Apache httpd-2
           Version: 2.2.9
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core

When there is any CGI scripts, or modules loaded, Apache's current behaviour of
returning 501 on an unknown method goes against the definition of the status
code in RFC2616. This is because the server might support the method on some
resource which is accessed by the CGI/module.

To quote the 501 status code definition:

"The server does not support the functionality required to fulfill the request.
This is the appropriate response when the server does not recognize the request
method and is not capable of supporting it for any resource."

While none of this is normative, the latter sentence makes this behaviour
incorrect for Apache. I might have a CGI/module accessed resource which can
support the method, even if Apache itself, serving static files, cannot.

I would suggest using "405 Method Not Allowed", but I realize that this
requires sending an Allow header, which may not be possible.

To re-create: access any resource served by Apache directly (and not via a
module or CGI script) using the method "foo" and view the status code.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message