@davidfowl @blowdart any comments on this one? It's pretty straightforward but there's nuance in where in the middleware pipeline it's enabled and enabling compression over HTTPS but not for HTML, to mitigate any security issues stemming from being able to force user content to be compressed over HTTPS.

Funnily enough Javier is doing the same thing as a feature - you should sync with him for his new idea which might mitigate the need to do this in a custom manner. (But generally, no, no concerns for this type of thing as it's static assets)

/azp run