-WG] the format parameter
Another alternative idea -- designate the 'format' param as an accept-header
override. This technique has been successful for the X-Method-Override header
and cements the Accept header syntax as the proper mechanism for selecting
output format.
On Thu, Jun 1
Another alternative idea -- designate the 'format' param as an accept-header
override. This technique has been successful for the X-Method-Override
header and cements the Accept header syntax as the proper mechanism for
selecting output format.
On Thu, Jun 10, 2010 at 10:59 AM, Justin Richer wro
One of the things that I found particularly useful with working with
OAuth1 was the ability to perform an entire transaction through URL
parameter manipulation. This is why I wholly support keeping the client
id and secret fields in the client auth flow and the username and
password fields in the u
I am implementing an OAuth 2 library and the format parameter does not
feel right.
If a client is using a library then the response format should be
totally transparent to the client. The library may have a setting if
the client wants to force a format for whatever reason, but individual
messages
