Is anyone aware of a gzip Ring middleware that produces Transfer-Encoding
headers rather than Content-Encoding
? The latter comes with a whole bag of consequences (e.g. for validity of ETag
headers) but all middlewares I could find so far use it for some reason...
OK some further research suggests that many clients don't implement Transfer-Encoding: gzip
😕
Makes these middlewares kinda hard to use properly with ETag
. Oh well.