You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2024. It is now read-only.
When proxying requests with "Accept-Encoding: gzip" header and a gzip encoded response I just get a gibberish response. Btw I'm using the raml1 branch of Osprey.
The interesting part here is, this doesn't happen for all requests.
In the first request I post a product to our endpoint, below you see the console log output of the response inside proxy.js. But first the decoded result:
When proxying requests with "Accept-Encoding: gzip" header and a gzip encoded response I just get a gibberish response. Btw I'm using the raml1 branch of Osprey.
The interesting part here is, this doesn't happen for all requests.
In the first request I post a product to our endpoint, below you see the console log output of the response inside proxy.js. But first the decoded result:
When querying the for this resource I get this gibberish and it looks like it wasn't decoded. Below you also find the log output of the get request:
By disabling the gzip compression. Both request return the same body content. So it seems not directly depend on the content length.
GET
POST:
The text was updated successfully, but these errors were encountered: