return codes and custom error pages

[jamestrotta]

When i look at my webstats, these are the rutrn codes which are showing up: 200, 206, 301, 304, and 404

I made a custum error 404 page which seems to be working. Code 301 seems to be an error too but how does one get a "moved permanently" error. I don't think I've moved anything. Should I make a custom error page for 301 or any of the others?

Thanks in advance for your help!

[byutj]

as long as you have 403, 404, and 500 you should be just fine, but if you want to do pages for each error your visitors get, that's cool too.

[Ddr]

Here is a listing of server error codes and what they mean:


100 - Continue
101 - Switching Protocols
200 - OK
201 - Created
202 - Accepted
203 - Non-Authoritative Information
204 - No Content
205 - Reset Content
206 - Partial Content
300 - Multiple Choices
301 - Moved Permanently
302 - Moved Temporarily
303 - See Other
304 - Not Modified
305 - Use Proxy
400 - Bad Request
401 - Unauthorized
402 - Payment Required
403 - Forbidden
404 - Not Found
405 - Method Not Allowed
406 - Not Acceptable
407 - Proxy Authentication Required
408 - Request Time-Out
409 - Conflict
410 - Gone
411 - Length Required
412 - Precondition Failed
413 - Request Entity Too Large
414 - Request-URI Too Large
415 - Unsupported Media Type
500 - Server Error
501 - Not Implemented
502 - Bad Gateway
503 - Out of Resources
504 - Gateway Time-Out
505 - HTTP Version not supported

[jamestrotta]

So what exactly is 301 moved permanently. I don't know what kind of error page to make for that one. For 404 I just look at the site map, report where the bad link was, etc.

Also byutj suggested 403 and 500. So far no one has gotten one of those, but I might as well make pages for them. Again, though, I don't know what to write.

Can anyone give some examples of error 301, or error 403 and 500 pages or tell me more about why users would see one?

[RocketJeff]

Not everything returned is an 'error code' (strictly speaking), they are return codes - some signify error, some success, some are just for information.

301 is not an error. Most of the time this is returned when the user enters http://www.eslgo.com (note: no trailing slash) - the server responds with a 301 and tells the browser to request http://www.eslgo.com/ (note: has a trailing slash). This is because directories have to have a trailing slash.

Only 4xx and 5xx are really errors, 4xx are 'Client Error' and 5xx are 'Server Errors'. I wouldn't bother with any of the 5xx and only the common 4xx errors.

If you look at HTTP Errors (http://www.modemhelp.net/httperrors/httperrors.shtml), it lists all the return codes and give a link to a little expanded information on each one.