> I don't see anything weird about the HTTP request. Try
> creating a dummy file, like /foo.txt, containing just a
> few ASCII characters, and see if you can reproduce the
> problem with that URL. If so, post a tcpdump of that.
In the tcpdump thats I posted in the last hour, the first hit
returned the image (and response 200) but it was never logged .
The second hit was when I clicked the refresh button and it
returned 304 and WAS logged. It works the same way with text
files.
This is the only log entry:
66.62.93.30 - - [01/Aug/2003:08:51:08 -0700] "GET /desertdawn.jpg
HTTP/1.1" 304 0 "" "Mozilla/4.0 (compatible; MSIE 6.0; Windows
98; Q312461)"
Also, no log entry of you downloading the tcpdump file (just the
incorrect url you tried)
24.153.164.125 - - [01/Aug/2003:09:19:53 -0700] "GET /tcpdump.ou
HTTP/1.0" 404 531 "" "Wget/1.8.2"
url: http://www.avenues.org/desertdawn.jpg
tcpdump: http://www.avenues.org/tcpdump.out
nsd.tcl: http://www.avenues.org/nsd.tcl (snippet of nslog
section)
Daniel P. Stasinski
Software Engineer
Mayor Pharmaceutical Laboratories
[EMAIL PROTECTED]
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
