ProxymanApp / ProxymanApp/Proxyman
Don't require specific Content-Type header when Protobuf rule is defined for URL
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
Description
My responses have the Content-Type "application/vnd.mapbox-vector-tile" (https://github.com/mapbox/vector-tile-spec). Even though I properly configured Protobuf for the URL path, the previewer did not show the decoded response body:
To circumvent this, I had to add script that changes the header: response.headers["Content-Type"] = "Content-Type: application/protobuf";
Why this feature/change is important?
It would make it easier to decode Protobuf, as right now a custom script is needed in some cases.
Context
Protobuf Settings / rule:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with a Protobuf rule for the URL and a response using Content-Type application/vnd.mapbox-vector-tile. Trace how the previewer decides whether to decode the response, then verify that the configured URL rule takes effect without a header-changing script. Done means the response body is decoded in the previewer despite its custom Content-Type.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100