aws-amplify / aws-amplify/amplify-hosting
Some gzip files are not served for blazor wasm project
- 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-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/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
d3drcnfa1b1cqc
### Region
eu-west-1
### Amplify Hosting feature
Performance
### Describe the bug
Hello,
I'm trying to host a blazor wasm project using amplify connected to github.
I followed this guide https://aws.amazon.com/fr/blogs/devops/deploy-net-blazor-webassembly-application-to-aws-amplify/
The gzip files and brotli files are well generated by the build command `dotnet publish -c Release -o release` but when deployed by Amplify only .js and .css are served with content-enconding to gzip.


### Expected behavior
All gzip files should be served
### Reproduction steps
1. Create a new blazor wasm project
2. Deploy using using amplify hosting
3. Open the web site with the network tab active
or
Open this url with network tab active: https://main.d3drcnfa1b1cqc.amplifyapp.com
### Build Settings
```yaml
version: 1
applications:
- frontend:
phases:
preBuild:
commands:
- curl -sSL https://dot.net/v1/dotnet-install.sh > dotnet-install.sh
- chmod +x *.sh
- ./dotnet-install.sh -c 6.0 -InstallDir ./dotnet6
- ./dotnet6/dotnet --version
build:
commands:
- ./dotnet6/dotnet publish -c Release -o release
artifacts:
baseDirectory: /release/wwwroot
files:
- '**/*'
cache:
paths: []
```
### Additional information
Thanks for your help
Contributor guide
Research direction
Reproduce the issue with a new Blazor WebAssembly project using the provided amplify.yml build settings and inspect the deployed site in the browser network tab. Compare the generated gzip and brotli files from `dotnet publish -c Release -o release` with the resources served by the Amplify app; done means all expected gzip files are served with gzip content encoding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- cloud, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100