-
Notifications
You must be signed in to change notification settings - Fork 2
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
Service responses are not compressed #6360
Comments
Spike to add reproduction involving |
Ticket description has been updated with the reproductions for |
Assignee to consider next steps. |
I checked, |
Created AWS Support ticket 172005082100601 |
As suggested by AWS Support, a
|
Assignee to resolve issue with AWS Support. |
AWS Support case 172005082100601 resolved with positive feedback. |
The following is a visualization of the relationships between the TF resources involved. Unlabeled arrows represent dependencies expressed via Assignee to verify that, on |
For demo, show that compression is working in all main deployments. |
Demoed on |
We implemented compression as part of #1910, but it appears to have been disabled again:
Note the
accept-encoding
header in the request and the absence of thecontent-encoding
header in the response.prod
reproduction using cURL:anvilprod
reproduction using cURL:The text was updated successfully, but these errors were encountered: