Add proxy response type - #7
Open
Athius wants to merge 6 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the gateway to the newer Lambda and HTTP client/server dependency stack, adds
configurable upstream response decoding, and refreshes the project documentation.
Changes
aws_lambda_events,base64,hyper, andreqwesthyper1.x APIs--response-type/RESPONSE_TYPEwith support for:auto(default)proxyv2proxyandv2modes for callers that want to force a formatREADME.mdwith the new runtime options and Docker examplesAGENTS.mdcontributor guidelines for this repositoryNotes
automode currently treats responses with a top-levelcookiesfield asApiGatewayV2httpResponsecookiesare decoded asApiGatewayProxyResponseTesting
cargo fmt --all -- --checkcargo checkcargo testcargo clippy -- -D warnings