In my mind, the simplest normalized request string has one line for each
name=value query parameter. If there are no parameters, there are no lines. The
confusion in the current text seems due to some new line chars coming from
section 3.3.1 and others from 3.3.1.1. It would be better for latter to return
a sorted array of name=value strings, and the former to output them one pair
per line.
My suggested text:
3.3.1. Normalized Request String
...
9. Each query parameter from the HTTP request URI
(each on its own line name=value\n),
after being normalized and sorted
as described in section 3.3.1.1
3.3.1.1. Parameters Normalization
...
[drop step 4 "...sorted parameters are concatenated..."
...
[drop the last 2 paragraphs, after the "Sorted" table.
This part of the example is already repeated at the
end of section 3.3.1. anyway.]
--
James Manger
-----Original Message-----
From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf Of
William Mills
Sent: Tuesday, 15 February 2011 3:42 AM
To: Eran Hammer-Lahav; Toby White; OAuth Mailing List
Subject: Re: [OAUTH-WG] Queries on draft-hammer-oauth-v2-mac-token-02
> > but I don't think the final newline should be there. By my reading of the
> > description of the algorithm, there's no reason for the final newline to be
> > appended - and if it should be appended, then the Normalized Request
> > String example at the end of 3.3.1 ought to end with *two* newlines, since
> > each of the HTTP request elements should be followed by a newline
> > character.
>
> Each of the 9 items is new-line terminated, even if empty. In 3.3.1.1,
> the new-line is a separator so that part does not end with a new-line.
> I'll clarify this.
>
> EHL
Perhaps an explicit example would help make it lear?
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
