Change Content-Type header key to properly parse json response#50
Change Content-Type header key to properly parse json response#50mationorato wants to merge 1 commit intoueberauth:masterfrom
Conversation
|
This shouldn't be the case since everything suppose to be normalized to downcased version. Could share more information and ideally create a unit test to prove such situation? |
|
Hey! Yes, I must admit that this looks weird to me too, specially since It is not the first time I'm using this library for a project, but the Not sure it is easy to setup a test on this, But i can share a demo of whats going on in a few hours. |
|
in fact, nothing is being converted to lowercase here: |
|
HTTPoison ... this is old code ... |
|
I just ran into this same error: It looks like the latest code here on GitHub has not yet been pushed to Hex. Specifically, this line in the current Hex package still uses Or could it be something else? 🤔 |
Oh sorry, the hex package it actually up date with this repo. Permalink I shared is from @mationorato 's fork branch used in this very PR. But changing |
Hey, I found an error that was causing the callback response not to be properly decoded.
It seems that the Twitter API changes the
content-typeresponse header toContent-Type. Causing the callback request handling to fail at detecting when was needed to decode the response body from json.