Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1026367

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

Show all headers | View raw

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 will try a translation here:

"after analyzing the situation, our development confirms this behavior
with Linux Mint squid version 3.527 as well.
To all appearances, the squid server answers the request with "http://:0"
URL so that ICAP answers the same.

Excerpt of cache.log: (see below)
...

Our developer then compiled a stock Squid version 3.5.27 with similar
compiler flags as the default squid. This version did not reply with
" http://:0" URL.
We cannot decide if this problem occurs if it is a problem with the
squid build or a random error."

### end of my translation

Here the original statement in German language:

##- Please type your reply above this line -##

Your request (303525) been updated. To add additional comments, reply to this email.

Gerhard Boscher (Avira OEM Integration Support)

Sep 25, 2020, 10:44 GMT+2
Hallo Herr Ivory,

nach Untersuchung der Situation stellte unsere Entwicklung bpsw. ebenso mit der default Version von Squid unter Linux Mint  - 3.527. ein gleiches Verhalten fest.
Allen Anschein nach sendet bereits der Squid Server die "http://:0" URLs auf einen Request, so dass ICAP diese in seiner Antwort ebenfalls wiedergibt.

Auszug aus der cache.log:

2020/09/07 14:14:22.182 kid1| 93,9| ModXact.cc(198) handleCommConnected: will write [FD 12r;rw(1)G/R job9]:
REQMOD icap://127.0.0.1:1344/service_scanner-reqmod ICAP/1.0
Host: 127.0.0.1:1344
Date: Mon, 07 Sep 2020 12:14:22 GMT
Encapsulated: req-hdr=0, null-body=233
Allow: 204
HEAD http://:0 HTTP/1.0
User-Agent: w3m/0.5.3+git20170102
Accept: text/html, text/*;q=0.5, image/*, application/*, message/*
Accept-Encoding: gzip, compress, bzip, bzip2, deflate
Accept-Language: en;q=1.0
Host: www.sernet.de


Nachdem unser Entwickler eine Squid  Version 3.5.27 selbst kompilierte , dabei ähnliche Flags verwendete wie die beim system default squid, arbeitete diese Version ohne dass die "http://:0" URL auftrat.
Wir können abschließend leider nicht sagen ob dies eine Problematik des Squid Servers ist die bei system-default builds auftritt oder evtl. zufällig.

Mit freundlichen Grüßen / Best regards

Gerhard Boscher
Specialist OEM Integration Support Engineer




Am 04.09.20 um 15:09 schrieb 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', host='', port='0', path='/'
>> kid1| 23,3| url.cc(492) urlParse: urlParse: Invalid port '0'
> 
> [...]
> 
> So my initial thought is that squid works correctly in this case. This
> is the header which squid needs to parse.
> 
> 
> ICAP/1.0 200 OK
> ISTag: "10017;4140202;836248;8189206"
> Server: AVIRA ICAP (1.21.1.61)
> X-Response-Info: Clean
> Encapsulated: req-hdr=0, null-body=215
> 
> HEAD http://:0 HTTP/1.0
> 
> User-Agent: w3m/0.5.3+git20170102
> Accept: text/html, text/*;q=0.5, image/*, application/*, message/*
> Accept-Language: en;q=1.0
> Host: www.sernet.de
> Accept-Encoding: gzip,bzip2,deflate
> 
> The
> 
> HEAD http://:0 HTTP/1.0
> 
> is weird. It starts with the http protocol but there is no domain name
> and port 0 obviously does not exist. This probably used to work because
> the squid3 parser was less strict before. I would try to change the
> output of your AVIRA server. Is there a reason why it has to send this
> specific HEAD line in the first place and can you modify it?


Best regards
Kevin Ivory (SerNet Support)
-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: 0551-370000-0, mailto:kontakt@sernet.de
Gesch.F.: Dr. Johannes Loxen und Reinhild Jung
AG Göttingen: HR-B 2816 - http://www.sernet.de

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 Andreas Schulz <andreas.schulz@tds.fujitsu.com> - 2020-07-14 14:10 +0200
  Bug#965012: add. information Andreas Schulz <andreas.schulz@tds.fujitsu.com> - 2020-07-14 14:30 +0200
  Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 Markus Koschany <apo@debian.org> - 2020-07-27 00:20 +0200
    Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327] SerNet Support Kevin Ivory <support@SerNet.de> - 2020-08-03 17:10 +0200
  Bug#965012: new test with debug_options ALL,9 Markus Koschany <apo@debian.org> - 2020-08-04 15:10 +0200
  Bug#965012: new test with debug_options ALL,9 Markus Koschany <apo@debian.org> - 2020-08-13 18:20 +0200
  Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327] SerNet Support Kevin Ivory <support@SerNet.de> - 2020-08-18 13:40 +0200
    Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327] Markus Koschany <apo@debian.org> - 2020-08-18 21:50 +0200
      Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327] SerNet Support Kevin Ivory <support@SerNet.de> - 2020-08-28 12:00 +0200
        Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327] Markus Koschany <apo@debian.org> - 2020-08-28 15:10 +0200
          Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327] SerNet Support Oliver Seufer <support@SerNet.de> - 2020-09-04 10:10 +0200
            Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327] Markus Koschany <apo@debian.org> - 2020-09-04 15:20 +0200
              Bug#965012: /usr/sbin/squid: ICAP-Error after Upgrade from 3.5.23-5+deb9u1 to 3.5.23-5+deb9u2 [TT#2398327] SerNet Support Kevin Ivory <support@SerNet.de> - 2020-09-25 11:30 +0200
  Bug#965012: new test with debug_options ALL,9 <j.stribrsky@email.cz> - 2020-09-02 11:40 +0200
    Bug#965012: squid3 http://:0 problem Markus Koschany <apo@debian.org> - 2020-09-29 00:10 +0200
  Bug#965012: RFT: squid3 3.5.23-5+deb9u5, please test Markus Koschany <apo@debian.org> - 2020-09-29 00:20 +0200
    Bug#965012: RFT: squid3 3.5.23-5+deb9u5, please test [TT#2407228] SerNet Support Kevin Ivory <support@SerNet.de> - 2020-09-29 15:10 +0200
    Bug#965012: RFT: squid3 3.5.23-5+deb9u5, please test Roberto C. Sánchez <roberto@debian.org> - 2020-09-29 22:50 +0200
    Bug#965012: RFT: squid3 3.5.23-5+deb9u5, please test Andreas Schulz <andreas.schulz@tds.fujitsu.com> - 2020-09-30 10:50 +0200
      Bug#965012: RFT: squid3 3.5.23-5+deb9u5, please test Markus Koschany <apo@debian.org> - 2020-10-02 18:40 +0200
  Bug#965012: squid3 http://:0 problem <j.stribrsky@email.cz> - 2020-09-29 08:40 +0200

csiph-web