Server HTTP status codes and the problem with a 500 Internal Server Error.
Servers and browsers communicate through so-called server headers or HTTP status codes. When a browser requests a particular page, the server that is responsible for showing that specific webpage returns an error code or status code that gives you information about how the server has handled it.
The 500 Internal Server Error is one of the most common error messages and doesn't say anything more than that something is wrong. It is often the response of one of your AJAX calls. The problem is most often one of the following four.
- Fatal error: Debug your script until you know exactly which line is the reason for this internal server error. The script has been halted and reached a fatal error, which prevents the script from continuing.
- Permissions: The read, write and execute permissions (changed by chmod) or ownership for a particular script (changed by chown) have not been set correctly.
- Wrong directory: CGI scripts have to be stored inside the CGI-BIN directory.
- ASCII upload mode: Saving a file on Unix in ASCII mode makes Unix interpreting it incorrectly.
At W3.org you can find a complete list of all server headers or HTTP status codes.
Would you like to comment?
Fields with * are obligatory.
Save