On 6/7/19 5:24 AM, Srikanth Raju wrote:
>
>
> > * The biggest reason we care about TLS termination with bump is
> > because we think it might give us performance benefits along some
> > critical code paths *due to connection pooling to some slow
> > upstreams within
Thank you for the reply Amos. I went back and read the documentation yesterday
with a fresh set of eyes and realized what I was doing wrong. Your summary at
the end of your reply is exactly where I ended up once I understood what the
follow_x_forwarded_for directive was doing. To be fair,
On 7/06/19 11:24 pm, Srikanth Raju wrote:
>
>
> > * The biggest reason we care about TLS termination with bump is
> > because we think it might give us performance benefits along some
> > critical code paths *due to connection pooling to some slow
> > upstreams
> * The biggest reason we care about TLS termination with bump is
> > because we think it might give us performance benefits along some
> > critical code paths *due to connection pooling to some slow
> > upstreams within squid.*
> > * Does squid automatically do this or does it
On 7/06/19 9:30 pm, Srikanth Raju wrote:
> Hello!
> We are planning to use squid as a forward egress proxy to whitelist
> domains. In general, we configured it to whitelist/blacklist domains
> based on the examples in the site and this seems to work with peek and
> splice on our preliminary tests
On 7/06/19 6:43 pm, Techie wrote:
> Hello,
>
> Running Squid 3.5 on Centos
>
> I am trying to limit uploads to AWS S3 buckets using squid to prevent
> saturation by end users.
>
> I have tried utilizing client delay pools but they seem to have no effect.
> delay pools for limiting downloads
On 7/06/19 2:38 am, Joey Officer wrote:
> Greetings all,
>
>
>
> squid.conf references the ability to use the x-forwarded-for header in
> ACLs by using the follow_x_forwarded_for in ACL, referenced here:
> http://www.squid-cache.org/Doc/config/follow_x_forwarded_for/ and here
>
Hello!
We are planning to use squid as a forward egress proxy to whitelist
domains. In general, we configured it to whitelist/blacklist domains based
on the examples in the site and this seems to work with peek and splice on
our preliminary tests as a transparent egress proxy. We're doing this
On 7/06/19 6:50 pm, Techie wrote:
> Hello,
>
> Previously running squid 3.1 on Centos 6, recently went to Centos7 with
> squid 3.5.
> Since the upgrade I have been receiving SSL errors connecting to https
> sites.
>
> I notice in the log for squid 3.1I have entries like this when hitting
> https
Hello,
Previously running squid 3.1 on Centos 6, recently went to Centos7 with
squid 3.5.
Since the upgrade I have been receiving SSL errors connecting to https
sites.
I notice in the log for squid 3.1I have entries like this when hitting
https sites
172.16.80.25 TCP_MISS/200 6086 CONNECT
Hello,
Running Squid 3.5 on Centos
I am trying to limit uploads to AWS S3 buckets using squid to prevent
saturation by end users.
I have tried utilizing client delay pools but they seem to have no effect.
delay pools for limiting downloads work great but I am trying to limit up
not down.
In
11 matches
Mail list logo
