Skip to content

Instantly share code, notes, and snippets.

@hispanic
Created November 26, 2015 12:43
Show Gist options
  • Select an option

  • Save hispanic/c6ddbdc0498fb5794d6f to your computer and use it in GitHub Desktop.

Select an option

Save hispanic/c6ddbdc0498fb5794d6f to your computer and use it in GitHub Desktop.
HttpClient Logging - Connection discarded
http-outgoing-58: Shutdown connection
Connection discarded
http-outgoing-58: Close connection
Connection released: [id: 58][route: {}->http://myhost:8080[total kept alive: 6; route allocated: 4 of 50; total allocated: 6 of 100]
@devansharora68
Copy link

Hello
We are facing similar issue.
Httpclient version 4.5.13

first call goes to squid proxy cache (enabled with basic auth).
It replies with X-Squid-Error: ERR_CACHE_ACCESS_DENIED

When proxy challenge is sent to squid it fails with below statements

|myproxyhost:80 requested authentication
org.apache.http.impl.client.ProxyAuthenticationStrategy:select|175|Authentication schemes in the order of preference: [Negotiate, Kerberos, NTLM, CredSSP, Digest, Basic]
org.apache.http.impl.client.ProxyAuthenticationStrategy:select|203|Challenge for Negotiate authentication scheme not available
org.apache.http.impl.client.ProxyAuthenticationStrategy:select|203|Challenge for Kerberos authentication scheme not available
org.apache.http.impl.client.ProxyAuthenticationStrategy:select|203|Challenge for NTLM authentication scheme not available
org.apache.http.impl.client.ProxyAuthenticationStrategy:select|203|Challenge for CredSSP authentication scheme not available
org.apache.http.impl.client.ProxyAuthenticationStrategy:select|203|Challenge for Digest authentication scheme not available
|org.apache.http.impl.conn.DefaultManagedHttpClientConnection:close|79|http-outgoing-1: Close connection
org.apache.http.impl.execchain.MainClientExec:execute|239|CONNECT refused by proxy: HTTP/1.1 407 Proxy Authentication Required
org.apache.http.impl.execchain.MainClientExec:releaseConnection|104|Connection discarded
org.apache.http.impl.conn.PoolingHttpClientConnectionManager:releaseConnection|351|Connection released: [id: 1][route: {tls}->http://myproxyhost:80->https://myserverurl:443][total available: 0; route allocated: 0 of 2; total allocated: 0 of 20]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment