Package: squid Version: 3.5.23-5 Followup-For: Bug #864389 It seems, that the problem is only related to https pages. Maybe some default or compile-time parameters have changed in recent update? Because now, Squid cannot cope with https requests. If it would only pass them thru by default... Now, because SSL support is not compiled in, it is not easy to cover it otherwise...
-- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=sk_SK.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8), LANGUAGE=sk_SK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages squid depends on: ii adduser 3.115 ii libc6 2.24-11 ii libcap2 1:2.25-1 ii libcomerr2 1.43.4-2 ii libdb5.3 5.3.28-12+b1 ii libdbi-perl 1.636-1+b1 ii libecap3 1.0.1-3.2 ii libexpat1 2.2.0-2 ii libgcc1 1:6.3.0-18 ii libgssapi-krb5-2 1.15-1 ii libkrb5-3 1.15-1 ii libldap-2.4-2 2.4.44+dfsg-5 ii libltdl7 2.4.6-2 ii libnetfilter-conntrack3 1.0.6-2 ii libnettle6 3.3-1+b1 ii libpam0g 1.1.8-3.6 ii libsasl2-2 2.1.27~101-g0780600+dfsg-3 ii libstdc++6 6.3.0-18 ii libxml2 2.9.4+dfsg1-2.2 ii logrotate 3.11.0-0.1 ii lsb-base 9.20161125 ii netbase 5.4 ii squid-common 3.5.23-5 Versions of packages squid recommends: ii libcap2-bin 1:2.25-1 Versions of packages squid suggests: pn resolvconf <none> pn smbclient <none> pn squid-cgi <none> pn squid-purge <none> pn squidclient <none> pn ufw <none> pn winbindd <none> -- Configuration Files: /etc/squid/squid.conf changed [not included] -- no debconf information
