Thanks for the response Amos. This is an AWS Fargate instance and I'm not
exactly sure how patching works in that space. I'm rather new to both
serverless concept and Squid. I will research this and get back to you.
Thanks!
On Friday, November 22, 2019, Amos Jeffries wrote:
> On 22/11/19 4:05 pm
On 22/11/19 4:05 pm, Chammi Kumarapathirage wrote:
> I have my logformat as follows.
> logformat jsonformat {"Client Hostname":"%>A","Source IP":"%>a","HTTP
> Method":"%rm","HTTP Protocol version":"%rv","Request
> Domain":"%>rd","Port":"%>rP","User Agent":"%{User-Agent}>h","Request
> Size":"%>st","
I have my logformat as follows.
logformat jsonformat {"Client Hostname":"%>A","Source IP":"%>a","HTTP Method
":"%rm","HTTP Protocol version":"%rv","Request Domain":"%>rd","Port":"%>rP",
"User Agent":"%{User-Agent}>h","Request Size":"%>st","Reply
Size":"%Hs","Request Status":"%Ss","Server FQDN":"
%
On 15/11/19 2:56 pm, chammidhan wrote:
> I have configured a Squid ECS cluster behind a network load balancer in AWS.
> To reflect the original client IP, I needed to enable PROXY Protocol V2 on
> the load balancer. The service itself is working fine and I can create rules
> based on the original c
I have configured a Squid ECS cluster behind a network load balancer in AWS.
To reflect the original client IP, I needed to enable PROXY Protocol V2 on
the load balancer. The service itself is working fine and I can create rules
based on the original client IP and these are applied as expected. How
