Hi, all!
We use squid with tproxy for caching. As our special construct,
our client origin destination is useless for getting the right
response. So if there is any workaround, can we force squid use the
Host header query result as the origin destination server address for
fetch response. Here is
r my purpose.
On Wed, Dec 25, 2013 at 6:05 PM, Amos Jeffries wrote:
> On 25/12/2013 9:12 p.m., Ge Jin wrote:
>> Hi, all!
>>
>> We use squid with tproxy for caching. As our special construct,
>> our client origin destination is useless for getting the right
>> response
Hi all!
We want to use tcp_outgoing_tos with freeBSD 10.0-BETA2.
And our test cases is very simple.
Here is the related configure.
# Squid normally listens to port 3128
acl normal_service_net src 192.168.1.1/32
acl good_service_net src 192.168.2.1/32
tcp_outgoing_tos 0x20 normal_service_net
tcp_o
And I tested with the same sutation on my Ubuntu server, it works correct :)
On Thu, Dec 26, 2013 at 3:59 PM, Ge Jin wrote:
> Hi all!
>
> We want to use tcp_outgoing_tos with freeBSD 10.0-BETA2.
>
> And our test cases is very simple.
> Here is the related configure.
> # Squi
PV6_TCLASS) on local=0.0.0.0
remote=[::] FD 18 flags=1: (22) Invalid argument
On Sat, Dec 28, 2013 at 12:40 AM, Andrew Beverley wrote:
> On Thu, 2013-12-26 at 15:59 +0800, Ge Jin wrote:
>> Hi all!
>>
>> We want to use tcp_outgoing_tos with freeBSD 10.0-BETA2.
>
> [...]
&
Hi, all!
I've searched the archives and not been able to find an answer so I
thought I'd post. Apologies if it's been covered before.
In the squid document, the directive tcp_outgoing_address says:
# NOTE: The use of this directive using client dependent ACLs is
# incompatible with the use of
