On Mon, Oct 01, 2007 at 12:05:58AM +0100, Nick Kew wrote:
> RFC2616 is clear that:
> 1. OPTIONS * is allowed.
> 2. OPTIONS can be proxied.
>
> However, it's not clear that OPTIONS * can be proxied,
> given that there's no natural URL representation of it (* != /*).
>
> The Co-Advisor suite has a test case to proxy OPTIONS * using:
>
> OPTIONS * HTTP/1.1\r\n
> Host: [remote target host]\r\n
> \r\n
>
> Unfortunately PR#43519 is obscuring the Co-Advisor test case
> (which purports to be testing our handline of Max-Forwards)
> by returning 403.
>
> It's not at all clear to me whether that syntax should
> be supported. Anyone?
>
I know Roy's already reported the proxy error as bogus, but I think
the OPTIONS * BUGZ report is also bogus. As a test, I assumed that
both www.apache.org and apache.webthing.com are reasonably configured
servers:
$ telnet apache.webthing.com 80
Trying 195.50.92.131...
Connected to www.webthing.com.
Escape character is '^]'.
OPTIONS * HTTP/1.1
Host: apache.webthing.com
HTTP/1.1 200 OK
Date: Mon, 01 Oct 2007 12:58:45 GMT
Server: Apache/2.2.5 (Unix) DAV/2 mod_ssl/2.2.5 OpenSSL/0.9.8a SVN/1.2.3
Allow: GET,HEAD,POST,OPTIONS,TRACE
Content-Length: 0
Content-Type: text/plain; charset=UTF-8
---
$ telnet apache.webthing.com 80
Trying 195.50.92.131...
Connected to www.webthing.com.
Escape character is '^]'.
OPTIONS * HTTP/1.0
HTTP/1.1 200 OK
Date: Mon, 01 Oct 2007 13:01:32 GMT
Server: Apache/2.2.5 (Unix) DAV/2 mod_ssl/2.2.5 OpenSSL/0.9.8a SVN/1.2.3
Allow: GET,HEAD,POST,OPTIONS,TRACE
Content-Length: 0
Connection: close
Content-Type: text/plain; charset=UTF-8
Can anything confirm that OPTIONS * is as hosed as the BUGZ report
claim? I haven't had time to actually trace the internals yet...
