in reply to Server 500

A quick check with Google turn up this:
The Web server (running the Web Site) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.

This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse these logs.

This is a long way of saying that the problem is not with your code, dear Brutus, but with in your Server. (My apologies to Bill Shakespeare, but it is waaaay before coffee.)

----
I Go Back to Sleep, Now.

OGB

Replies are listed 'Best First'.
Re^2: Server 500
by JavaFan (Canon) on Apr 27, 2010 at 16:21 UTC
    Actually, in usually *is* the fault of your code. 500 is the servers way of saying "I didn't do it and I'm ok". If something goes wrong and the server knows what, it'll be more specific than returning a 500. But if it calls program, and the program dies (be it because it cannot be compiled, exits unexpectedly, doesn't generate any output, something else), then the server throws you a 500. It usually doesn't know what happened, and if it would know, it wouldn't tell you.