-
Notifications
You must be signed in to change notification settings - Fork 8
Add support for content-encoding and compressed response.body #30
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or request
Description
This library fails if a route returns the following headers:
'content-type' => 'application/json; charset=utf-8 and
'content-encoding' => 'gzip',
In this case the response.body is gzipped json.
We need to support compressed response.bodies.
Note: Axios has an existing decompress function that appears to use zlib to automatically inflate compressed response.bodies.
Axios code here:
EDIT: content-encoding is part of the fetch spec so it appears that something is broken in node 18.8-18.9 that is causing this issue somewhere down the line. Close this issue when content-encoding is working again.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request