Alan Lehman wrote:
CONFIDENTIALITY NOTICE: This e-mail message including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you
-----Original Message-----
From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx]
Sent: Sunday, July 11, 2010 1:55 AM
To: squid-users@xxxxxxxxxxxxxxx
Subject: Re: possible SOAP problem with 3.1.4
Alan Lehman wrote:
We have particular application software license server for our office
that is located behind a Squid proxy. It stopped working after
upgrading
Squid from 3.1.0.17 to 3.1.4. This server periodically goes to the
software company's web site to verify the license is valid and upload
user counts, etc. It appears to be some sort of SOAP application. The
license server runs on a Windows server. From access.log:
Running 3.1.0.17 (succeeds) -
1278609155.802 470 172.16.4.43 TCP_MISS/200 725 POST
http://selectserver.bentley.com/bss/ws/Misc.asmx -
DIRECT/64.90.235.78
text/xml
1278609157.482 1054 172.16.4.43 TCP_MISS/200 117679 POST
http://selectserver.bentley.com/bss/ws/GatewayWS.asmx -
DIRECT/64.90.235.78 text/xml
Running 3.1.4 (fails) -
1278607986.223 1138 172.16.4.43 TCP_MISS/500 838 POST
http://selectserver.bentley.com/bss/ws/Misc.asmx -
DIRECT/64.90.235.78
application/soap+xml
1278607987.128 895 172.16.4.43 TCP_MISS/200 1178 POST
http://selectserver.bentley.com/bss/ws/Misc.asmx -
DIRECT/64.90.235.78
text/xml
I verified the situation by going back to 3.1.0.17 with the same
config,
whereupon it started working again. I tried adding cache deny for
this
domain but it didn't change anything.
Any thoughts would be most appreciated.
Thanks,
Alan Lehman
Don't know the problem.
You are going to have to dig into the request/reply's a bit further to
see what the problems is.
The biggest difference between 3.1.0.17 and 3.1.4 is that HTTP/1.1 is
sent to the server by 3.1.4. It may be doing some broken magic, as
evidenced by the different response type given to Squid now.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.5
So far I'm unable to determine a consistent pattern with Wireshark. Is there a way I can force 3.1.4 to use HTTP/1.0?
Alan
You can reverse the 1.1 enabling patch found here:
http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-9916.patch
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.5
