Hi.
> but this doesn't appear to be used.
I guess that depends on loading order of the libraries. Is it really
required? Most likely not but that's because another library was updated
in the meantime and it bundles (yet another) version of HttpComponents
client (4.0.2).
> Is there any interest in upgrading to a current 4.3.3 version of httpclient throughout the codebase?
Of course, but note that there's a high coupling between ZAP codebase,
Commons HttpClient 3.1 and, more important, the add-ons.
Upgrading all the codebase (e.g. replace
org.apache.commons.httpclient.URI(?)) will lead to binary incompatible
changes, not a problem per se, but it requires carefully planning when
to phaseout (or stop loading) older (binary incompatible) add-ons and
introduce the new ones.
> I'd be happy to dig into this.
A good starting point (and major improvement) would be to adapt/update
the class HttpSender, while keeping it binary compatible ;)
Best regards.