On Wed, 2019-07-31 at 11:32 +, Jochen Wiedmann wrote:
>
> On 2019/07/31 10:48:37, Oleg Kalnichevski wrote:
>
> > I am confused now. HttpClient always uses plain HTTP to connect to
> > the
> > first proxy hop. It upgrades to TLS only once the connection to the
> > request target has been
On 2019/07/31 10:48:37, Oleg Kalnichevski wrote:
> I am confused now. HttpClient always uses plain HTTP to connect to the
> first proxy hop. It upgrades to TLS only once the connection to the
> request target has been fully established. Naturally all CONNECT
> messages get transmitted in
On Wed, 2019-07-31 at 10:29 +, Jochen Wiedmann wrote:
>
> On 2019/07/31 10:06:40, Oleg Kalnichevski wrote:
>
> > This is depends on the connection route defined by the route
> > planner.
> > If the connection route in marked as secure HttpClient will attempt
> > to
> > establish a tunnel
On 2019/07/31 10:06:40, Oleg Kalnichevski wrote:
> This is depends on the connection route defined by the route planner.
> If the connection route in marked as secure HttpClient will attempt to
> establish a tunnel through the proxy (by way of CONNECT request)
> instead of passing the
On Wed, 2019-07-31 at 11:31 +0200, Jochen Wiedmann wrote:
> I've got an application, which is sending a SOAP request to an
> external server via a corporate proxy, which I do not control.
> Sending
> the request fails with a message "HTTP/1.1 500 handshakefailed".
> However, sending another
I've got an application, which is sending a SOAP request to an
external server via a corporate proxy, which I do not control. Sending
the request fails with a message "HTTP/1.1 500 handshakefailed".
However, sending another request via SoapUI through the same proxy
works just fine.
In order to
