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

Re: WGLC issue: token68 in p7

From: Manger, James H <James.H.Manger@team.telstra.com>
Date: Thu, 21 Mar 2013 19:36:05 +1100
To: "julian.reschke@gmx.de" <julian.reschke@gmx.de>
CC: "derhoermi@gmx.net" <derhoermi@gmx.net>, "murch@andrew.cmu.edu" <murch@andrew.cmu.edu>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <03C53580-6FFC-43A7-A52D-3C328789C994@team.telstra.com>
NTLM and variants send base64 blobs back and forth: in credentials and challenges.

James Manger

----- Reply message -----
From: "Julian Reschke" <julian.reschke@gmx.de>
Date: Thu, Mar 21, 2013 6:32 pm
Subject: WGLC issue: token68 in p7
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Cc: "Bjoern Hoehrmann" <derhoermi@gmx.net>, "Ken Murchison" <murch@andrew.cmu.edu>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>

On 2013-03-20 01:46, Manger, James H wrote:
> Björn,
> '=' is only allowed at the end to ensure the syntax is unambiguous.
> A token68 value can only be distinguished from an auth-param
> (token = (token / quoted-string)) due to this restriction.
> Let's keep token68 as it is.
> --
> James Manger
> ...

As far as I can tell, if a given scheme always uses token68 (such as the
Basic credentials), it's not necessary to be able to distinguish.

We added token68 for "Basic". Basic only needs token68 for credentials.
Can somebody recall why we added it for challenges as well?

Best regards, Julian
Received on Thursday, 21 March 2013 08:36:42 UTC

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