While the Body Hash extension addresses the use cases for a request body that is not of type x-www-form-urlencoded, it makes standard multipart/form-data requests difficult in that it requires a hash of the full body in the request. Are there thoughts to addressing this use case by simply allowing the oauth_body_hash parameter to address the value within the boundary?
I would like a user to be able to select a file in a HTML form and input the SHA-1 hash of the file body only and have this request come across according to the spec (hidden inputs would contain the necessary oauth_ parameters). Also, most extensions use the prefix xoauth_ for additional parameters. Should this spec not follow suit? Thanks, ~Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
