Re: [AOLSERVER] IM'ed URLs not being logged

2003-08-01 Thread Dossy
On 2003.08.01, Daniel P. Stasinski [EMAIL PROTECTED] wrote:
   Capture the entire HTTP request that isn't logged,
   using tcpdump -s 2000 -w tcpdump.out port 80 or
   similar. Give us a URL to download tcpdump.out
   so we can examine it.

 http://www.avenues.org/tcpdump.out

Is this file supposed to be 269 bytes?  It looks like it just contains a
HTTP request.  Where's the tcpdump data itself?

-- Dossy

--
Dossy Shiobara   mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
  He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on. (p. 70)


--
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.


Re: [AOLSERVER] IM'ed URLs not being logged

2003-08-01 Thread Daniel P. Stasinski
  Is this file supposed to be 269 bytes?  It looks like it
  just contains a HTTP request.  Where's the tcpdump data
  itself?

Sorry, try again.

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.


Re: [AOLSERVER] IM'ed URLs not being logged

2003-08-01 Thread Rob Mayoff
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.


--
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.


Re: [AOLSERVER] IM'ed URLs not being logged

2003-08-01 Thread Daniel P. Stasinski
  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.


Re: [AOLSERVER] IM'ed URLs not being logged

2003-08-01 Thread Rob Mayoff
+-- On Aug 1, Daniel P. Stasinski said:
| 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.

Sounds like you need to put AOLserver under the debugger and step
through a request.


--
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.


Re: [AOLSERVER] IM'ed URLs not being logged

2003-07-31 Thread Daniel P. Stasinski
  You mean when they click on the URL in the IM they receive
  and the browser goes to fetch the image, the nsd/nslog never
  logs the HTTP request?

Correct.

  Is this reproducible?  Always?  For any image, or specific
  images, or image types?  Is it dependent on the recipient of
  the IM?

I have pasted URL's in AIM and on irc, and also typed in the
specific url into the url box on IE 6 and Linux/Mozilla and in
each case it was not logged.  This is consistent behavior.  If I
hit refresh, it does log it.  Also, the browsers caches are clear
so I know it's not a caching problem.  This is true with both
jpegs and gifs.  I don't have any URL handling code/filters that
might be blocking it.  All of the images are the root page
directory.

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.


Re: [AOLSERVER] IM'ed URLs not being logged

2003-07-31 Thread Rob Mayoff
+-- On Jul 31, Daniel P. Stasinski said:
| I have pasted URL's in AIM and on irc, and also typed in the
| specific url into the url box on IE 6 and Linux/Mozilla and in
| each case it was not logged.

Capture the entire HTTP request that isn't logged, using tcpdump -s
2000 -w tcpdump.out port 80 or similar. Give us a URL to download
tcpdump.out so we can examine it.


--
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.