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
I've just discovered the (obvious when you think about it, but not so much when you dig) behavior of fetch implementations regarding Content-Encoding: gzip; etc.: the body is automatically decompressed, unless you specific an implementation-specific option (compress: false in node-fetch, which doesn't seem to work when we tested it by the way).
The behaviour is very useful to us, but I would like to be able to rely on it knowing it's a documented and stable behavior, and couldn't find this documented in the Fetch Standard, where is this documented?
As far as I understand it it's not part of the spec but an implementation-specific feature, right?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello 👋
I've just discovered the (obvious when you think about it, but not so much when you dig) behavior of
fetch
implementations regardingContent-Encoding: gzip; etc.
: the body is automatically decompressed, unless you specific an implementation-specific option (compress: false
in node-fetch, which doesn't seem to work when we tested it by the way).The behaviour is very useful to us, but I would like to be able to rely on it knowing it's a documented and stable behavior, and couldn't find this documented in the Fetch Standard, where is this documented?
As far as I understand it it's not part of the spec but an implementation-specific feature, right?
Beta Was this translation helpful? Give feedback.
All reactions