[ale] A new web server

Ken Ratliff forsaken at targaryen.us
Sun Jan 18 18:21:43 EST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jan 18, 2009, at 3:47 PM, Terry Bailey wrote:

> The web server logs seem to be OK.
>
> I am using Apache on Centos 5.2 64 bit.  I am assuming that since
> Apache came as a non-add-on that it is also 64 bit and not in some
> emulation mode.
>
> What refuses to load sometimes are some of the gif and jpg files.  If
> you do a refresh on the browser, they come down immediately. This is
> true with different browsers.

Right, I got that part - My original question still remains. Are the  
server logs returning a 200 on the requests which don't actually show  
images, or are they displaying a 304?

For example -
192.168.1.50 - - [18/Jan/2009:14:02:06 -0500] "GET /images/bggrad.jpg  
HTTP/1.1" 200 415 "http://narco.noctum.net/style.css" "Mozilla/5.0  
(X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121621 Ubuntu/8.04  
(hardy) Firefox/2.0.0.11" "-"
192.168.1.50 - - [18/Jan/2009:14:04:16 -0500] "GET /images/bgbody.jpg  
HTTP/1.1" 304 - "http://narco.noctum.net/style.css" "Mozilla/5.0 (X11;  
U; Linux i686; en-US; rv:1.9.0.5  Gecko/2008121621 Ubuntu/8.04 (hardy)  
Firefox/2.0.0.11" "-"

In the first case, it tells me that it returned a 200, and sent 415  
bytes, and in the second, it was cached and returned a 304. I have  
seen instances of a webserver returning a 200 result code, but  
transferring 0 bytes, which is why I'm curious if that's the case here.

> This is a new box running a Xeon dual core with 4 gigs of RAM.
>
> My old server, running Apache, had only 512 of RAM and had a clock
> speed of 450 Megahertz. It served out this Web site just fine.

> I have a computer on my local area network that is running Fedora 9
> with Apache.  So, I downloaded the Web server data, keeping the same
> file structure, to it.  It works just great!

Well that means it's likely not an apache configuration problem, and I  
doubt it's hardware as well. So it's probably something in the OS.

Usually when I see weird crap like this, it's a permissions issue, and  
usually after I've already started tearing my hair out because I  
assumed that permissions couldn't possibly be the problem! :) I've  
also seen some strange behavior come about as the result of funky  
rewrite rules.

But check the apache error log as well.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (Darwin)

iEYEARECAAYFAklzuYsACgkQXzanDlV0VY5OogCfQxTlNmhAEFdVVw2zUAkHkuH1
DfwAn1MM8jLFNAvRvpPhtRNDHiFHGWzx
=cj6l
-----END PGP SIGNATURE-----



More information about the Ale mailing list