- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 14 Apr 2010 17:17:07 +0200
- To: Mark Nottingham <mnot@mnot.net>
- CC: HTTP Working Group <ietf-http-wg@w3.org>, =JeffH <Jeff.Hodges@KingsMountain.com>
On 13.04.2010 16:41, Julian Reschke wrote: > ... > Here's proposed text for the definition of "Effective Request URI", with > questions inlined: > ... I did some more work, and started to consider how this effects Part 2 (see <http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/196/i196.2.diff>). As expected, it works well for "Identifying the Resource Associated with a Representation" (<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-09.html#rfc.section.6.1>). However, in general it's not as easy as simply replacing "request-target" by "Effective Request URI". 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. Should we re-consider this, mapping the request OPTIONS * HTTP/1.1 Host: example.org to the Effective Request URI http://example.org (note no trailing slash)? Best regards, Julian
Received on Wednesday, 14 April 2010 15:17:50 UTC