So if your initial request packet isn't even getting an ACK,
it would seem that perhaps this is not happening on the server
itself, but maybe at a firewall?

At any rate, I have tried spoofing the User Agent info for
Netscape, and that doesn't seem to make a difference; I tried
manually using this request string:

GET / HTTP/1.0
Connection: Keep-Alive
User-Agent: Mozilla/4.72 [en] (Win98; I)
Host: www.cbs.com
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */*
Accept-Encoding: gzip
Accept-Language: en
Accept-Charset: iso-8859-1,*,utf-8

and got no response. Then, just to be sure, I tried the same with
curl:

curl -H "User-Agent: Mozilla/4.72 [en] (Win98; I)" -H "Accept: image/gif,
image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */*" -H
"Accept-Language: en" -H "Accept-Charset: iso-8859-1,*,utf-8" -v
http://www.cbs.com/

Still nothing. :-(

Jason Priebe
WRAL OnLine
http://www.wral-tv.com/

> Could it be something to do with HTTP 1.1? I ran a tcpdump
> on it while
> I hit the site with Netscape, and here's what it looks like
> for packets
> 5, 6, and 7:
>
> No. Time Source Destination
> Protocol
> Info
> 5 2.030504 bugsy 63.240.56.20
> HTTP
> GET / HTTP/1.0\r\n
> 6 2.163558 63.240.56.20 bugsy
> TCP
> www > 2414 [ACK] Seq=1972092872 Ack=1687383820 Win=31777 Len=0
> 7 2.182229 63.240.56.20 bugsy
> HTTP
> HTTP/1.1 200 OK\r\n
>
>
> Now, if I run curl against the same URL, here are packets 6 and 7:
>
> No. Time Source Destination
> Protocol
> Info
> 6 0.203790 bugsy 63.240.56.20
> HTTP
> GET / HTTP/1.0\r\n
> 7 3.201028 bugsy 63.240.56.20
> HTTP
> GET / HTTP/1.0\r\n
>
>
> So, my guess is that cbs.com maybe has some agent identifier in there,
> and if you don't match an accepted string value, you get the
> black hole
> of death?
>
> -te
>
> --
> Troy Engel :: KeyID DF3D5207
> Perl is just another tool in the Unix toolbox. Perl does one thing,
> and it does it well: it gets out of your face. - Larry Wall
>
Received on 2000-09-19