- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 14 Apr 2010 17:42:16 +0200
- To: Mark Nottingham <mnot@mnot.net>
- CC: HTTP Working Group <ietf-http-wg@w3.org>, =JeffH <Jeff.Hodges@KingsMountain.com>
On 14.04.2010 17:17, Julian Reschke wrote: > ... > The reason for this is that with the currently proposed definition, > "Effective Request Target" is undefined for certain requests, such as > when request-target is "*" or just an authority component. > ... Related to that, <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-09.html#rfc.section.4.1.2> says: - snip - If a proxy receives a request without any path in the request-target and the method specified is capable of supporting the asterisk form of request-target, then the last proxy on the request chain MUST forward the request with "*" as the final request-target. For example, the request OPTIONS http://www.example.org:8001 HTTP/1.1 would be forwarded by the proxy as OPTIONS * HTTP/1.1 Host: www.example.org:8001 after connecting to port 8001 of host "www.example.org". - snip -- But what if the method does not support the asterisk? What is supposed to happen for: GET http://www.example.org:8001 HTTP/1.1 ? Best regards, Julian
Received on Wednesday, 14 April 2010 15:42:55 UTC