-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
UNC-99 apigateway accept-encoding header wrong #13350
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
UNC-99 apigateway accept-encoding header wrong #13350
Conversation
Test Results - Preflight, Unit22 282 tests +4 20 530 ✅ +4 16m 7s ⏱️ -44s Results for commit dc23c1a. ± Comparison against base commit 4484dd1. This pull request removes 13 and adds 17 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 4m 6s ⏱️ Results for commit dc23c1a. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 34m 22s ⏱️ - 27m 6s Results for commit dc23c1a. ± Comparison against base commit 4484dd1. This pull request removes 1375 tests.♻️ This comment has been updated with latest results. |
simonrw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the presence and value of this header is not critical - accept-encoding is so standard that presumably nobody worries about the parity of it with AWS. We are more lenient with what we accept so I guess it's not a problem.
LGTM
|
Thanks for the review @simonrw. I will add a bit of clarity as to the issue, since I realise my PR description might not be super explicit. We do wnat to keep those in parity, as it can impact the response encoding from an integration if we modify headers that shouldn't be modified.
This issue is actually a parity with AWS. The headers sent from our testing python client is impacted by the addition of the package in the upstream project. This is why we can't merely update the snapshot here. Since the same package is not installed in this project. I will try to bring a follow up that will bring back an assertion that what is sent by the requests client is what is received by the integration to make sure we don't end up losing parity on that front either. |
Motivation
In upstream projects the
Accept-Encodingcan change due to the presence of thezstandardlibrary. It seems safer for now to skip those.Changes
Skip the header from snapshot when captured
Tests
Related