Skip to content

Use raw_query_string to populate QueryStringParameters #483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 23, 2022

Conversation

calavera
Copy link
Contributor

API GW v2 is not compatible with the whatgw specification.
Using the raw query string makes the request behave closer
to the standard.

Signed-off-by: David Calavera [email protected]

Issue #, if available:

Fixes #470

By submitting this pull request

  • I confirm that my contribution is made under the terms of the Apache 2.0 license.
  • I confirm that I've made a best effort attempt to update all relevant documentation.

API GW v2 is not compatible with the whatgw specification.
Using the raw query string makes the request behave closer
to the standard.

Signed-off-by: David Calavera <[email protected]>
@bnusunny
Copy link
Contributor

LGTM

@bnusunny bnusunny merged commit bb34300 into main May 23, 2022
@bnusunny bnusunny deleted the fix_query_parameters_coming_from_apigw_v2 branch May 23, 2022 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

lambda_http::Request should expose a QueryMap from a raw_query_string
2 participants