Support HTTP/2

[psiinon]

This depends on #1765
No eta yet, the above issue is non trivial :/

[zesty]

Is there somewhere interested folks can follow discussion/development on this?

[kingthorin]

Yup right here. Though there's really nothing to discuss. It is being actively worked on.

[psiinon]

@zesty is there anything in particular you like to know?

[zesty]

@psiinon nope, just curious

[eranpeleg1]

hey,
@psiinon
#1765 seems to be closed
does it means zap supports http2 ?

[psiinon]

@eranpeleg1 in the weeklies yes 😁
Have a play and let us know how it works for you!

[zesty]

Does this mean that HTTP host header (and/or "some parts"?) manipulation is arriving soon?

ref: "zap missing features" at: https://www.zaproxy.org/docs/burp-to-zap-feature-map/

[psiinon]

@zesty Yes - in fact its partly done.
I've just submitted this PR to update that page: zaproxy/zaproxy-website#1500

[thc202]

Should we close this? (It was not yet "officially" announced though, e.g. changelog or main release notes.)

[kingthorin]

I think we can.

[thc202]

Closing, we did mention it's complete in a monthly blog post: https://www.zaproxy.org/blog/2023-02-02-zap-updates-2023-january/#http2-support

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.