How to stop tinyproxy from using “Proxy-Connection” header

connectionhttp-headerstinyproxy

I just setup tinyproxy for the first time, and I'm trying to make it mimic a normal connection as closely as possible. I already disabled the Via header, but I'm not sure how to change the Proxy-Connection:keep-alive header. I would like for it to simply be Connection:keep-alive. I understand that Proxy-Connection is not only revealing of proxy usage, but unnecessary according to sites like this.

To be honest, I'm not sure exactly what party is sending this header, whether it's my local machine or the remote tinyproxy. How would one either verify this and/or change this in the configuration?

Edit:

I'm seeing the header when I use the proxy while browsing in Chrome. Inspecting the request headers in chrome reveals:

Best Answer

Tinyproxy is not adding the Proxy-Connection header. It is the client who must be adding it.

Tinyproxy should even remove this header (and a few others) from the request (or response) before sending it on to the server (or client).

You could verify this by sniffing the traffic between the proxy and server (wireshark...) and looking at the request packets as going from proxy to server.

Related Solutions

TinyProxy: blank screen

That means that TinyProxy is working. Look further down to find the ACL configuration for tinyproxy. You need to tell it what IP ranges to accept. From the documentation:

Allow
Deny
The Allow and Deny options provide a means to customize which clients are 
allowed to access Tinyproxy. Allow and Deny lines can be specified multiple
times to build the access control list for Tinyproxy. The order in the config
file is important. If there are no Access or Deny lines, then all clients are
allowed. Otherwise, the default action is to deny access. The argument to
Access or Deny can be a single IP address of a client host, like 127.0.0.1,
an IP address range, like 192.168.0.1/24 or a string that will be matched
against the end of the client host name, i.e, this can be a full host name like
host.example.com or a domain name like .example.com or even a top level domain
name like .com.

Apache reverse proxy forwarding https header

The problem is that variables describe the environment of the server receiving the request. When the connection is made to the backend HTTP server it will set its own variables to describe its own environment. You cannot force a server to change its own description of the world it lives in; the best you can do is forward a header that the server can choose to use to change its own environment.

I'm not clear on whether you have access to the backend server configuration. If you do, you may be able to use the SetEnv or SetEnvIf directive there. There's some documentation at the mod_env page at apache.org.

Best Answer

Related Solutions

TinyProxy: blank screen

Apache reverse proxy forwarding https header

Related Topic