Repository navigation
Add support for HTTP/3 #9463
Description
Activity
- changed the title
[-]Update scanner to include http3 only websites[/-][+]Add support for HTTP/3[/+]on Sep 14, 2026 Hello ZAP Maintainers, I am currently looking into implementing HTTP/3. During my deep dive, I noticed that ZAP's current proxy foundation is built strictly for TCP, while QUIC requires UDP. To proceed, would you recommend I focus solely on building an outbound HTTP/3 client first, or do you have a preferred strategy for handling this transport mismatch?
This is not a good first issue.
@thc202 I would like to take on this issue. Please give me a chance to demonstrate my ability to tackle it. I am fully prepared to dedicate time to the necessary research and code implementation, and I'll deliver my best work. Could you please assign this issue to me?
Is your feature request related to a problem? Please describe.
Hi There,
I have a website (working/can be connected to) based on http3 only, but your service/scanner seems it doesnt support that, maybe for the futuristic features better to upgrade accordingly.
My website:
https://http3only.servomed.de/
Will show "Failed to attack network unreachable" but thats false.
ThX!
Describe the solution you'd like:
Add http3 only (no http1.0,1.1,2.0) scan ability.
Describe alternatives you've considered:
N/A
Screenshots:
No response
Additional context:
No response
Would you like to help fix this issue?