Skip to content

Encoded parameters causes failed signature #100

Open
ephracis opened this Issue Nov 19, 2011 · 4 comments

3 participants

@ephracis

Encoded values works fine, but encoded names does not. The OAuth specification seems to allow encoded characters in the parameter names.

Encoded names are needed since Rails expect parameters to have brackets in them. For example when updating the name of a device model one would send out device%5Bname%5D=foo

@andreychernih

+1 on this issue.

@ephracis

I have sent a pull request to the oauth gem which fixes this issue. Hopefully they will include it.

@andreychernih

great! thanks for the heads up, @ephracis

@amritk
amritk commented Nov 11, 2013

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.