MapStaticAssets doesn't work for Content-Encoding "gzip"

[Garios]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I use the default template "Blazor Web App". If I refresh the browser nearly all files will be completly reloaded. Only for a few files (blazor.web.js, favicon.png) I get the 304 - not modified.

I focused on "bootstrap.min.46ein0sx1k.css". The browser requests with header content-encoding='gzip, deflate, br, zstd'. The server response with a gzip-encoded content and adds two 'Etag's to the headers. I looked in BlazorAppNet9.staticwebassets.endpoint.json and found that all variants using 'gzip' have two 'etag's. If I remove the first etag-entry, it works and the server response with an 304 (not modified). I also tried to changed the request-header for getting no gzip-encoded content - this works too.

Expected Behavior

In BlazorAppNet9.staticwebassets.endpoint.json the selector for gzip shouldn't have two 'ETag's.

Steps To Reproduce

• Create a new "Blazor Web App"

  • .NET 9
  • Auth: no
  • configure for https: yes
  • interactive render mode: server
  • interactivity ___location: global
  • include sample pages: yes
  • don't use top-level statements: no
  • enlist int .net aspire orchestration: no

• Start using a browser which requests with content-encoding='gzip'

Exceptions (if any)

No response

.NET Version

9.0.302 (libs are on 9.0.7)

Anything else?

No response

[javiercn]

@Garios thanks for contacting us.

This is expected and by design. In development we disable caching for static assets to ensure there aren't issues with stale files.

If you use "EnableStaticAssetsDevelopmentCaching": true, you should see the caching headers being applied.

[Garios]

I have already come up with this idea, which is why I tried building with Release and without Debugging. Obviously this didn't disables the development-mode. What is responsible for 'development-mode' - ASPNETCORE_ENVIRONMENT": "Development"?

Using "EnableStaticAssetsDevelopmentCaching": true in appsettings.json works in dev-mode.

@javiercn , Thank you for your fast help!!

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.