http://wiki.oauth.net/ProblemReporting specifies oauth_problem=version_rejected&oauth_acceptable_versions=1.0-1.0 Simone's examples don't conform to this.
Names in oauth_parameters_absent should be percent encoded first, and then concatenated with &. Simone's example should be transmitted as oauth_problem=parameter_absent&oauth_parameters_absent=oauth_consumer_key %26oauth_nonce (without any line breaks that were inserted by Google Groups). HTTP response codes are specified by OAuth Core http://oauth.net/core/1.0/#http_codes On Mar 2, 8:49 am, Simone Tripodi <[email protected]> wrote: > I've been developing an OAuth SP for a customer and while writing the > Problem Reporting I've been in trouble about the response format: > reading the specification on > > http://wiki.oauth.net/ProblemReporting > > I understood that it should be, for example > > oauth_problem=version_rejected&oauth_acceptable_versions=1.0 > > There are some SP - I mean also Google - that replies in this different > format: > > version_rejected > oauth_acceptable_versions=1.0 > > What should be the right format? > > In the case the first is the official, in the wiki page the > 'oauth_parameters_absent' is described as > > "The parameter named oauth_parameters_absent consists of a set of > parameter names, percent-encoded and separated by '&'." > > So, what's the right operations sequence? First the parameters > concatenation using '&' and then percent-encoding? Otherwise a message > that looks like > > oauth_problem=parameter_absent&oauth_parameters_absent=oauth_consumer_key&oauth_nonce > > should be harder to understad!!! > > it could be nice adding in the wiki page the HTTP error code - > according tohttp://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html > spec - that the SP should be send to the consumer for each problem. > > Are there already been defined? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
