Re: [squid-users] Proper Cache Peer Access

2016-12-16 Thread Amos Jeffries
On 14/12/2016 2:56 p.m., cred...@eml.cc wrote: > On Tue, Dec 13, 2016, at 06:33 PM, Amos Jeffries wrote: >> On 14/12/2016 2:10 p.m., creditu wrote: >>> Looking for the best way to provide cache peer access for two urls on a >>> 3.1 accelerator. For example if a set of backend servers fullfill >>>

Re: [squid-users] Proper Cache Peer Access

2016-12-13 Thread creditu
On Tue, Dec 13, 2016, at 06:33 PM, Amos Jeffries wrote: > On 14/12/2016 2:10 p.m., creditu wrote: > > Looking for the best way to provide cache peer access for two urls on a > > 3.1 accelerator. For example if a set of backend servers fullfill > > requests for both www.example.com and www-legacy.e

Re: [squid-users] Proper Cache Peer Access

2016-12-13 Thread Amos Jeffries
On 14/12/2016 2:10 p.m., creditu wrote: > Looking for the best way to provide cache peer access for two urls on a > 3.1 accelerator. For example if a set of backend servers fullfill > requests for both www.example.com and www-legacy.example.com is the > following the correct way to handle them in

[squid-users] Proper Cache Peer Access

2016-12-13 Thread creditu
Looking for the best way to provide cache peer access for two urls on a 3.1 accelerator. For example if a set of backend servers fullfill requests for both www.example.com and www-legacy.example.com is the following the correct way to handle them in regards to the cach peer access? http_port 19