I'm working with AWS API Gateway and right now I'm having to alter the Content-Type header manually in order to get my SignatureOnlyEndpoint to validate correctly.

Let me know if I'm using this wrong, but I figured we should be allowing case-insensitive headers here as well.

LGTM

Hi @ngoue, could you please add a commit to retrigger the Travis-CI build ? I open an issue on their supprot because it didn't trigger any builds for your PR. Now they say it is fixed, but it requires another commit/push.

Hi @ngoue, could you please retry again to force-push ? I'm liaising with Travis-CI support team to understand why this is again triggering issues.

Hi @ngoue, it seems Travis CI team is not able to remove you from the "Abuse" list because you have no TravisCI account attached to your github account. I will run the build on locally on my side and if the tests are passing I'll force the merge of this PR.
Stay with me :-)

Build has been run locally due to the TravisCI bug and all tests were passing.

Hahaha interesting... I guess I'll go make a Travis CI account and connect them. Sorry to cause so much trouble!