network: change normal removal of Accept-Encoding header to being filtered to supported encoding
Open
Nobody has claimed this yet.
add-on
enhancement
in:network
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
Is your feature request related to a problem? Please describe.
IMHO, ZAP should look like a legit browser as much as possible. Otherwise, site scans may be filtered.
The current behavior and recommendation from the ZAP documentation is to remove Accept-Encoding. I propose to change this to:
- Keep the incoming Accept-Encoding values, filtering out unsupported encodings.
- For non-proxy requests, add the supported Accept-Encoding values.
Describe the solution you'd like
- Keep the incoming Accept-Encoding values, filtering out unsupported encodings.
- For non-proxy requests, add the supported Accept-Encoding values.
Describe alternatives you've considered
A proxy script.
Screenshots
No response
Additional context
No response
Would you like to help fix this issue?
- Yes
Contributor guide
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
Review ZAP's documentation for the current Accept-Encoding recommendation and trace the proxy and non-proxy request paths. Verify completion by preserving supported incoming encodings, filtering unsupported ones, and adding supported encodings for non-proxy requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100