encoding newlines in attribute values

[Rowan Kerr]

On 18-Apr-07, at 9:47 PM, Johnny Bufu wrote:
> The core spec doesn't allow newline characters ("\n") in any openid.*
> values. Currently, Attribute Exchange doesn't specify a way to encode
> newlines in attribute values.

Every indirect OpenID message would seem to be already url-encoded by  
the browser, or server as post data .. so "\n" => %0A (i.e.  
application/x-www-form-urlencoded mime type)

Do we need a pre-url-encode encoding, or can we rely on browsers to  
do the right thing... I suppose it's helpful to spell it out for non- 
browser agents that want to pass OpenID messages.

If we want to define sending binary data in OpenID messages, maybe we  
should leverage multipart/form-data.