Open angryziber opened 2 years ago
What kind of parameters are you configuring via Configuration to enable proxying? What type of authentication is your proxy using? Are you using the same proxy for proxying both HTTP and HTTPS requests?
For example, when configuring proxying via the following:
then TSL HTTPS requests (as I understood HTTP requests already work for you for TSP and OCSP) seem to work without a problem via a proxy that requests Basic auth.
We set both http and https and user and password using these mentioned setters, but it doesn't work - we get errors only TSL requests in logs, but no specifics besides IOException. If we disable proxy, everything works again. We actually found an inconvenient way to disable proxy for TSL only using the internal registry.
We actually found an inconvenient way to disable proxy for TSL only using the internal registry.
By "internal registry", do you mean the ConfigurationRegistry instance inside the org.digidoc4j.Configuration class?
Did you try configuring everything else but the TSL proxy via the connection-type-specific methods?
Where ExternalConnectionType stands for one of TSL
, OCSP
and TSP
.
We are looking into trying to reproduce the issue locally, but with no luck so far.
Unfortunately, it is not possible to set proxy for everything except TSL, e.g.
setHttpProxyHostFor(TSL, "")
has no effect if "global" proxy is already set, but it should accept either blank string or even better, null, do disable TSL proxy.
But the original problem remains: if TSL proxy is set (both http & https), it doesn't use the httpProxyUser/httpProxyPassword, so all requests result in 407 responses
TSL tries to use the proxy without auth and fails. TSP and OCSP respect proxy auth.