Added claims field to authorizer requestContext for lambdaProxyContex…

[ppasmanik]

…t populated with decoded payload from JWT token if Authorization header is spedified to allow testing lambda logic that is based on claims from the token

This pull request addresses issue #264

[dherault]

Thank you for your PR, please consider #304

[dherault]

Thank you for your contribution! v3.16.0

[fubar]

Thanks for this!

@ppasmanik The authorization header check is case-sensitive (it requires "Authorization") and does not kick in when a lower-case header ("authorization") is present. Both are valid as per HTTP specs and the various HTTP client libraries out there use either variation.

In the spirit of making local environments as similar to production as possible, my expectation was that unauthenticated requests would be blocked in the same way that API Gateway does. I don't currently have the time to contribute here, but thought I'd share my thoughts anyways.

[horyd]

I am having this problem now as mentioned by @fubar, I'm unable for some reason to get that header into title case, it is always being sent in lowercase and as such is not being picked up. The PR #295 seems to be looking at this same concern by with regards to content-type.

Either way, created #376 as this is currently a blocker for me