W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Re: p1: HTTP(S) URIs and fragment identifiers

From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
Date: Mon, 22 Apr 2013 17:08:29 +0900
Message-ID: <5174EFFD.8000801@it.aoyama.ac.jp>
To: Zhong Yu <zhong.j.yu@gmail.com>
CC: Mark Nottingham <mnot@mnot.net>, Julian Reschke <julian.reschke@gmx.de>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
On 2013/04/21 1:39, Zhong Yu wrote:
> I like Mark's idea better. In many contexts when people use the term
> HTTP URI they would consider fragment a legit optional part, so the
> spec should not appear to exclude it in general.

This problem was detected for the general case by IRI WG last summer. 
Please see: http://trac.tools.ietf.org/wg/iri/trac/ticket/126.

The IRI WG is now closed, and it is unclear when or whether any of the 
work will be continued/completed. But this is a clear issue that those 
defining URI schemes (anew as the text in the tracker assumes, or also 
just as a spec update as for http and https) have to understand and deal 

 From that issue:

 > 1) Fragment identifiers are part of URIs, and scheme definitions
 > cannot and MUST NOT disallow fragments on specific schemes (even if
 > the usability of a fragment id on the particular scheme being defined
 > seems questionable at the time the scheme definition is made).

 > 2) Fragment identifiers are independent of schemes, depending on MIME
 > media types, and therefore scheme definitions cannot define anything
 > about fragment identifiers.

> On Sat, Apr 20, 2013 at 3:16 AM, Mark Nottingham<mnot@mnot.net>  wrote:
>> On 20/04/2013, at 6:07 PM, Julian Reschke<julian.reschke@gmx.de>  wrote:
>>> On 2013-04-20 09:30, Mark Nottingham wrote:
>>>> On 20/04/2013, at 5:28 PM, Julian Reschke<julian.reschke@gmx.de>  wrote:
>>>>> On 2013-04-20 06:07, Mark Nottingham wrote:
>>>>>> P1 sections 2.7.1 and 2.7.2 define the HTTP and HTTPS URI schemes without fragment identifiers.
>>>>>> While it's true that HTTP sends these URIs without fragids "on the wire" in the request-target, the schemes *do* allow fragids pretty much everywhere else they're used (including some places in HTTP, e.g., the Location header).
>>>>>> Given that this is going to be the definition for these URI schemes, and we already require that the fragid be omitted in the request-target, shouldn't the syntax allow a fragment identifier?
>>>>> No.
>>>>> Fragment identifiers are allowed for *any* URI scheme; the scheme definition doesn't need to include it.
>>>> Then why do we include query?
>>> Because we are defining a<http://greenbytes.de/tech/webdav/rfc3986.html#absolute-uri>.

Because the query is scheme-specific. For people who mostly work with 
HTTP, the query part seem like a sure thing, but there are many schemes 
where query parts are not allowed, and others where query parts have 
very specific protocol implications (e.g. mailto:), whereas in HTTP, 
it's pretty much just "something sent to the server", and details are 
left to client and server internals.

>> But this section *isn't* defining just a single protocol element; it's defining the form of HTTP URIs.
>> I suspect the right thing to do here is to specify that HTTP(s) URIs use the path-abempty form of the hier-part, give some examples, and leave the rest of the ABNF to RFC3986 (or its successors).

That's one way to do it. And of course it has to say that the <scheme> 
part is "http" for http URIs and "https" for https URIs. That's pretty 
obvious to everybody, but we are writing the spec that's nailing this down.

Another alternative is to say that the http-URI and https-URI 
productions correspond to (are concretizations of) the absolute-URI 
production in RFC 3986.

Another solution is to just leave the current text.

But in any of the three above cases (and in particular in the last one), 
it might be very helpful to add a note that of course these schemes can 
take fragments, and point to 
http://tools.ietf.org/html/rfc3986#section-3.5 for details.

If the fragment part is included, then it would be better to rename the 
productions to something like http-URI-reference and 
https-URI-reference, and say that they correspond to URI-reference in 
RFC 3986.

>> At any rate, I don't see the http-uri or https-uri rules actually used anywhere normatively,

Do you mean inside the HTTP spec suite, or have you checked other specs? 
If not the productions then the actual syntax is used VERY widely.

Regards,   Martin.

>> so I *think* this is editorial. I.e., it's on your conscience :)
>> Cheers,
>> --
>> Mark Nottingham   http://www.mnot.net/
Received on Monday, 22 April 2013 08:09:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC