feat: web server compression

[JammingBen]

Description

Adds a compression middleware to the web server to reduce the request size when delivering static files. This speeds up loading times in web clients.

The chi middleware we're using for this currently supports gzip as compression algorithm. We might want to extend this to support br (Brotli) in the future, since it's a newer and more performant algorithm. But for now, any compression is a big step up.

Related Issue

• refs Slow network connection: Load timeout for modules web#7964

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[kulmann]

🚀

[kobergj]

Found this in the docs about Compress middleware:

NOTE: make sure to set the Content-Type header on your response otherwise this middleware will not compress the response body. For ex, in your handler you should set w.Header().Set("Content-Type", http.DetectContentType(yourBody)) or set it manually.

Are we doing this already?

[JammingBen]

Found this in the docs about Compress middleware:

NOTE: make sure to set the Content-Type header on your response otherwise this middleware will not compress the response body. For ex, in your handler you should set w.Header().Set("Content-Type", http.DetectContentType(yourBody)) or set it manually.

Are we doing this already?

Seems to be the case, although I can't tell where exactly this happens (I guess here ?). All responses have a Content-Type header and compression works just fine.

[fschade]

Found this in the docs about Compress middleware:

NOTE: make sure to set the Content-Type header on your response otherwise this middleware will not compress the response body. For ex, in your handler you should set w.Header().Set("Content-Type", http.DetectContentType(yourBody)) or set it manually.

Are we doing this already?

Seems to be the case, although I can't tell where exactly this happens (I guess here ?). All responses have a Content-Type header and compression works just fine.

exactly, all static assets use the assets server, so LGTM