[squid-users] Upstream proxy errors

I have a local squid proxy that passes all requests to an upstream proxy
at our ISP. Normal web pages are fine, but a thick client application
that is proxy aware fails to work if I point it at our local proxy. If
I point it directly at the ISP's proxy, it works perfectly.

I have been doing some packet sniffing. I think I have found the problem
- or at least the symptoms of a problem.

Packets sent from the client to the server via both proxies include
this:-

POST http://de4.autotrader.co.uk/DealerEditv4/services/DealerEdit
HTTP/1.0
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 1.1.4322.573)
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Content-Length: 1966
Expect: 100-continue
Host: de4.autotrader.co.uk
Via: 1.1 jfc:3128 (squid/2.5.STABLE6)
X-Forwarded-For: 192.168.0.10
Cache-Control: max-age=259200
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://soap.dealeredit.autotrader.co.uk"
xmlns:types="http://soap.dealeredit.autotrader.co.uk/encodedTypes"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Header><wsu:Timestamp
xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility"><wsu:Created>2
004-12-16T19:03:34Z</wsu:Created><wsu:Expires>2004-12-16T19:08:34Z</wsu:
Expires></wsu:Timestamp></soap:Header>
  <soap:Body
soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <tns:authenticate>
      <dmsId xsi:type="xsd:int">11111</dmsId>
      <productCode xsi:type="xsd:string">11111111</productCode>
      <clientConfig href="#id1" />
      <date
xsi:type="xsd:dateTime">2004-12-16T00:00:00.0000000-00:00</date>
      <token xsi:type="xsd:string" />
      <sessionId xsi:type="xsd:string" />
    </tns:authenticate>
    <tns:ClientConfiguration id="id1"
xsi:type="tns:ClientConfiguration">
      <browser xsi:type="xsd:string">6.0.2600.0000</browser>
      <clientTime xsi:type="xsd:string">16/12/2004 19:03:34</clientTime>
      <cpu xsi:type="xsd:string">Intel(R) Pentium(R) 4 CPU 1400MHz</cpu>
      <hostname xsi:type="xsd:string">bob.trml.co.uk</hostname>
      <machineId
xsi:type="xsd:string">cbd091ab-ff73-435f-b045-9a</machineId>
      <memory xsi:type="xsd:string">803721216</memory>
      <operatingSystem xsi:type="xsd:string">Microsoft Windows NT
5.1.2600.0</operatingSystem>
      <screenResolution
xsi:type="xsd:string">1600x1200</screenResolution>
      <username xsi:type="xsd:string">Martyn</username>
      <clientDBVersion xsi:type="xsd:string">403</clientDBVersion>
      <clientExeVersion
xsi:type="xsd:string">4.1.0.14</clientExeVersion>
    </tns:ClientConfiguration>
  </soap:Body>
</soap:Envelope>

A packet arriving from the upstream proxy contains this:-

HTTP/1.0 100 Continue
Date: Thu, 16 Dec 2004 18:58:28 GMT
Via: 1.1 cache0 (NetCache NetApp/5.3.1R2)

To which the squid server adds:-

X-Cache: MISS from jfc
Proxy-Connection: close

As it passes it back to the client.

More data then arrives from the upstream proxy, but of course by now,
the client has thrown its toys out of the cot.

Mow this is mostly gobbledy gook to me, but I am sure the answer is in
there somewhere.

regards
 
Martyn Bright
Received on Thu Dec 16 2004 - 12:43:21 MST