I'm dropping it from MAC.
EHL
> -Original Message-
> From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf
> Of Andrew Wooster
> Sent: Friday, May 20, 2011 8:42 PM
> To: Julian Reschke
> Cc: Kris Selden; OAuth WG
> Subject: Re: [OAUT
On May 19, 2011, at 10:52 AM, Julian Reschke wrote:
> On 2011-05-19 19:47, Kris Selden wrote:
>> I totally missed the error_description in the WWW-Authenticate header in the
>> bearer spec. I'm not sure why the human readable error description is not
>> in the response body on a 401 but I assume
On 2011-05-19 19:47, Kris Selden wrote:
I totally missed the error_description in the WWW-Authenticate header in the
bearer spec. I'm not sure why the human readable error description is not in
the response body on a 401 but I assume there is a reason.
Dunno.
Is what you were proposing onl
I totally missed the error_description in the WWW-Authenticate header in the
bearer spec. I'm not sure why the human readable error description is not in
the response body on a 401 but I assume there is a reason.
Is what you were proposing only apply to error_description when in HTTP headers?
On 2011-05-19 11:14, Kris Selden wrote:
Well, like it or not, the default for HTTP header fields is not UTF-8.
Encoding in HTTP header fields is not the topic, error_description is already
encoded into a URI before it is in the Location field.
There are 3 spots where error_description appears
> Well, like it or not, the default for HTTP header fields is not UTF-8.
Encoding in HTTP header fields is not the topic, error_description is already
encoded into a URI before it is in the Location field.
There are 3 spots where error_description appears:
http://tools.ietf.org/html/draft-ietf-
On 2011-05-19 01:24, Kris Selden wrote:
Is there a problem with sticking to UTF-8? OAuth already mandates JSON which is
Unicode only.
Well, like it or not, the default for HTTP header fields is not UTF-8.
Would be nice to keep it simple.
I'm guessing without guidance, most would convert to
Is there a problem with sticking to UTF-8? OAuth already mandates JSON which is
Unicode only.
Would be nice to keep it simple.
I'm guessing without guidance, most would convert to UTF-8 and percent encode
anyway.
On May 18, 2011, at 1:32 PM, Julian Reschke wrote:
> On 2011-05-18 22:25, Kris S
On 2011-05-18 22:25, Kris Selden wrote:
How about taking a page from URI spec since it is a query parameter value and
follow this for the value of such human readable text params:
When a new URI scheme defines a component that represents textual
data consisting of characters from the Univer
How about taking a page from URI spec since it is a query parameter value and
follow this for the value of such human readable text params:
When a new URI scheme defines a component that represents textual
data consisting of characters from the Universal Character Set [UCS],
the data should
On 2011-05-18 18:20, Eran Hammer-Lahav wrote:
The error_description parameter and similar parameters in the MAC and
Bearer specs do not specify the language or encoding used. This is a
problem. Can someone offer a solution?
For parameters, you can use the encoding defined in RFCs 2231 and 5987.
The error_description parameter and similar parameters in the MAC and Bearer
specs do not specify the language or encoding used. This is a problem. Can
someone offer a solution?
EHL
___
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/lis
12 matches
Mail list logo
