Eran - but that does change anything. That HTML4/HTML5 media type does not specify how to encode parameters into query portion of URIs. I'm not aware of any RFC that describes this name=value pair encoding. So, OAuth draft needs to specify how a client needs to manipulate auth/resource server's URIs to add protocol-specific parameters.
Subbu On Dec 1, 2010, at 2:16 PM, Eran Hammer-Lahav wrote: > The latest reference is: > > http://www.w3.org/TR/html5/association-of-controls-and-forms.html#application-x-www-form-urlencoded-encoding-algorithm > > But that's still a draft. > > EHL > >> -----Original Message----- >> From: oauth-boun...@ietf.org [mailto:oauth-boun...@ietf.org] On Behalf >> Of Subbu Allamaraju >> Sent: Wednesday, December 01, 2010 2:05 PM >> To: OAuth WG >> Subject: [OAUTH-WG] Comment on 'application/x-www-form-urlencoded' >> for URI parameters >> >> Here is some feedback on the use of the 'application/x-www-form- >> urlencoded' media type in the latest drafts (10 or 11). >> >> The draft refers to the 'application/x-www-form-urlencoded' media type for >> encoding parameters into the query component of URIs. For instance, see >> 4.1 in draft 11 has >> >> "In order to direct the end-user's user-agent to the authorization >> server, the client constructs the request URI by adding the following >> parameters to the end-user authorization endpoint URI query component >> using the "application/x-www-form-urlencoded" format as defined by >> [W3C.REC-html401-19991224]" >> >> However, this media type specifies how to encode parameters in the body of >> a representation but not in URIs. In fact use of this encoding for characters >> like spaces will break URIs. >> >> Subbu >> _______________________________________________ >> OAuth mailing list >> OAuth@ietf.org >> https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
