Last update: 2008-03-01
Never argue with an idiot. They drag you down to their level, then beat you with experience
- Anonymous
AddonDoc2 1.1
ChangeDateNew 3.5.6
Chmod 0.2
CopyNews 0.4
CustomFields 1.0
EasyEdit 1.0.1
EmptyProfile 0.6.1
FieldIncluder 1.0
Filter By Field 2.1
Full Profile Build 1.0
IsNewValue 0.1
Link Validator 1.3
Maginot Columns 0.3
Maginot Line Build 17
Modify News : Missing Subject 0.1.2
Multipart 1.59
NewFiles 1.1
NewsCounter 0.4
NumericNewsID 0.2
Prisoner's Dilemma build 2
Profile Numeric Filter 0.1.2
QueryFetcher 0.2
Random News 1.2
Search And Replace 1.0
ShadowMail 2.2
Snipper 1.0.1
SortOrders 2.3
Style Debugger 0.2
Top Bottom News Fields 0.1
X Multisubmit 2.4.3
Weberver & Perl Errors
If you have found my guidance here or in the Coranto forums helpfull or is using one of my addons and liked it here is your chance to materially support and encourage me to spend time helping others and keep developing existing and future addons to Coranto. Please note that this is a donation and not payment, what I do with my free time is up to me!

Eduardo Pedreņo
Ken Edwards (mavmesa)
Jesse Walden
Michio Takagi
:. 500 - Internal Server Error 2004-07-17

Basically this can mean anything, it is just the webserver indicating that something has gone wrong and that you should look in the webservers error log for more details.

If you have access to the errorlog, fine, if you donīt you are kind of blindfolded in a dark room when something goes wrong and you need to trace down the error. Personally, since I am a coder, I really canīt see myself using a webhost that doesnīt provide me with access to the webservers errorlog but I know this is quite common.

If you are in the situation where you donīt have access to webservers errorlog you could try and upload this script (provided by courtesy of LoneOwl) to your webservers cgi-bin directory and execute it. Make sure you have the chmod settings right!

Anyway, the message in the errorlog should give you a pointer of what is wrong and how to fix the problem. If not, the steps mentioned in the "Premature end of script headers"-section can be applied to this problem as well.

If the problem still canīt be solved, it might be a problem with the end of line character. This is often the case if you are running on a Linux server (at home maybe?) and use your Windows machine to edit and upload the files to the server from.

In particular, Apache on Red Hat has been known to be complaining even if the files are being uploaded in ASCII mode but this can be remedied by adding "-w" at the end of the shebang line like so:

#!/path/to/perl -w

Another way to handle the situation is to use a texteditor where you can specify the target operating system when saving the file. The Unix file format should then be used.

If you still canīt figure out why you receive this message post a message in the forum, stating that you have read this document and explain what measures you have taken thus far to pinpoint the problem.

Tell a friend   Print article   Comment this one!   Parahead
9 visitors online Valid HTML 4.01!   Valid CSS! © copyright 2003 Henrik Ahlén
Design based on Stylish by MVS
Content powered by Coranto