bug: Request header inspection doesn't work for Accept-Encoding. [Mac Desktop]

[lukesneeringer]

Describe your issue?

I downloaded requestly because I wanted to know what headers I was sending to a server, and the tool I was using (reqwest crate for Rust) doesn't have an easy way to be verbose about a request.

This basic functionality doesn't work, although this appears to be limited to the Accept-Encoding header.

Repro steps

My reproduction case is as follows:

1. Download the current Mac client (1.6.0), install disk image, open app, run the terminal command to enable interception (. <(curl -sS localhost:7040/tpsetup)).
2. Send several basic curl commands with distinct Accept-Encoding headers:

• curl -I -v https://google.com/
• curl -I -v https://google.com/ -H "Accept-Encoding: gzip"
• curl -I -v https://google.com/ -H "Accept-Encoding: brotli"
• curl -I -v https://google.com/ -H "Accept-Encoding: identity"

1. Observe that they all have an accept-encoding: gzip header.

What Requestly tool were you using?

• Extension
• Desktop-App
• Android SDK
• Selenium

Your Environment

MacOS

Requestly Version

v1.6.0

Error screenshot

[echo-sg]

Thank you for raising this, we'll check for the issue at our end and revert soon.

[nsrCodes]

Our proxy middleware splits the original connection ( client -> server) into two parts (client -> proxy and proxy -> server) with some pre-defined assumptions. Overriding the accept-encoding is one of those assumptions.

This needs to be fixed since this could also be a likely cause for #271

Thanks for pointing this out, we will try to address this ASAP