Hi Mark, Is this the tcpdump you were after? Our web service (which our .NET client application at Deakin University is trying to call through their Squid proxy) is at http://services.qsrinternational.com cheers, Marcus > Hi Marcus, > > Sorry for the delay, took a while to organise with our sysadmin. The > following the tcpdump you requested. > > 14:26:29.944471 IP 128-184-148-120.its.deakin.edu.au.1239 > felix.its.deakin.edu.au.squid: S 431603593:431603593(0) win 65535 <mss > 1460,nop,nop,sackOK> > > E..0..@........x.......8........p...~........... > 14:26:29.944658 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 3551896320 win 65535 > > E..(..@........x.......8........P...4......... > 14:26:29.946638 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: P 0:384(384) ack 1 win 65535 > > E.....@....m...x.......8........P.......POST > http://services.qsrinternational.com/ > 14:26:29.948167 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: P 384:1714(1330) ack 1461 win 65535 > E..Z..@........x.......8... > > ....P....p..<?xml version="1.0" encoding="utf-8"?><soa > 14:26:29.948524 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 4381 win 65535 > > E..(..@........x.......8...<....P.... ........ > 14:26:29.948877 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 7301 win 65535 > > E..(..@........x.......8...<....P............. > 14:26:29.949114 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 10221 win 65535 > > E..(..@........x.......8...<....P....9........ > 14:26:30.102041 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 11447 win 64309 > > E..(..@........x.......8...<....P..5.9........ > 14:26:38.114901 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: P 1714:2098(384) ack 11447 win 64309 > > E.....@....b...x.......8...<....P..5.'..POST > http://services.qsrinternational.com/ > 14:26:38.116810 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: P 2098:3428(1330) ack 12907 win 65535 > > E..Z..@........x.......8.......jP....*..<?xml version="1.0" encoding="utf- > 8"?><soa > 14:26:38.116875 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 15617 win 65535 > > E..(..@........x.......8........P....r........ > 14:26:38.117291 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 18537 win 65535 > E..(..@........x.......8.......hP.... > > ........ > 14:26:38.117521 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 21173 win 65535 > > E..(..@........x.......8........P............. > 14:26:38.117658 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: . ack 22893 win 65535 > > E..(..@........x.......8.......lP............. > 14:26:38.140319 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: P 3428:3865(437) ack 22893 win 65535 > > E.....@...."...x.......8.......lP.......POST > http://services.qsrinternational.com/ > 14:26:38.140564 IP 128-184-148-120.its.deakin.edu.au.1239 > > felix.its.deakin.edu.au.squid: R 3865:3865(0) ack 22893 win 0 > > E..(..@........x.......8.......lP....M........ > 14:27:11.531696 IP 128-184-148-120.its.deakin.edu.au > win- > f.its.deakin.edu.au: icmp 40: echo request seq 7936 > > E..<...........x.......^....ABCDEFGHIJKLMNOPQRSTUVWABCDEFGHI > 14:27:11.532078 IP 128-184-148-120.its.deakin.edu.au.1242 > win- > f.its.deakin.edu.au.microsoft-ds: S 2119852512:2119852512(0) win 65535 > <mss 1460,nop,nop,sackOK> > > E..0..@........x........~Za.....p....c.......... > 14:27:11.532305 IP 128-184-148-120.its.deakin.edu.au.1242 > win- > f.its.deakin.edu.au.microsoft-ds: . ack 3591166814 win 65535 > > E..(. @........x........~Za....^P............. > 14:27:11.532395 IP 128-184-148-120.its.deakin.edu.au > win- > f.its.deakin.edu.au: icmp 40: echo request seq 8192 > E..<. > > .........x......-^.. .ABCDEFGHIJKLMNOPQRSTUVWABCDEFGHI > 14:27:11.532511 IP 128-184-148-120.its.deakin.edu.au.1242 > win- > f.its.deakin.edu.au.microsoft-ds: P 0:137(137) ack 1 win 65535 > > E.....@....Q...x........~Za....^P...4........SMBr.....S................. .... > .b..PC > 14:27:11.533969 IP 128-184-148-120.its.deakin.edu.au.1242 > win- > f.its.deakin.edu.au.microsoft-ds: . 137:1597(1460) ack 185 win 65351 > E.....@....$...x........~Zbj....P..G...... > z.SMBs.........BSRSPYL ........@....z > . > 14:27:11.534066 IP 128-184-148-120.its.dea > > > hope this is what you require. > > Regards, > Shannon -----Original Message----- From: Mark Nottingham [mailto:mnot@xxxxxxxxxxxxx] Sent: Friday, 20 October 2006 1:29 PM To: Marcus Ogden Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: HTTP protocol violation error using .NET 2.0 web services through Squid-2.5 proxy Hi, Can you post a trace (e.g., tcpdump, tcpflow) of the interaction between .NET and Squid? Just headers is fine. I'd be very interested to see what's happening here... Thanks, On 2006/10/19, at 4:42 AM, Marcus Ogden wrote: > Hello, > > A client of ours using the Squid proxy server (version > 2.5.STABLE6-3.4E.12.1) on Red Hat Enterprise Linux 4 is experiencing a > problem when running our .NET 2.0 client application, which > communicates > with a .NET 2.0 web service on our server. > > When our client application sends an HTTP 1.1 request through the > Squid > proxy to our server, it receives the error: > > "The server committed a protocol violation. > Section=ResponseStatusLine" > > Other clients not using Squid are not experiencing this problem. > > Researching this, we've found a few posts that report similar problems > using .NET 2.0 web services and/or the HTTP 1.1 protocol through > Squid, > e.g. > > http://forums.asp.net/thread/1194960.aspx > http://groups.google.to/group/ > microsoft.public.dotnet.framework.remoting > /msg/dae1a8e9eed3dcf3?dmode=source > http://www.squid-cache.org/mail-archive/squid-users/200606/0534.html > > We've also tried the suggestion in > http://forums.asp.net/thread/1284850.aspx to set the > useUnsafeHeaderParsing property in the client .NET application's > config > file to "true", but our client reports this hasn't solved the problem. > > Any suggestions on how we can resolve this issue would be much > appreciated. > > Regards, > > Marcus Ogden > Software Development > QSR International > www.qsrinternational.com > > -- Mark Nottingham mnot@xxxxxxxxxxxxx
