- From: Mike Burrows <asplake@freenetname.co.uk>
- Date: Thu, 21 Jan 2010 16:01:25 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Apps Discuss <discuss@apps.ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
- Message-ID: <7a2269961001210701t15ea51cdmf48cc696282c44b6@mail.gmail.com>
Hi Julian (and all), Which made have a closer look at existing parameters (sorry for not bringing > this up earlier): > > | ( "type" "=" type-name "/" subtype-name ) > > I believe this *definitively* needs quoting, as "/" is a separator > character in HTTP and thus can not appear in a token. > But is 'type-name "/" subtype-name' a token? I didn't interpret as such - in fact I assumed (perhaps erroneously) that it was in fact two tokens separated by "/". Regards, Mike 2010/1/21 Julian Reschke <julian.reschke@gmx.de> > Hi, > > a few comments regarding quoting of link parameters: > > <http://tools.ietf.org/html/draft-nottingham-http-link-header-07#section-5> > defines the new parameters: > > | ( "hreflang" "=" Language-Tag ) > | ( "media" "=" ( MediaDesc | <"> MediaDesc <"> ) ) > > "hreflang" and "media", so quoting is allowed for media, but it's not for > hreflang. I think it's correct that valid language tags never require > quoting, but I'm not sure that disallowing quoting is the right thing to do > here. > > Which made have a closer look at existing parameters (sorry for not > bringing this up earlier): > > | ( "type" "=" type-name "/" subtype-name ) > > I believe this *definitively* needs quoting, as "/" is a separator > character in HTTP and thus can not appear in a token. > > Also, as this spec uses the RFC 2616 ABNF, we probably need to duplicate > the statement from < > http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.3.7>: > > "...Linear white space (LWS) MUST NOT be used between the type and subtype, > ..." > > Best regards, Julian > > > > > > > >
Received on Thursday, 21 January 2010 15:02:00 UTC