starred/Proxyman
1
0
Fork 0
mirror of https://github.com/ProxymanApp/Proxyman.git synced 2026-04-27 09:05:54 +03:00
Code Issues 1.2k Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #1670] "Copy as" cURL omits "accept-encoding" header #1662

New issue
Closed
opened 2026-03-03 19:53:16 +03:00 by kerem · 12 comments
kerem commented 2026-03-03 19:53:16 +03:00
Owner
Copy link

Originally created by @seidnerj on GitHub (Jun 7, 2023).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1670

Originally assigned to: @NghiaTranUIT on GitHub.

Description

"Copy cURL" omits "accept-encoding" header

Steps to Reproduce

(test using HTTP v1.1)

  1. Record a request that has the accept-encoding header present
  2. "Copy cURL"

Current Behavior

cURL command does not contain the "accept-encoding" header

Expected Behavior

cURL command should include all headers

Environment

  • App version: ProxyMan 4.8.0
  • macOS version: macOS Ventura v13.4
Originally created by @seidnerj on GitHub (Jun 7, 2023). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1670 Originally assigned to: @NghiaTranUIT on GitHub. ## Description "Copy cURL" omits "accept-encoding" header ## Steps to Reproduce (test using HTTP v1.1) 1. Record a request that has the accept-encoding header present 2. "Copy cURL" ## Current Behavior cURL command does not contain the "accept-encoding" header ## Expected Behavior cURL command should include all headers ## Environment - App version: ProxyMan 4.8.0 - macOS version: macOS Ventura v13.4
kerem 2026-03-03 19:53:16 +03:00
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@seidnerj commented on GitHub (Jun 7, 2023):

Also, potentially related issue (which might be related to some other issues I'm seeing): when running a cURL request through Proxyman to a URL that returns a gzip encoded response, the response is returned unencoded, but when not specifying Proxyman as a proxy server to cURL, you get binary output.

Here is an example. The next command returns unencoded output:

curl 'https://www.amazon.com/gp/aw/c' \
-H 'Host: www.amazon.com' \
-H 'user-agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5} like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148' \
-H 'accept-language: en-US,en;q=0.9' \
--cookie 'x-main="4Z1Mzz53uzeMicHDK1GT0lSGil5f2Hx29rWundALnER8uCukLfK1ep0@Si2H1mVZ"' \
--proxy http://localhost:9090

<!doctype html><html lang="en-us" class="a-no-js a-touch ....

Whereas this (simply omitting the proxy), returns binary output:

curl 'https://www.amazon.com/gp/aw/c' \
-H 'Host: www.amazon.com' \
-H 'user-agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5} like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148' \
-H 'accept-language: en-US,en;q=0.9' \
--cookie 'x-main="4Z1Mzz53uzeMicHDK1GT0lSGil5f2Hx29rWundALnER8uCukLfK1ep0@Si2H1mVZ"'

Warning: Binary output can mess up your terminal. Use "--output -" to tell 
Warning: curl to output it to your terminal anyway, or consider "--output 
Warning: <FILE>" to save to a file.

I am using the following version of cURL:

~ ❯❯❯ /usr/bin/curl --version                                                                                                                                                            ✘ 2 
curl 7.88.1 (x86_64-apple-darwin22.0) libcurl/7.88.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.11 nghttp2/1.51.0
Release-Date: 2023-02-20
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS GSS-API HSTS HTTP2 HTTPS-proxy IPv6 Kerberos Largefile libz MultiSSL NTLM NTLM_WB SPNEGO SSL threadsafe UnixSockets
<!-- gh-comment-id:1581135531 --> @seidnerj commented on GitHub (Jun 7, 2023): Also, potentially related issue (which might be related to some other issues I'm seeing): when running a cURL request through Proxyman to a URL that returns a gzip encoded response, the response is returned unencoded, but when not specifying Proxyman as a proxy server to cURL, you get binary output. Here is an example. The next command returns unencoded output: ``` curl 'https://www.amazon.com/gp/aw/c' \ -H 'Host: www.amazon.com' \ -H 'user-agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5} like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148' \ -H 'accept-language: en-US,en;q=0.9' \ --cookie 'x-main="4Z1Mzz53uzeMicHDK1GT0lSGil5f2Hx29rWundALnER8uCukLfK1ep0@Si2H1mVZ"' \ --proxy http://localhost:9090 ``` `<!doctype html><html lang="en-us" class="a-no-js a-touch ....` Whereas this (simply omitting the proxy), returns binary output: ``` curl 'https://www.amazon.com/gp/aw/c' \ -H 'Host: www.amazon.com' \ -H 'user-agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5} like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148' \ -H 'accept-language: en-US,en;q=0.9' \ --cookie 'x-main="4Z1Mzz53uzeMicHDK1GT0lSGil5f2Hx29rWundALnER8uCukLfK1ep0@Si2H1mVZ"' ``` ``` Warning: Binary output can mess up your terminal. Use "--output -" to tell Warning: curl to output it to your terminal anyway, or consider "--output Warning: <FILE>" to save to a file. ``` I am using the following version of cURL: ``` ~ ❯❯❯ /usr/bin/curl --version ✘ 2 curl 7.88.1 (x86_64-apple-darwin22.0) libcurl/7.88.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.11 nghttp2/1.51.0 Release-Date: 2023-02-20 Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: alt-svc AsynchDNS GSS-API HSTS HTTP2 HTTPS-proxy IPv6 Kerberos Largefile libz MultiSSL NTLM NTLM_WB SPNEGO SSL threadsafe UnixSockets ```
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@seidnerj commented on GitHub (Jun 7, 2023):

More info on the above, this is the difference between the request going through Proxyman and the one that does not.

Through Proxyman:

   Trying 127.0.0.1:9090...
* Connected to localhost (127.0.0.1) port 9090 (#0)
* allocate connect buffer
* Establish HTTP proxy tunnel to www.amazon.com:443
> CONNECT www.amazon.com:443 HTTP/1.1
> Host: www.amazon.com:443
> User-Agent: curl/7.88.1
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 200 Connection Established
< Content-Length: 0
* Ignoring Content-Length in CONNECT 200 response
< 
* CONNECT phase completed
* CONNECT tunnel established, response 200
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
* ALPN: server did not agree on a protocol. Uses default.
* Server certificate:
*  subject: C=US; L=Wilmington; O=Proxyman LLC; CN=www.amazon.com; ST=Delaware
*  start date: Jun  7 12:23:02 2023 GMT
*  expire date: Jul  8 12:23:02 2024 GMT
*  subjectAltName: host "www.amazon.com" matched cert's "www.amazon.com"
*  issuer: C=US; L=Wilmington; O=Proxyman LLC; CN=Proxyman CA (19 Apr 2023, macbook-pro-16.local); OU=https://proxyman.io; ST=Delaware
*  SSL certificate verify ok.
* using HTTP/1.x
> GET /gp/aw/c HTTP/1.1
> Host: www.amazon.com
> Accept: */*
> Cookie: at-main=Atza|IwEBIKV4oEO6QN6tXrkQ0nW5XQgCy-fHn_EUgIn4IsuTMSMqIDU_f...."
> User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5} like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
> Accept-Language: en-US,en;q=0.9
> 
< HTTP/1.1 200 OK
< Accept-CH-Lifetime: 86400
< Accept-CH: ect,rtt,downlink,device-memory,sec-ch-device-memory,viewport-width,sec-ch-viewport-width,dpr,sec-ch-dpr
< Cache-Control: no-cache, no-store, must-revalidate, max-age=0
< Connection: keep-alive
< Content-Language: en-US
< content-security-policy-report-only: default-src 'self' blob: https: data: mediastream: 'unsafe-eval' 'unsafe-inline';report-uri https://metrics.media-amazon.com/
< Content-Security-Policy: upgrade-insecure-requests;report-uri https://metrics.media-amazon.com/
< Content-Type: text/html;charset=UTF-8
< Date: Wed, 07 Jun 2023 17:00:21 GMT
< Expires: -1
< Pragma: no-cache
< Server: Server
< Set-Cookie: session-token="hZaoPx6FXPufwTH2nDgPJduxHjK6OyTqxMznqd61GhFEyYY5sNmuxbIQkPI+...; Version=1; Domain=.amazon.com; Max-Age=31536000; Expires=Thu, 06-Jun-2024 17:00:21 GMT; Path=/; Secure
< Strict-Transport-Security: max-age=47474747; includeSubDomains; preload
< transfer-encoding: chunked
< Vary: Content-Type,Accept-Encoding,User-Agent
< x-amz-rid: FG309ZKDP3VQC53KWGYZ
< X-Content-Type-Options: nosniff
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1;
< Connection: Transfer-Encoding
< 
<!doctype html><html lang="en-us" class="a-no-js a-touch a-mobile" data-19ax5a9jf="mongoose"><!-- sp:feature:head-start -->
...
</div></body></html>
<!--       _
       .__(.)< (MEOW)
        \___)   
 ~~~~~~~~~~~~~~~~~~-->
* Connection #0 to host localhost left intact

Without Proxyman:

   Trying 65.9.104.215:443...
* Connected to www.amazon.com (65.9.104.215) port 443 (#0)
* ALPN: offers http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=www.amazon.com
*  start date: Jan 17 00:00:00 2023 GMT
*  expire date: Jan 16 23:59:59 2024 GMT
*  subjectAltName: host "www.amazon.com" matched cert's "www.amazon.com"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /gp/aw/c HTTP/1.1
> Host: www.amazon.com
> Accept: */*
> Cookie: at-main=Atza|IwEBIKV4oEO6QN6tXrkQ0nW5XQg...."
> User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5} like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
> Accept-Language: en-US,en;q=0.9
> 
< HTTP/1.1 200 OK
< Accept-CH-Lifetime: 86400
< Accept-CH: ect,rtt,downlink,device-memory,sec-ch-device-memory,viewport-width,sec-ch-viewport-width,dpr,sec-ch-dpr
< Cache-Control: no-cache, no-store, must-revalidate, max-age=0
< Connection: keep-alive
< Content-Language: en-US
< content-security-policy-report-only: default-src 'self' blob: https: data: mediastream: 'unsafe-eval' 'unsafe-inline';report-uri https://metrics.media-amazon.com/
< Content-Security-Policy: upgrade-insecure-requests;report-uri https://metrics.media-amazon.com/
< Content-Type: text/html;charset=UTF-8
< Date: Wed, 07 Jun 2023 17:04:52 GMT
< Expires: -1
< Pragma: no-cache
< Server: Server
< set-cookie: session-token="3+TLhtwYhn0wx6og/E2lcrSGfpW6ZV03J559uHOnNEDPhXNh16hXEdluz7sndrLc4Q+...."; Version=1; Domain=.amazon.com; Max-Age=31536000; Expires=Thu, 06-Jun-2024 17:04:52 GMT; Path=/; Secure
< Strict-Transport-Security: max-age=47474747; includeSubDomains; preload
< Transfer-Encoding: chunked
< Vary: Content-Type,Accept-Encoding,User-Agent
< x-amz-rid: F30J6F5TTJCMNGSWQSRN
< X-Content-Type-Options: nosniff
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1;
< X-Cache: Miss from cloudfront
< Via: 1.1 b12493f4f82b360a236f87474564427a.cloudfront.net (CloudFront)
< X-Amz-Cf-Id: Ird1PIInp_HMTugma1KECaIHWElk0ly7BkGs5-8zxnghLsNxq8zFvg==
< X-Amz-Cf-Pop: TLV50-C2
< Content-Encoding: gzip

< 
Warning: Binary output can mess up your terminal. Use "--output -" to tell 
Warning: curl to output it to your terminal anyway, or consider "--output 
Warning: <FILE>" to save to a file.
* Failure writing output to destination
* Failed reading the chunked-encoded stream
* Closing connection 0

As can bee seen, the request that does not go through Proxyman returns with "Content-Encoding: gzip". Unclear why would going through a proxy change the response by the server. Thoughts?

<!-- gh-comment-id:1581230426 --> @seidnerj commented on GitHub (Jun 7, 2023): More info on the above, this is the difference between the request going through Proxyman and the one that does not. Through Proxyman: ``` Trying 127.0.0.1:9090... * Connected to localhost (127.0.0.1) port 9090 (#0) * allocate connect buffer * Establish HTTP proxy tunnel to www.amazon.com:443 > CONNECT www.amazon.com:443 HTTP/1.1 > Host: www.amazon.com:443 > User-Agent: curl/7.88.1 > Proxy-Connection: Keep-Alive > < HTTP/1.1 200 Connection Established < Content-Length: 0 * Ignoring Content-Length in CONNECT 200 response < * CONNECT phase completed * CONNECT tunnel established, response 200 * ALPN: offers h2,http/1.1 * (304) (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/cert.pem * CApath: none * (304) (IN), TLS handshake, Server hello (2): * (304) (IN), TLS handshake, Unknown (8): * (304) (IN), TLS handshake, Certificate (11): * (304) (IN), TLS handshake, CERT verify (15): * (304) (IN), TLS handshake, Finished (20): * (304) (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 * ALPN: server did not agree on a protocol. Uses default. * Server certificate: * subject: C=US; L=Wilmington; O=Proxyman LLC; CN=www.amazon.com; ST=Delaware * start date: Jun 7 12:23:02 2023 GMT * expire date: Jul 8 12:23:02 2024 GMT * subjectAltName: host "www.amazon.com" matched cert's "www.amazon.com" * issuer: C=US; L=Wilmington; O=Proxyman LLC; CN=Proxyman CA (19 Apr 2023, macbook-pro-16.local); OU=https://proxyman.io; ST=Delaware * SSL certificate verify ok. * using HTTP/1.x > GET /gp/aw/c HTTP/1.1 > Host: www.amazon.com > Accept: */* > Cookie: at-main=Atza|IwEBIKV4oEO6QN6tXrkQ0nW5XQgCy-fHn_EUgIn4IsuTMSMqIDU_f...." > User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5} like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 > Accept-Language: en-US,en;q=0.9 > < HTTP/1.1 200 OK < Accept-CH-Lifetime: 86400 < Accept-CH: ect,rtt,downlink,device-memory,sec-ch-device-memory,viewport-width,sec-ch-viewport-width,dpr,sec-ch-dpr < Cache-Control: no-cache, no-store, must-revalidate, max-age=0 < Connection: keep-alive < Content-Language: en-US < content-security-policy-report-only: default-src 'self' blob: https: data: mediastream: 'unsafe-eval' 'unsafe-inline';report-uri https://metrics.media-amazon.com/ < Content-Security-Policy: upgrade-insecure-requests;report-uri https://metrics.media-amazon.com/ < Content-Type: text/html;charset=UTF-8 < Date: Wed, 07 Jun 2023 17:00:21 GMT < Expires: -1 < Pragma: no-cache < Server: Server < Set-Cookie: session-token="hZaoPx6FXPufwTH2nDgPJduxHjK6OyTqxMznqd61GhFEyYY5sNmuxbIQkPI+...; Version=1; Domain=.amazon.com; Max-Age=31536000; Expires=Thu, 06-Jun-2024 17:00:21 GMT; Path=/; Secure < Strict-Transport-Security: max-age=47474747; includeSubDomains; preload < transfer-encoding: chunked < Vary: Content-Type,Accept-Encoding,User-Agent < x-amz-rid: FG309ZKDP3VQC53KWGYZ < X-Content-Type-Options: nosniff < X-Frame-Options: SAMEORIGIN < X-XSS-Protection: 1; < Connection: Transfer-Encoding < <!doctype html><html lang="en-us" class="a-no-js a-touch a-mobile" data-19ax5a9jf="mongoose"><!-- sp:feature:head-start --> ... </div></body></html> <!-- _ .__(.)< (MEOW) \___) ~~~~~~~~~~~~~~~~~~--> * Connection #0 to host localhost left intact ``` Without Proxyman: ``` Trying 65.9.104.215:443... * Connected to www.amazon.com (65.9.104.215) port 443 (#0) * ALPN: offers http/1.1 * (304) (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/cert.pem * CApath: none * (304) (IN), TLS handshake, Server hello (2): * (304) (IN), TLS handshake, Unknown (8): * (304) (IN), TLS handshake, Certificate (11): * (304) (IN), TLS handshake, CERT verify (15): * (304) (IN), TLS handshake, Finished (20): * (304) (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256 * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=www.amazon.com * start date: Jan 17 00:00:00 2023 GMT * expire date: Jan 16 23:59:59 2024 GMT * subjectAltName: host "www.amazon.com" matched cert's "www.amazon.com" * issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2 * SSL certificate verify ok. * using HTTP/1.1 > GET /gp/aw/c HTTP/1.1 > Host: www.amazon.com > Accept: */* > Cookie: at-main=Atza|IwEBIKV4oEO6QN6tXrkQ0nW5XQg...." > User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5} like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 > Accept-Language: en-US,en;q=0.9 > < HTTP/1.1 200 OK < Accept-CH-Lifetime: 86400 < Accept-CH: ect,rtt,downlink,device-memory,sec-ch-device-memory,viewport-width,sec-ch-viewport-width,dpr,sec-ch-dpr < Cache-Control: no-cache, no-store, must-revalidate, max-age=0 < Connection: keep-alive < Content-Language: en-US < content-security-policy-report-only: default-src 'self' blob: https: data: mediastream: 'unsafe-eval' 'unsafe-inline';report-uri https://metrics.media-amazon.com/ < Content-Security-Policy: upgrade-insecure-requests;report-uri https://metrics.media-amazon.com/ < Content-Type: text/html;charset=UTF-8 < Date: Wed, 07 Jun 2023 17:04:52 GMT < Expires: -1 < Pragma: no-cache < Server: Server < set-cookie: session-token="3+TLhtwYhn0wx6og/E2lcrSGfpW6ZV03J559uHOnNEDPhXNh16hXEdluz7sndrLc4Q+...."; Version=1; Domain=.amazon.com; Max-Age=31536000; Expires=Thu, 06-Jun-2024 17:04:52 GMT; Path=/; Secure < Strict-Transport-Security: max-age=47474747; includeSubDomains; preload < Transfer-Encoding: chunked < Vary: Content-Type,Accept-Encoding,User-Agent < x-amz-rid: F30J6F5TTJCMNGSWQSRN < X-Content-Type-Options: nosniff < X-Frame-Options: SAMEORIGIN < X-XSS-Protection: 1; < X-Cache: Miss from cloudfront < Via: 1.1 b12493f4f82b360a236f87474564427a.cloudfront.net (CloudFront) < X-Amz-Cf-Id: Ird1PIInp_HMTugma1KECaIHWElk0ly7BkGs5-8zxnghLsNxq8zFvg== < X-Amz-Cf-Pop: TLV50-C2 < Content-Encoding: gzip < Warning: Binary output can mess up your terminal. Use "--output -" to tell Warning: curl to output it to your terminal anyway, or consider "--output Warning: <FILE>" to save to a file. * Failure writing output to destination * Failed reading the chunked-encoded stream * Closing connection 0 ``` As can bee seen, the request that does not go through Proxyman returns with "Content-Encoding: gzip". Unclear why would going through a proxy change the response by the server. Thoughts?
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Jun 8, 2023):

It's our decision to remove these headers: accept-encoding and content-encoding from the Request. The reason is: Many users would like to see the Response Body in plain text from their Terminal.

If the cURL has these headers, the response body is:

< 
Warning: Binary output can mess up your terminal. Use "--output -" to tell 
Warning: curl to output it to your terminal anyway, or consider "--output 
Warning: <FILE>" to save to a file.

which is hard to see the Content.

I guess, I would add an option into the Setting, so it doesn't omit any headers.

<!-- gh-comment-id:1582110546 --> @NghiaTranUIT commented on GitHub (Jun 8, 2023): It's our decision to remove these headers: `accept-encoding` and `content-encoding` from the Request. The reason is: Many users would like to see the Response Body in plain text from their Terminal. If the cURL has these headers, the response body is: ``` < Warning: Binary output can mess up your terminal. Use "--output -" to tell Warning: curl to output it to your terminal anyway, or consider "--output Warning: <FILE>" to save to a file. ``` which is hard to see the Content. ------------ I guess, I would add an option into the Setting, so it doesn't omit any headers.
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@seidnerj commented on GitHub (Jun 8, 2023):

The thing is, when you're trying to replicate behavior already seen by using cURL, you expect the same result. Not including this header can not only change the encoding by the server, but can also affect the actual content and/or flow that follows. It depends on what is the logic implemented by the server.

I highly recommended that by default this replicates the exact request.

Thank you for your consideration.

It's our decision to remove these headers: accept-encoding and content-encoding from the Request. The reason is: Many users would like to see the Response Body in plain text from their Terminal.

If the cURL has these headers, the response body is:


< 

Warning: Binary output can mess up your terminal. Use "--output -" to tell 

Warning: curl to output it to your terminal anyway, or consider "--output 

Warning: <FILE>" to save to a file.

which is hard to see the Content.

I guess, I would add an option into the Setting, so it doesn't omit any headers.

<!-- gh-comment-id:1582174908 --> @seidnerj commented on GitHub (Jun 8, 2023): The thing is, when you're trying to replicate behavior already seen by using cURL, you expect the same result. Not including this header can not only change the encoding by the server, but can also affect the actual content and/or flow that follows. It depends on what is the logic implemented by the server. I highly recommended that by default this replicates the exact request. Thank you for your consideration. > It's our decision to remove these headers: `accept-encoding` and `content-encoding` from the Request. The reason is: Many users would like to see the Response Body in plain text from their Terminal. > > > > If the cURL has these headers, the response body is: > > ``` > > < > > Warning: Binary output can mess up your terminal. Use "--output -" to tell > > Warning: curl to output it to your terminal anyway, or consider "--output > > Warning: <FILE>" to save to a file. > > ``` > > which is hard to see the Content. > > > > ------------ > > I guess, I would add an option into the Setting, so it doesn't omit any headers.
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Jun 9, 2023):

Thanks @seidnerj I will put this flag in the next release 👍

<!-- gh-comment-id:1584209738 --> @NghiaTranUIT commented on GitHub (Jun 9, 2023): Thanks @seidnerj I will put this flag in the next release 👍
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@seidnerj commented on GitHub (Jun 9, 2023):

Many thanks!

<!-- gh-comment-id:1584287516 --> @seidnerj commented on GitHub (Jun 9, 2023): Many thanks!
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Jun 10, 2023):

@seidnerj you can try this Beta build: https://download.proxyman.io/beta/Proxyman_4.8.0_Support_cURL_Encoding_Headers.dmg

You can disable it in the Setting -> Tool -> Remove Encoding Header. It's ON by default to avoid breaking the current behavior.

CleanShot 2023-06-10 at 14 38 35@2x

<!-- gh-comment-id:1585559249 --> @NghiaTranUIT commented on GitHub (Jun 10, 2023): @seidnerj you can try this Beta build: https://download.proxyman.io/beta/Proxyman_4.8.0_Support_cURL_Encoding_Headers.dmg You can disable it in the Setting -> Tool -> Remove Encoding Header. It's ON by default to avoid breaking the current behavior. ![CleanShot 2023-06-10 at 14 38 35@2x](https://github.com/ProxymanApp/Proxyman/assets/5878421/4ae2ba54-7863-4e72-a659-a6d294b69743)
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@seidnerj commented on GitHub (Jun 10, 2023):

You are awesome! Really appreciate the responsiveness with everything! This in part is what makes Proxyman a truly amazing product. Keep up the good work!

<!-- gh-comment-id:1585560081 --> @seidnerj commented on GitHub (Jun 10, 2023): You are awesome! Really appreciate the responsiveness with everything! This in part is what makes Proxyman a truly amazing product. Keep up the good work!
kerem commented 2026-03-03 19:53:17 +03:00
Author
Owner
Copy link

@seidnerj commented on GitHub (Jun 10, 2023):

I think it would be good to consider whether this setting should be something like "preserve original request" which will have an effect on all headers as well as other aspects that might be related.

Right now this option is very specific and there's already another option that changes the original request ("add content-length").

That's just my 2 cents.

<!-- gh-comment-id:1585565587 --> @seidnerj commented on GitHub (Jun 10, 2023): I think it would be good to consider whether this setting should be something like "preserve original request" which will have an effect on all headers as well as other aspects that might be related. Right now this option is very specific and there's already another option that changes the original request ("add content-length"). That's just my 2 cents.
kerem commented 2026-03-03 19:53:18 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Jun 11, 2023):

It's a really good suggestion @seidnerj. I'm going to refactor this way 👍

<!-- gh-comment-id:1585985909 --> @NghiaTranUIT commented on GitHub (Jun 11, 2023): It's a really good suggestion @seidnerj. I'm going to refactor this way 👍
kerem commented 2026-03-03 19:53:18 +03:00
Author
Owner
Copy link

@NghiaTranUIT commented on GitHub (Jun 11, 2023):

I took your advice, and here is the new Beta: https://download.proxyman.io/beta/Proxyman_4.8.0_Use_new_option_for_cURL.dmg

Thanks again 👍

CleanShot 2023-06-11 at 10 40 10@2x

<!-- gh-comment-id:1585995918 --> @NghiaTranUIT commented on GitHub (Jun 11, 2023): I took your advice, and here is the new Beta: https://download.proxyman.io/beta/Proxyman_4.8.0_Use_new_option_for_cURL.dmg Thanks again 👍 ![CleanShot 2023-06-11 at 10 40 10@2x](https://github.com/ProxymanApp/Proxyman/assets/5878421/c5eac0ae-fb43-4c79-91b8-a090c5d44bab)
kerem commented 2026-03-03 19:53:18 +03:00
Author
Owner
Copy link

@seidnerj commented on GitHub (Jun 11, 2023):

That’s great! Many thanks 🚀

<!-- gh-comment-id:1586016006 --> @seidnerj commented on GitHub (Jun 11, 2023): That’s great! Many thanks 🚀
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
6.9.0
6.8.0
6.7.0
6.6.0
6.5.0
6.4.0
6.3.0
6.2.0
6.1.0
6.0.2
6.0.0
6.0.1
5.25.0
5.24.0
5.23.0
5.23.1
5.22.0
5.20.0
5.21.0
5.19.0
5.18.0
5.17.0
5.16.0
5.15.0
5.14.0
5.12.2
5.12.1
5.12.0
5.11.0
5.10.0
5.8.0
5.9.0
5.7.0
5.6.1
5.6.0
5.5.0
5.4.0
5.2.0
5.3.0
5.1.1
5.0.0
4.16.0
4.15.0
4.14.0
4.13.0
4.12.0
4.11.0
4.10.0
4.9.1
4.9.0
4.8.2
4.8.1
4.8.0
4.7.1
4.7.0
4.6.1
4.6.0
4.5.0
4.4.0
4.3.1
4.3.0
4.2.1
4.2.0
4.1.0
4.0.0
3.15.0
3.14.0
3.13.0
3.12.0
3.11.0
3.10.0
3.9.0
3.8.0
3.7.0
3.6.2
3.6.1
3.6.0
3.5.2
3.5.1
3.5.0
3.4.0
3.3.0
3.2.0
3.1.0
3.0.0
2.35.4
2.35.3
2.35.2
2.35.1
2.35.0
2.34.1
2.34.0
2.33.0
2.32.1
2.32.0
2.31.0
2.30.0
2.29.0
2.28.0
2.27.0
2.26.0
2.25.0
2.24.0
2.23.0
2.22.0
2.21.1
2.21.0
2.20.0
2.19.0
2.18.0
2.17.0
2.16.1
2.16.0
2.15.2
2.15.1
2.15.0
2.14.2
2.14.1
2.14.0
2.13.0
2.12.0
2.11.1
2.11.0
2.10.0
2.9.1
2.9.0
2.8.0
2.7.0
2.6.0
2.5.3
2.5.2
2.5.1
2.5.0
2.4.2
2.4.1
2.4.0
2.3.0
2.2.0
2.1.1
2.1.0
2.0.1
2.0.0
1.24.0
1.23.0
1.22.0
1.21.0
1.20.0
1.19.0
1.18.1
1.18.0
1.17.1
1.17.0
1.16.0
1.15.0
1.14.1
1.14.0
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.3
1.9.2
1.9.1
1.9.0
1.8.0
1.7.2
1.7.1
1.7.0
1.6.2
1.6.1
1.6.0
1.5.1
1.5.0
1.4.7
1.4.6
1.4.5.1
1.4.5
1.4.4.1
1.4.4
1.4.3
1.4.2
1.4.1.1
1.4.1
1.4
1.3.9
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4.3
1.3.4.2
1.3.4.1
1.3.4
1.3.3
1.3.2
1.3.1
1.3
1.2
1.1.2
1.1.1
1.1
1.0.3
1.0.2
1.0
0.8.1
0.8
0.7
0.6
0.5.1
0.5
v0.4.1
Labels
Clear labels   
Discussion

   
Feature request

   
In Progress...

   
Plugins

   
Waiting response

   
Windows

   
Windows

   
bug

   
duplicate

   
enhancement

   
feature

   
good first issue

   
iOS

   
macOS 10.11

   
question

   
wontfix

   
✅ Done
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#1662
No description provided.