Accept-encoding header parameter is always attached #6045

Depends on which interceptor you are on

Native or Agent you can kill it
the curl relay sets it unconditionally

packages/hoppscotch-desktop/plugin-workspace/relay/src/request.rs:108

self.handle.accept_encoding("")

fix is to add a header named Accept-Encoding and leave the value box empty
libcurl drops its own generated header when you hand it one with nothing after the colon

a header without content (no data on the right side of the colon) as in Accept: removes the internally used header

https://curl.se/libcurl/c/CURLOPT_HTTPHEADER.html

checked against libcurl 8.7.1 with a local listener

curl --compressed -H 'Accept-Encoding: ' http://127.0.0.1:8099/

GET / HTTP/1.1
Host: 127.0.0.1:8099
User-Agent: curl/8.7.1
Accept: */*

nothing on the wire
a real value works too so Accept-Encoding: identity goes out as identity

blank values do reach the relay
only blank keys are filtered packages/hoppscotch-common/src/helpers/utils/EffectiveURL.ts:373
and the relay forwards key and value verbatim packages/hoppscotch-desktop/plugin-workspace/relay/src/header.rs:46

Browser or Extension not possible
Accept-Encoding is a forbidden request header so the browser writes it and ignores yours
https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_request_header

The value you quoted matches what a browser sends rather than what libcurl builds so check which interceptor is selected first