This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: httpd2 causes 100% server for few seconds _after_ request completed

Hello Guys,

OK, new day and new details ;) Sorry, a bit long, but they might
be helpful...
Honestly I don't know any better way to monitor windows's
activity than ProcessExplorer, so I'm adding it's screenshot
to demonstrate what happening on my system. Of course cygcheck's
output from W2K3 server attached as well, but I'm seeing this
on all my computers, including fresh W2K installation.

W2K3 Server with TS activated. Fresh installation of httpd2, only
one change in httpd.conf file - log format changed from common
to combined. I'm quering http://localhost:80/ and see default
<html><body><h1>It works!</h1></body></html> message 44 bytes long.

Not it turns to be really interesting. I've tried the page above
with different browsers - IE6, Mozilla, Opera 9.01 and curl.
All browsers already in memory and I'm just refreshed page.

Take a look at access_log - - [28/Oct/2006:13:17:40 +0300] "GET / HTTP/1.1" 304 - "-" "Mozilla/5.0 (Windows; U; Windows NT
5.2; en-US; rv: Gecko/20060909 Firefox/" - - [28/Oct/2006:13:18:25 +0300] "GET / HTTP/1.1" 304 - "-" "Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.2; iOpus-I-M; .NET CLR 1.1.4322)" - - [28/Oct/2006:13:19:20 +0300] "GET / HTTP/1.1" 200 44 "-" "Opera/9.01 (Windows NT 5.2; U; en)" - - [28/Oct/2006:13:19:20 +0300] "GET /favicon.ico HTTP/1.1" 404 209 "-" "Opera/9.01 (Windows NT
5.2; U; en)" - - [28/Oct/2006:13:19:36 +0300] "GET / HTTP/1.1" 200 44 "-" "curl/7.15.4 (i686-pc-cygwin)
libcurl/7.15.4 OpenSSL/0.9.8b zlib/1.2.3"

and on the picture:

First peak load (on picture) was after request with Firefox, second,
narrower, after Explorer6 and there's nothing (!) after requests with
Opera and curl.
I've noticed that both FF and IE get 304 (not modified) responce code,
but it doesn't seem to affect server behaviour at all, even with usual
code 200 and actually transferred data impact on server exactly the

I thought there must be some differences in requests to Apache from
different browser (and how Apache treat these requests) so I dumped
FF request and Apache response and then replayed them with curl.
I've created exactly the same request with exactly the same headers
and got exactly the same answer. 100% load with FF and nothing like
this in case of curl. Maybe there's some other factors involved, don't
know what it could be.

I'm stuck on this so far...

Any ideas ?

Sergei Kolodka

Attachment: cygcheck.out
Description: Binary data

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]