The latest Weekly and Live ZAP releases (generated today, Feb 10th) are now using a completely different networking stack.
Previously, ZAP used code written for Paros Proxy on top of an old and out of date version of the Apache Commons HttpClient library.
Not surprisingly, the ZAP code base makes very heavy use of networking and so this has been a very significant change.
Hopefully not much!
ZAP should work in the same way as before. All of your previous networking related configurations should be maintained.
There are however a few changes you may notice:
- The Options / Local Proxies screen has been replaced by an Options / Network / Local Servers/Proxies screen.
- The Options / Dynamic SSL Certificates screen has been replaced by an Options / Network / Server Certificates screen.
- The Options / Network / Local Servers/Proxies screen has a new tab - “Pass-through” - this allows you to configure the authorities (domain/address and port) that will pass-through ZAP, thus sending the data without being decrypted/encrypted. This is useful when a client has certificate pinning for certain hosts or the domain/data is irrelevant to the target being tested.
That should be all the differences that you see.
Why spent a very significant amount of time and effort replacing the whole networking layer?
Because there’s more to come :)
Now we are using a modern maintained networking layer we can build on top of it and support new protocols like HTTP/2 and HTTP/3.
We will also be able to handle some of the edge cases that we previously could not support including manipulating the Host header.
We expect the new implementation to consume less resources than the previous stack and this will hopefully make requests quicker as well.
Last, but definitely not least, as the networking code is in an add-on we will be able to update it whenever we need to rather than having to wait until the next full release.
There is currently no ETA for these changes but they are a priority for us.
In the meantime please download the Weekly or Live releases, give them a go and let us know if you have any problems or spot any differences in the network handling.
Many thanks to StackHawk who sponsored this work.