W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2012

Re: Status Line Syntax production/parsing

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 28 Aug 2012 21:46:34 +0200
Message-ID: <503D201A.3050209@gmx.de>
To: Karl Dubost <karld@opera.com>
CC: Bjoern Hoehrmann <derhoermi@gmx.net>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
On 2012-08-28 21:09, Karl Dubost wrote:
> Bjoern,
>
>
> Le 28 août 2012 à 14:47, Bjoern Hoehrmann a écrit :
>> If you are asking about something like
>>
>>   HTTP/1.1<sp>200<crlf>
>>
>> Without the <sp> after the status code, then no, that is not fine.
>
> Yes, that was my reading too. Thanks for confirming.
> I was wondering if it was intentional, because a meaningful trailing space is likely to create interoperability issues. Though I have nothing to backup that. It might not be a concern at all.
>
> Basically I would have proposed something such as
>
>      status-line = HTTP-version SP status-code (CRLF|SP reason-phrase CRLF)
>
> so handling the case with no trailing space.

Well,

	HTTP-version SP status-code [ SP reason-phrase ] CRLF

On the other hand, a ultra-simple syntax for the first line might sense; 
and there may be code out there relying on it.

Best regards, Julian
Received on Tuesday, 28 August 2012 19:47:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 28 August 2012 19:47:15 GMT