Had a use case to ask about, apologies if I missed in docs. Is there a
configuration that allows squid running as forward proxy to add a
custom response header containing the origin server IP address that
served the resource? Assuming no cache hierarchy.
In the event that the resource is served
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 8:10 a.m., Darren Spruell wrote:
Had a use case to ask about, apologies if I missed in docs. Is
there a configuration that allows squid running as forward proxy to
add a custom response header containing the origin server IP
address
On Thu, Oct 16, 2014 at 12:40 PM, Amos Jeffries squ...@treenet.co.nz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 8:10 a.m., Darren Spruell wrote:
Had a use case to ask about, apologies if I missed in docs. Is
there a configuration that allows squid running as forward
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/10/2014 9:29 a.m., Darren Spruell wrote:
On Thu, Oct 16, 2014 at 12:40 PM, Amos Jeffries
squ...@treenet.co.nz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
On 17/10/2014 8:10 a.m., Darren Spruell wrote:
Had a use case to ask about,
On Thu, Oct 16, 2014 at 1:53 PM, Amos Jeffries squ...@treenet.co.nz wrote:
I view the Via header as similar to the Received header in SMTP.
In this case it's added by other proxies/caches, correct?
Thats a good analogy, but not quite. It MUST be added by all proxies
including Squid.
