- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 30 Oct 2011 09:18:16 +0100
- To: Yutaka OIWA <y.oiwa@aist.go.jp>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2011-10-29 15:54, Yutaka OIWA wrote:
> mostly +1 for requiring generic-parser-compatible syntaxes.
>
> Could you explain what
>
> Note: the fact that "realm" only allows quoted-string syntax was a
> bad design choice not to be repeated in new schemes.
>
> means?
> ...
Rephrasing to...:
Note: the fact that the value syntax for the "realm" parameter is
restricted to quoted-string was a bad design choice not to be
repeated for new parameters.
> I don't think it is a bad idea, as long as ["realm=" token] pattern is
> not valid. (because it is equivalent to use a generic parser first and
> then to require quoted-string as a value.)
> ...
The issue is that - depending on the API - after you have run a generic
parser you simply might not have that kind of information.
It's comparable to require an XML attribute to be quoted with single
quotes, and to disallow double quotes. It can be made to work by
customizing the parser, but why would you want to?
Best regards, Julian
Received on Sunday, 30 October 2011 08:18:52 UTC