Comments on HTTP Status Codes Explained - AddedBytes.com

Comment on HTTP Status Codes Explained

Comment by Jessica ( )

I recently installed apache 2.2.6, with ssl on Solaris 9. It's a pretty standard install.
In my access log, I see entries like this every couple minutes:

127.0.0.1 - - [03/Nov/2007:15:46:41 +0000] "GET /" 400 480
127.0.0.1 - - [03/Nov/2007:15:46:42 +0000] "GET /" 400 480
127.0.0.1 - - [03/Nov/2007:15:46:52 +0000] "GET /" 400 480
127.0.0.1 - - [03/Nov/2007:15:46:53 +0000] "GET /" 400 480
127.0.0.1 - - [03/Nov/2007:15:46:54 +0000] "GET /" 400 480

I didn't start seeing this until I modified my http.conf from
CustomLog logs/access_log common
to
CustomLog logs/access_log combined
(I wanted more information in logs for webalizer to have good
reports)

What would cause these log entries?

Thanks!

Comment on HTTP Status Codes Explained

Comment by bbq ( http://www.myideology.cn/ )

Great! I need your help!

And I have linked your address in my blog! :)

Comment on HTTP Status Codes Explained

Comment by New to This Stuff ( )

I have a site where I have .exe files available for download. Some of the files are quite large. I see lots of 200 and 206 status codes among others. Is there anything I can do to determine exactly how many FULL copies were successfully downloaded? Would a 200 status code indicate that? Could multiple 206 codes from the same IP indicate a successfull download of a FULL copy?

Thanks.

Comment on HTTP Status Codes Explained

Comment by Jeff Johnson ( )

Here's where to set the max request-URI length in Apache 2.2:

http://httpd.apache.org/docs/2.2/mod/core.html#limitrequestline

Thought this might help some of you.

Comment on HTTP Status Codes Explained

Comment by Mike ( http://ezrstats.org )

Good information - thank you. I'm not encountering an HTTP 414 error until about 6-8,000 characters in the URL (using 1and1.com managed server. (I use long URI to upload data).

Comment on HTTP Status Codes Explained

Comment by LeeTK ( http://www.leetk.com )

Thanks for so complete Http error info

Comment on HTTP Status Codes Explained

Comment by Hohn A. Parker ( )

Great post(s)!

I have a "slightly" unrelated question if I may...

We have a situation (which I've been tasked to fix of course!) where a custom mod is behaving badly and causing apache to appear hung. (Before you ask :-): No, I dot not have the swag to make them fix the thing. I have to live with, detect and create an axe to recover from the behavior.) By hung I mean connect but not respond. Most of the time this means apache's active process count incrementally grows until it reaches its configured max. But not always.

Can you suggest a programmatic way of testing a server (apache or otherwise) to see if it is "hung"?

Thanks in advance!

John

Comment on HTTP Status Codes Explained

Comment by sqeaky ( http://www.freetechupport.us )

Curtis if someone is just using prebuilt scripts to attack your server, simple use of best practices with thwart them every time. Patch your software in a timely fashion, have a tightly configured firewall, and make sure to use secure Remote administration tools, like SSH, and a script kiddy will be left out in the cold. However a more determined hacker, might use your server to find a day 0 exploit, but this is unlikely and is a risk all webmasters share.

Comment on HTTP Status Codes Explained

Comment by sqeaky ( http://www.freetechupport.us )

I used this to generate a set of error pages for each response over 500, Thanks!

Comment on HTTP Status Codes Explained

Comment by Travis Finucane ( http://www.finucane.org/ )

Rahul, download the source of thttpd from http://www.acme.com/software/thttpd/. Then modify libhttpd.c to add whatever status titles you wish. Compile it. Create a cgi with a Status: XXX header.

Of course, this doesn't mean the server is actually behaving as it should. For example 206, should really only be returned if the request only asks for partial content, and it should actually return the bytes specified by content-range.