aws-amplify / aws-amplify/amplify-hosting

The content-encoding header is missing in response

Open
#2,399 2 comments 2 reactions 0 assignees View on GitHub
custom-headers question
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-console/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [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_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the request for the main JavaScript asset with an accept-encoding header and compare the response headers. Review the related issue 330 for existing context. Done means the response includes the expected content-encoding header when encoding is requested.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.