Hello,
I'm running into similar issues due to "reordering". Could you provide the
mentioned code changes, or suggest what I should be looking for? I recently
upgraded from 3.1 (had no such issues) to 3.5, and retained the same
configuration file.
--
Sent from:
http://squid-web-proxy-cache.101
Eliezer
>
>
> http://ngtech.co.il/lmgtfy/
> Linux System Administrator
> Mobile: +972-5-28704261
> Email: elie...@ngtech.co.il
>
>
> From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On
> Behalf Of Sonya Roy
> Sent: Thursday, June 22, 2017 21:
-cache.org] On Behalf
Of Sonya Roy
Sent: Thursday, June 22, 2017 21:54
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Header order in squid proxy
The sites I am talking about check the User-Agent header and makes sure the
user-agent is for a well-known browser, i.e. a browser th
On 06/22/2017 12:54 PM, Sonya Roy wrote:
> The sites I am talking about check the User-Agent header and makes sure
> the user-agent is for a well-known browser, i.e. a browser that they
> support. And any browser like Firefox, Chrome, Safari, Edge for example,
> sends the headers in a certain order
The sites I am talking about check the User-Agent header and makes sure the
user-agent is for a well-known browser, i.e. a browser that they support.
And any browser like Firefox, Chrome, Safari, Edge for example, sends the
headers in a certain order and the order depends on the browser. And this
h
On 06/22/2017 11:49 AM, Sonya Roy wrote:
> I noticed that squid changes the header order received from the client
> before sending it to the origin server.
>
> I assume this is because squid parses the header data and adds some
> headers depending on the config file and then recreates the header
Hi,
I noticed that squid changes the header order received from the client
before sending it to the origin server.
I assume this is because squid parses the header data and adds some headers
depending on the config file and then recreates the header data.
Is there any way to prevent this? To kee