-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optionally avoid url encoding params #258
Comments
@axelson have you tried doing this approach you mentioned? Cause I'm worried that hackney will also try to url encode :/ |
@edgurgel currently I am inserting the parameter that I need (
Where It appears to be working, I'd just prefer a nicer API if possible. Also I haven't tested it with additional params, but I expect that would work as well (since it would fall under the last condition in the original code snippet I posted). |
This is also relevant when accessing the linkedIN v1 api.
LinkedIN won't register properly if the url is encoded. |
@astjohn here's some more snippets if they're helpful
Where
|
Any idea on this ? I have the same problem (linkedin API). I can not find a solution playing with callbacks. |
Somewhat related to #195 |
Hi is it possible to avoid running
URI.encode_query
on the passed in params?Currently the params are always being run through
URI.encode_query
in https://github.com/edgurgel/httpoison/blob/a4a7877/lib/httpoison/base.ex#L162:I would like to not url-encode one of the params (because I need to avoid url-encoding the
,
character) for a particular API that I am working with. Do I have any alternatives beside runningURI.encode_query
on my other parameters and joining my non-encoded param manually with a&
?The text was updated successfully, but these errors were encountered: