Enhancement: Add support for raising alerts for other than HTTP/1.x interactions
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
ZAP needs a mechanism by which alerts can be raised for messages/packets other than HTTP/1.x (i.e.: for HTTP/2, WebSocket, Raw Socket connections, etc.)
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
The issue names no files, tests, or entry points. Start by tracing how ZAP currently raises alerts for HTTP/1.x interactions, then identify the boundaries for HTTP/2, WebSocket, and raw socket messages. Done means a defined mechanism supports alerts for those non-HTTP/1.x interactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100