Turns out Response.sendBytes was calling Response.write, but Response.send was not.
In this case, this meant text responses would not get affected by compression middleware. However, it would still set the Content-Encoding header, breaking the website in browsers.
This PR replaces send implementation with one that calls sendBytes.
Turns out
Response.sendByteswas callingResponse.write, butResponse.sendwas not.In this case, this meant text responses would not get affected by compression middleware. However, it would still set the
Content-Encodingheader, breaking the website in browsers.This PR replaces
sendimplementation with one that callssendBytes.