Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

2020-09-25 Thread SerNet Support Kevin Ivory
Hi Markus, Oliver had submitted a bug report to Avira OEM integration support and they have finally analyzed the problem. The developer states that it is a problem of the (Debian or Mint) Squid build that does not occur in a vanilla build of the standard squid3 package. German message below. I

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

2020-09-04 Thread Markus Koschany
Hello Oliver, Am 04.09.20 um 09:44 schrieb SerNet Support Oliver Seufer: > Hello Markus, > > This is Oliver. I just did some more troubleshooting and I found the error > message in the debug logfile: > kid1| 23,3| url.cc(471) urlParse: urlParse: Split URL 'http://:0' into > proto='http',

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

2020-09-04 Thread SerNet Support Oliver Seufer
Hello Markus, This is Oliver. I just did some more troubleshooting and I found the error message in the debug logfile: kid1| 23,3| url.cc(471) urlParse: urlParse: Split URL 'http://:0' into proto='http', host='', port='0', path='/' kid1| 23,3| url.cc(492) urlParse: urlParse: Invalid port '0'

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

2020-08-28 Thread Markus Koschany
Hello Kevin, Am 28.08.20 um 11:53 schrieb SerNet Support Kevin Ivory: [...] > is there any way to extract only the data you need? > > All cases in my debug log (46 GB) seem to be of a POST > that is logged in access.log as > 2020-08-27 11:29:24   1243 172.16.100.3 TAG_NONE/500 3640 POST >

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

2020-08-28 Thread SerNet Support Kevin Ivory
Hello Markus, we are having problems extracting a test case with debug data. The problem arises sporadically on our customer systems with HTTP POST or PUT, rarely with GET, sometimes with out HTTP monitoring, sometimes with Debian updates. Since I haven't been able to create a test case on our

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

2020-08-18 Thread Markus Koschany
Hello Kevin, On Tue, 18 Aug 2020 13:37:30 +0200 SerNet Support Kevin Ivory wrote: > Hi Markus, > > On Thu, 13 Aug 2020 21:56:14 +0200 Markus Koschany wrote: > > Version: 3.5.23-5+deb9u3 > > thanks for the work on the patches. We have two different ICAP dependent > packages. After installing

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

2020-08-18 Thread SerNet Support Kevin Ivory
Hi Markus, On Thu, 13 Aug 2020 21:56:14 +0200 Markus Koschany wrote: Version: 3.5.23-5+deb9u3 thanks for the work on the patches. We have two different ICAP dependent packages. After installing squid 3.5.23-5+deb9u3, ICAP worked for Avira ICAP, but it did not work for our squid-redirector

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327]

2020-08-03 Thread SerNet Support Kevin Ivory
Just for the sake of completeness: we have this problem as well and still have many systems with Debian Stretch that need Squid Icap to communicate with Avira Savapi antivirus. Because this bugs hits us as well, we are now holding on to version 3.5.23-5+deb9u1. On Mon, 27 Jul 2020 00:15:18 +0200

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2

2020-07-26 Thread Markus Koschany
Hello Andreas, On Tue, 14 Jul 2020 13:57:48 +0200 Andreas Schulz wrote: > Package: squid > Version: 3.5.23-5+deb9u2.1 > Severity: important > File: /usr/sbin/squid > > Dear Maintainer, > > We installed the security update deb9u2 and learned that no more > http-access (with icap) was possible.

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2

2020-07-14 Thread Andreas Schulz
Package: squid Version: 3.5.23-5+deb9u2.1 Severity: important File: /usr/sbin/squid Dear Maintainer, We installed the security update deb9u2 and learned that no more http-access (with icap) was possible. No problem with https because https is forwarded directly and with disabled icap feature