File socket trasmission errors in Apache/2.0.28 (Win98)

["William A. Rowe, Jr." <wr...@covalent.net>]

From: "Shard" <sh...@hotmail.com>
Newsgroups: comp.infosystems.www.servers.ms-windows
Sent: Tuesday, November 20, 2001 2:02 AM
Subject: Re: Maximum filesize in Apache/2.0.28 (Win32)


> > "Shard" <sh...@hotmail.com> wrote in message news:3b01138b.0111190000.47bfe83f@posting.google.com...
> 
> > > I'm currently running Apache version 2.0.28 on Windows 98. It is
> > > running perfectially with php enabled, except any file of size 7888 or
> > > larger returns an error web page. Plain text or another file type.
> > > Small images and text will display if they are 7887 bytes or less, but
> > > anything over will give an immideate error page.
> > >
> > > Server error!
> > > The server encountered an internal error and was unable to complete
> > > your request. The server is either overloaded or there was an error in
> > > a CGI script.
> > > If you think this is a server error, please contact the Webmaster
> > > Error 32545
> 
> There is no filewall at all.
> 
> "William A. Rowe, Jr." <wr...@lnd.spam.not.welcome.net> wrote in message news:<9t...@dispatch.concentric.net>...
> > Does the default page (index.html.en) show up correctly, without any
> > php filtering or cgi invocation?  [It is smaller than 7kb.]
> 
> > Bill
> 
> The index.html.en works perfectially. The main page shows up and so
> does the image.
> 
> > That's not the system error... please dig into error.log and let us know
> > _exactly_ what messages appeared in there for these requests?

Actually, this is the system error [outch!]  We shouldn't be sending things
like 32545 as HTTP response codes, yet we still are [thought that bug was fixed.]


> > Does the size you mention apply to the -response- or the -script-?
> 
> There is no actual script running, thats one thing that has me a bit
> confused. I made a small page in plain html that displayed 2 images,
> one image 2.5k, the other 74k. I opened it locally and the page
> dislayed fine. I opened it on my server, the small file displays but
> the large one comes up with the red X instead of the picture. I
> checked error.log, and there has never been any errors placed there in
> regards to files not dislaying. I cleared error.log before trying to
> load the page, and it is still absolutially empty. If I try to load a
> non existing file it tells me in error.log, so I know it worsk.
> However it shows up in access.log like there was no problem.
> 
> 192.168.0.13 - - [20/Nov/2001:15:38:35 +0800] "GET /testsize.html
> HTTP/1.1" 200 190
> 192.168.0.13 - - [20/Nov/2001:15:38:35 +0800] "GET /apache_pb.gif
> HTTP/1.1" 304 0
> 192.168.0.13 - - [20/Nov/2001:15:38:35 +0800] "GET /testsize.jpg
> HTTP/1.1" 32545 803
> 
> Actually it does seem to give some odd numbers next to it. Here is the
> same file requested both times, but the 1st request it was 1 byte
> smaller, sitting on the 7887 threshold.
> 192.168.0.13 - - [20/Nov/2001:15:59:19 +0800] "GET /small.txt
> HTTP/1.1" 200 7887
> 192.168.0.13 - - [20/Nov/2001:16:00:41 +0800] "GET /small.txt
> HTTP/1.1" 32545 803

This request is a _huge_ hint, it looks like the sockets reuse is failing.
That is, the first request was just fine, the second (kept-alive) was the 
one that 'coughed.'

> I tested a small php file that outputted a lot. The php was 206 bytes
> but it output 195k of text. Though that same outputted text in a text
> file just gave me that overloaded server error again.
> 
> 192.168.0.13 - - [20/Nov/2001:15:54:51 +0800] "GET /meeee.php
> HTTP/1.1" 200 200074
> 192.168.0.13 - - [20/Nov/2001:15:56:05 +0800] "GET /me.html HTTP/1.1"
> 32545 803
> 
> And still error.log is empty.

That's a serious problem.  This is now logged as a bugs incident.