"Content-Encoding: gzip" is not being added to the response header for some reason.

Open
#2,124 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
macos

Research direction

Start with response scripting and the built-in gzip plugin described in the report; reproduce the header change while parsing and stringifying the JSON response. Check whether the response header is preserved when the response is sent, and consider the issue done when Content-Encoding: gzip is delivered to the device as expected.

Written by the indexing model from the issue text.

Description

bug

Description

Due to the nature of the application I'm trying to proxy, it requires this header to be set even if the response data isn't actually inflated.

I can confirm I can add any other custom header except for that header.

Steps to Reproduce

  1. Attempt to modify response headers
  2. Add some new JSON data to the response body by parsing then stringifying

Current Behavior

In response scripting, adding response.headers["Content-Encoding"] = "gzip"; before modifiying the response body by parsing, commiting the changes to the body and stringifying to finally send back seems to programmatically modify the response headers, but it doesn't actually send that header back.
I've tried the builtin gzip plugin to try inflating the data before sending it to see if automatically adds that header but it doesn't.

Expected Behavior

The header should've been added and sent back to the device.

Environment

  • App version: Proxyman Version 5.7.0 (50700)
  • macOS version: Version 13.2.1 (Build 22D68)
Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProxymanApp/Proxyman

All issues in ProxymanApp/Proxyman

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.