ProxymanApp / ProxymanApp/Proxyman

[Feature Request] Automatically decompress Brotli compressed response body

Open
#1,722 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Description

Description

Currently, Proxyman iOS App doesn't seems to be supporting Brotli decompression out of the box. I have to export the response body and decompress it using unbrotli, which loses all of the awesome feature (such as TreeView) from Proxyman and instead I have to open the response (typically a JSON) in external programs like VSCode and inspect the response from there.

It would be awesome if the Proxyman iOS App can decompress the Brotli response body based on the Content-Encoding header returned by the server!

Why this feature/change is important?

For one or two responses this might be OK, but for just a bit more responses and the process would feel much more devastating. Considering that Cloudflare supported Brotli compression a while ago, this feature would be a very useful one to have when requesting any modern sites that uses the Brotli compression algorithm.

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.

Research direction

Start by tracing how the Proxyman iOS App handles captured response bodies and reads the Content-Encoding header. Compare the current export-and-external-decompression workflow with the desired in-app behavior, including preservation of TreeView for Brotli-compressed responses. Done means supported Brotli responses are decompressed automatically without requiring export.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios
Domain
mobile, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.