On Sat, Aug 27, 2005 at 04:19:45PM +0100, Nick Kew wrote: > >httpd can't predict what methods the resource will accept. > > If it's rejecting a request based on <Limit(Except)>, it can infer > a list of allowed methods from that.
I guess, but there's no knowing the the CGI itself would then accept is what I meant. > >This patch doesn't seem to honour RFC2616, and doesn't add an "Allow:" > >header to the request. It's also specific to a single method. > > > >However, at present I don't think mod_cgi(d) will allow an "Allow:" > >header through from a CGI, so this probably should be fixed, for this > >reason. > > Erm, last time I looked, a CGI script could generate any HTTP headers > it pleases. Not to be confused with the fact that a typical CGI script > generates less than a full HTTP response, so Apache usually has to add > something to what CGI generates. I think we have our wires crossed, I'm mean it's a bug, the "Allow" head isn't being handled correctly. I know what it should do :) I went and tested; #!/bin/sh echo "Allow: GET" echo "Status: 405 Method Not Allowed" and I get; HTTP/1.1 405 Method Not Allowed Date: Sat, 27 Aug 2005 19:35:41 GMT Server: Apache/2.3.0-dev (Unix) mod_ssl/2.3.0-dev OpenSSL/0.9.7e Content-Length: 0 Connection: close Content-Type: text/plain -- Colm MacCárthaigh Public Key: [EMAIL PROTECTED]
