W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2009

RE: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header

From: Eran Hammer-Lahav <eran@hueniverse.com>
Date: Wed, 9 Dec 2009 10:43:37 -0700
To: Julian Reschke <julian.reschke@gmx.de>
CC: "HTTP Working Group (ietf-http-wg@w3.org)" <ietf-http-wg@w3.org>
Message-ID: <90C41DD21FB7C64BB94121FBBC2E7234378529421C@P3PW5EX1MB01.EX1.SECURESERVER.NET>


> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke@gmx.de]
> Sent: Wednesday, December 09, 2009 9:15 AM
> To: Eran Hammer-Lahav
> Cc: HTTP Working Group (ietf-http-wg@w3.org)
> Subject: Re: Proposed RFC 2617 erratum, Re: Backwards definition of
> authentication header
> 
> Eran Hammer-Lahav wrote:
> >> OK,
> >>
> >> so let's report an erratum against RFC 2617 to get this on the record:
> >>
> >> -- snip --
> >> Section 1.2, paragraph 4:
> >> OLD:
> >>
> >>         challenge   = auth-scheme 1*SP 1#auth-param
> >>
> >> NEW:
> >>
> >>         credentials = basic-credentials | auth-scheme #auth-param
> >
> > Don't you need the 1*SP in there?
> >
> > EHL
> > ...
> 
> Not really, the "#" construct already allows leading linear white space
> (otherwise RFC 2068 would have been incorrect as well :-).

Allows or requires it?

EHL
Received on Wednesday, 9 December 2009 17:45:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:14 GMT