Noticed as part of the v0.29.0 alpha release line that in the projects usingdevServer.proxy configuration, those proxied requests started not returning content anymore.
I dug into the headers a bit and started filtering them out and noticed that the one that fixed was when omitting the content-encoding header
< content-encoding: gzip
Which makes sense, as we are processing the request server side first and returning the full body, so telling the client the response is encoded is probably making it think the browser needs to decode it, when it's not necessary.
Haven't quite pinpointed the exact release this broke on (given some periodic rebasing in the release branch, but it does seem to break on the v0.29.0-alpha.0 release which only had this change - https://github.com/ProjectEvergreen/greenwood/pull/1110
Type of Change
Bug
Summary
Noticed as part of the v0.29.0 alpha release line that in the projects using
devServer.proxy
configuration, those proxied requests started not returning content anymore.An example endpoint trying to be proxied to is - https://www.contributary.community/api/topology
![Screenshot 2023-09-30 at 1 51 52 PM](https://github.com/ProjectEvergreen/greenwood/assets/895923/8acb6769-8a20-4316-8085-08c514227e4e)
Details
Interestingly, I noticed the endpoint worked when using
curl
locally and bypassing the browser entirely.I dug into the headers a bit and started filtering them out and noticed that the one that fixed was when omitting the
content-encoding
headerWhich makes sense, as we are processing the request server side first and returning the full body, so telling the client the response is encoded is probably making it think the browser needs to decode it, when it's not necessary.
Haven't quite pinpointed the exact release this broke on (given some periodic rebasing in the release branch, but it does seem to break on the v0.29.0-alpha.0 release which only had this change - https://github.com/ProjectEvergreen/greenwood/pull/1110