al NAT rule for all the fscking IPs it uses (if you set a
proxy it does a connect BY IP and not by name, and the IPs are hardcoded
and not resolved by DNS).
So it is possible you can't bump a store connection (remember that
technically a bump is a MITM intrusion that TLS is explicitely design
On Wed, Nov 11, 2020 at 11:45:26AM -0500, Alex Rousskov wrote:
> On 11/11/20 6:56 AM, Lorenzo Marcantonio wrote:
> > I'm using 4.13 with libressl 3.2.2 and SSL bumps.
>
> FYI: Libressl-based builds are not officially supported. I do not know
> whether libressl is a factor
;t
think that so many sites anyway send incomplete chains.
--
Lorenzo Marcantonio
signature.asc
Description: PGP signature
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
pem
Any ideas on how to solve/troubleshoot/workaround the problem?
--
Lorenzo Marcantonio
signature.asc
Description: PGP signature
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
Thank you very much Amos,
why then do we have the problem only if file is > 55kB? The bug your are
referring (#4067) to is not listed in version 3.4 known bugs
Here are the headers for a working transaction (< 55kB):
HTTP/1.1 100 Continue
Connection: keep-alive
HTTP/1.1 200 OK
Server: gunicorn/
Hello,
we have squid 3.4.6 talking to websense over icap.
We have problems in uploading files larger than 55 kB.
this is the icap.log when file is correctly uploaded (<55kB):
1415810436.490 0 192.168.x.x TAG_NONE/000 0 POST
http://www.csm-testcenter.org/test DOMAIN/user HIER_NONE/- -
this
thank for replay
SO = CentOS 7
squid-3.4.6-1.el7.centos.x86_64
=
[root@lv-034-005 squid]# cat squid.conf
#
# Recommended minimum configuration:
#
#Default: debug_options ALL,1
#more: debug_options ALL,1 33,2 28,9
debug_options ALL,1 2
