Compression not working for static Assets
See original GitHub issueCompression not working for Static assets.

Is there a way to enable Fastify Compress to work with Fastify-Static?
Current code:
`fastify.register(require(“fastify-compress”));
fastify.register(require(“fastify-static”), { root: path.join(__dirname, “assets”), prefix: “/assets” // optional: default ‘/’ });`
Thank you.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
IIS static content compression not working - Stack Overflow
1 Answer 1 · 1.Install failed request tracing in add role and feature->Web Server->health and diagnostics->tracing · 2.Open IIS manager->go to ...
Read more >Why is IIS7 not compressing my static files? - Server Fault
In IIS7, click on the site that you are working with. ... Click into it and make sure that you have compression enabled...
Read more >Improve Your Web App Performance By Serving Static Files in ...
Manually Compress Static Files to GZIP After that, you should set up the hosting server to make sure that it will return http...
Read more >Static resource stops working on compression
If I extract and compress again the page fails to load: load application tab, see that it works -> Download file from static...
Read more >Static and dynamic content compression - Progress Software
You can compress responses to requests for static content. This way, when a client requests static content, such as .htm or .txt ,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
nextjs bypass fastify completely and render straight to the http response object. It cannot work with nextjs.
Il giorno mar 13 ago 2019 alle 13:25 Jibin Thomas notifications@github.com ha scritto:
@musdy that will be fixed in the next 1.x release (next week).