I think it's meant to be there. If you look at Signature Base String construction, item 9 is a normal "line item" just like all others and should have a newline at the end. So you can think of it as the params as one sting w/ newline between followed by a newline. In the example, it looks like each param is followed by a newline which is not exactly how the spec words it, but it's the same result.
For me, ending the params with a newline results in the same signature values as the spec. What might be unclear is if there should be an empty newline if the query string is empty. Eran? On Feb 13, 2011, at 2:57 AM, Toby White wrote: > * I think there's an error in the parameters normalization example. > > The final output of the normalization algorithm at the end of 3.3.1.1 > is given as: > > a2=r%20b\n > a3=2%20q\n > a3=a\n > b5=%3D%253D\n > c%40=\n > c2=\n > > 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. _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
