You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following several discussions with @vladgolubev and @dkatavic (see #85 and #75) I think we should have a middleware that makes sure that the headers in the lambda-proxy integration from API Gateway are always exposed in canonical format (dash-separated-camelcasing).
The idea of this middleware would be to go over all the available headers and reconstruct the object with all the keys properly normalized.
Thoughts?
The text was updated successfully, but these errors were encountered:
Following several discussions with @vladgolubev and @dkatavic (see #85 and #75) I think we should have a middleware that makes sure that the headers in the lambda-proxy integration from API Gateway are always exposed in canonical format (dash-separated-camelcasing).
The idea of this middleware would be to go over all the available headers and reconstruct the object with all the keys properly normalized.
Thoughts?
The text was updated successfully, but these errors were encountered: