The content-encoding header is missing in response

[parth-prajapati-git]

Before opening, please confirm:

• [X] I have checked to see if my question is addressed in the FAQ.
• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting bug reports.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

No response

Region

No response

Amplify Console feature

No response

Describe the bug

When my app request to get the main js asset, The content-encoding header is missing in response even if the accept-encoding header is included in the request.

Same issue https://github.com/aws-amplify/amplify-console/issues/330

Expected behavior

Should get a response with content-encoding header

Reproduction steps

Request for the assets

Build Settings

No response

Additional information

No response

[github-actions[bot]]

Hi :wave:, thanks for opening! While we look into this...

If this issue is related to custom domains, be sure to check the custom domains troubleshooting guide to see if that helps. Also, there is a more general troubleshooting FAQ that may be helpful for other questions.

Lastly, please make sure you've specified the App ID and Region in the issue!

[eaoliver]

This is still broken. There are still no Content-Encoding headers being returned from Amplify. Here's a NextJS demo I have running on Amplify for reference: https://main.d1d4qzybk2342u.amplifyapp.com/