I am currently in the process of developing a website and getting all the bugs out. On my order form page I continue to receive the following error whenever I submit the form:

Method Not Allowed
The requested method POST is not allowed for the URL /assuretech/cgi-bin/secure.pl.

I have gone in circles with my technical support regarding this issue and they have no idea what it is. They continue to say it has something to do with the Perl script I am using but the only time I get this error is when I am referencing my host's secure server (https://host5.avidhosting.com). If I just call the script from my cgi-bin (cgi-bin/secure.pl) I don't have any trouble. I have spent several hours reading articles on the Internet in regard to this 405 error and from what I have gathered this issue is a misconfiguration on the server that the admin needs to resolve. Is this correct? Is there anything on my end that I may be doing wrong?

The url for the order form is here: (http://www.assuretech.net/dataform/order.htm).

If anyone could help me figure this out, I would be very thankful.

Travis

Yes, it's a server configuration problem. I'm guessing that you're on Windows NT?

It seems that your host needs to set the "verbs" for the .pl extension to include POST. It can be set through the properties dialog box of a virtual directory by pressing the Configuration button (I'm sure they'll know how to do it). I'm not entirely sure whether it would need to be set for individual directories, or whether the changes made would affect all directories.

This site is being hosted on an Apache server running on the Linux platform. Do you know what the configuration would be for this vs. NT or is the above mentioned solution the same?

Travis

It's something in the Apache configuration file then, or perhaps in a .htaccess file of the directory your script is in. You can set acceptable methods using those files.

But I'm not an expert there (or on IIS for that matter). Someone around will know.

Well my technical support finally solved the problem. There was an incorrect entry in the secure config file for apache.

To access a cgi-bin it we must add a line
ScritAlias aliasname actualdirectory

This has to be there for the apache-ssl too... This is usually missed out and hence the problem...

Have a great day :)

regards
amar