User-Agent Header not used for TLS tunnel

In case where HTTP tunnel is needed, the “User-Agent” header is reset and the default agent “okhttp/3.x.x” is used. This is causing the request being ignored as its considered to be originating from an unknown client.

Reference code from RealConnection.

 /**
   * Returns a request that creates a TLS tunnel via an HTTP proxy, or null if no tunnel is
   * necessary. Everything in the tunnel request is sent unencrypted to the proxy server, so tunnels
   * include only the minimum set of headers. This avoids sending potentially sensitive data like
   * HTTP cookies to the proxy unencrypted.
   */
  private Request createTunnelRequest() throws IOException {
    return new Request.Builder()
        .url(route.address().url())
        .header("Host", Util.hostHeader(route.address().url(), true))
        .header("Proxy-Connection", "Keep-Alive")
        .header("User-Agent", Version.userAgent()) // For HTTP/1.0 proxies like Squid.
        .build();
  }

[swankjesse]

@JoshSolo you can hack this in with an Authenticator by following the instructions on pre-emptive authentication: https://square.github.io/okhttp/4.x/okhttp/okhttp3/-authenticator/#preemptive-authentication

[yschimke]

Won’t fix.