Could consumer software recognize oauth_problem=parameter_duplicated, and react by sending another request without duplicate parameters, without bothering the user? That would be good for the user, and thus a good reason to add parameter_duplicated to the repertoire. But I wonder why the consumer wouldn't send a correct request (without duplicates) to begin with.
Regarding encoding, an example response body would be oauth_problem=parameter_absent &oauth_parameters_absent=oauth_token%26oauth_nonce ... but without the line break. The '&' that separates the absent parameter names is percent-encoded to %26 (like any parameter value). A consumer can parse this easily. On Nov 6, 10:03 am, Paul Walker <pjwal...@gmail.com> wrote: > Um, the consumer would resolve the problem by not sending duplicate > parameters. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
