Yep. I should not write ABNF after a day of editing.
EHL
On Jul 12, 2010, at 1:39, "Michael D Adams" wrote:
> On Sun, Jul 11, 2010 at 8:19 PM, Eran Hammer-Lahav
> wrote:
>> My bad. I forgot to update the ABNF for the parameters.
>>
>> credentials= "OAuth" RWS access-token RWS [ 1#aut
On Sun, Jul 11, 2010 at 8:19 PM, Eran Hammer-Lahav wrote:
> My bad. I forgot to update the ABNF for the parameters.
>
> credentials = "OAuth" RWS access-token RWS [ 1#auth-param ]
Thanks. I suppose it should be
credentials= "OAuth" RWS access-token [ RWS 1#auth-param ]
which I'll add t
.org [mailto:oauth-boun...@ietf.org] On Behalf Of Eran
Hammer-Lahav
Sent: Monday, 12 July 2010 1:19 PM
To: m...@automattic.com; OAuth WG
Subject: Re: [OAUTH-WG] Authorization Header Format in draft-10
My bad. I forgot to update the ABNF for the parameters.
The right answer is 2 in the ex
mes Manger
-Original Message-
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of Eran
Hammer-Lahav
Sent: Monday, 12 July 2010 1:19 PM
To: m...@automattic.com; OAuth WG
Subject: Re: [OAUTH-WG] Authorization Header Format in draft-10
My bad. I forgot to update the ABNF for the
My bad. I forgot to update the ABNF for the parameters.
The right answer is 2 in the example below and the correct ABNF is:
credentials= "OAuth" RWS access-token RWS [ 1#auth-param ]
access-token = 1*( quoted-char / <"> )
quoted-char= "!" / "#" / "$" / "%" / "&" / "'" / "("
According to section 5.1.1, commas, equal signs, and quotation marks
are all allowed in the access-token. How do I parse the following
Authorization header?
Authorization: OAuth vF9dft4qmT,foo="bar"
1. The access-token is 'vF9dft4qmT', and the value of some extension
parameter 'foo' is 'bar'.
2.
