[squid-users] CONNECT errors with 2.7.STABLE2-2

A tool supposedly worked until May and now, due to the evil squid update
to 2.7.x, won't work anymore. Of course squid is to blame, as always.
Since we all know, the professional tool is written with great care,
adhering to the specs and RFC by knowledgeable people. Unlike squid. Of
course. Call me bitter.

From our logs:

1215083751.310 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html
1215083785.295 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html
1215083805.308 2 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html
1215083818.308 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html
1215083819.294 0 10.47.52.76 TCP_MISS/417 1811 CONNECT drm.viasyshc.com:443 - NONE/- text/html

Their app logs:

07/03/08[11:02:09] ERROR: HTTP Transport: POST HTTP error 417 bytes = 16. Retrying Seq No 4, RetryCount 1(max 1)
07/03/08[11:02:09] DEBUG: ====================HEADER INFO START================
 Server: squid/2.7.STABLE2
 Date: Thu, 03 Jul 2008 09:02:10 GMT
 Content-Type: text/html
 Content-Length: 1416
 Expires: Thu, 03 Jul 2008 09:02:10 GMT
 X-Squid-Error: ERR_INVALID_REQ 0
 X-Cache: MISS from proxy-cbf-2.charite.de
 X-Cache-Lookup: NONE from proxy-cbf-2.charite.de:8080
 Via: 1.0 proxy-cbf-2.charite.de:8080 (squid/2.7.STABLE2)
 Connection: close
 ====================HEADER INFO END==================

How can I debug their crap^h^h^h^hprofessional error free software?

-- 
Ralf Hildebrandt (i.A. des IT-Zentrums)         Ralf.Hildebrandt_at_charite.de
Charite - Universitätsmedizin Berlin            Tel.  +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin    Fax.  +49 (0)30-450 570-962
IT-Zentrum Standort CBF                 send no mail to snickebo_at_charite.de