- Error pages
- Posted by Firas D. on February 11th, 2004
What error pages is a user using a browser likely to see? In common
environments, I mean.
From what I can tell from looking at
<url:http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html>, probably just:
400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 410
Gone, 500 Internal Server Error.
Are there any you would add to the list? Keeping the total at most 8
errors. Or 10, absolute max. I'd like to trim it down to just five most
likely ones though.
I'm wondering because I'm making a collection of custom error documents.
As good a way to procrastinate as any.
- Posted by Bitmap on February 11th, 2004
Generally I always cover the 404. 500 is worth doing if you can error trap,
especially for perl.
401 if you have a password site, usually it leads to a sign up or forgotten
password page.
Those are the only three I cover (I think).
Bitmap
"Firas D." <fd-nospam-@firasd.org> wrote in message
news:c0drkn$169q05$1@ID-214165.news.uni-berlin.de...
- Posted by Firas D. on February 12th, 2004
Bitmap wrote:
So,
1: 404 (duh)
2: 403 (like when they access a subdirectory that doesn't have an index
file)
3: 410
4: 500
5: 401 (maybe)
I can't remember ever stumbling onto a page that said "400"; is it just
a behind-the-scenes thing?
- Posted by John Smith on February 18th, 2004
Firas D. wrote:
to a single script file and take appropritate action from within your
error.php (or whatever). This is what I do, and offers a relatively
painless solution to error handling in all situations, and the user never
has to know an error was even encountered on your site!
John
- Posted by Firas D. on February 18th, 2004
John Smith wrote:
You mean, send the client a 200: Ok? Bad idea!
http://fishbowl.pastiche.org/2004/01..._responsecodes
- Posted by Firas D. on February 19th, 2004
Firas D. wrote:
Since the gentleman hasn't responded, can anyone confirm that the
suggested setup would work as I assumed it would?
