Topic awaiting preservation: AGGHH!!! =( 405 Error!!!!!!1 (Page 1 of 1)

I am about to go crazy over here!!!!!

I have a form, its a windows server, and it gives me 405 error Method not allowed check your MIME crap message..

I tried everythign!!!!!!!!!!!!! what the hell could be wrong???????

MAX

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

sorry =)

Here is the page: http://www.hometownusatitle.com/order.html

and I am using Matt's Wrights Perl Script...

here is the script where you edit it..

# Define Variables #
# Detailed Information Found In README File. #
# There is no need to modify $mailprog in the Devmailer version of formmail. #
# #
# $smtp_server is name of your SMTP server. If you do not have your own, #
# you can put your ISP's smtp server. This is where all the mail will be #
# relayed. #
#
# For Exchange and Lotus Notes / CC Mail servers this is the IP address to #
# your SMTP gateway.

$smtp_server = "smtp.buckyeweb.com";

# $mail_admin defines the e-mail address that should be used as the #
# SMTP envelope sender address. This will be the address to which #
# FormMail-generated messages will be bounced if they are ever found #
# to be undeliverable for any reason. NOTE: This should be some #
# e-mail address that is ROUTINELY and FREQUENTLY monitored. #

# NOTE! NOTE NOTE! RFC 2821 absolutely _requires_ every mail server to
# have a working postmaster e-mail address. If you don't have one then
# for God's sake GET ONE! This means YOU!

$mail_admin = "molly@hometownusatitle.com";

# @recipient_addresses defines the e-mail addresses that e-mail can #
# be sent to. This must be filled in correctly to prevent SPAM and allow #
# valid addresses to receive e-mail. Read the documentation to find out how #
# this variable works!!! It is EXTREMELY IMPORTANT. #

@recipient_addresses = (molly@hometownusatitle.com);

# @recipient_domains defines the e-mail domains that e-mail can #
# be sent to. This must be filled in correctly to prevent SPAM and allow #
# valid addresses to receive e-mail. Read the documentation to find out how #
# this variable works!!! It is EXTREMELY IMPORTANT. #

@recipient_domains = (www.hometownusatitle.com);

# ACCESS CONTROL FIX: Peter D. Thompson Yezek #
# @valid_ENV allows the sysadmin to define what environment variables can #
# be reported via the env_report directive. This was implemented to fix #
# the problem reported at http://www.securityfocus.com/bid/1187 #

@valid_ENV = ('REMOTE_HOST','REMOTE_ADDR','REMOTE_USER','HTTP_USER_AGENT');

# Devmailer version compatibility. #
# Versions before Devmailer 1.5 do not have the AddMultipleRecipients #
# method, which allows for specifying multiple recipients in the RECIPIENT #
# HTML field (as a comma or semicolon delimited list of addresses). #
# If you are using a version prior to 1.5, set $usingOldDM = 1. #
# Otherwise its best left alone. #

$usingOldDM = 0;

# Devmailer Log Level: The range of values are from 0 (no logging) to 4 #
# (verbose) 2 is the default LogLevel for Devmailer

$dmLogLevel = 2;

# Default From Address: Most SMTP servers require a valid and fully #
# sender's address. You can specify this with the EMAIL input tag, but #
# if you would rather have a default, you can specify it here. #

$dmFromAddress = 'FormMail@mydomain.com';

# Done #
##############################################################################

MAX

[This message has been edited by Ducati (edited 07-05-2002).]

Apparently, you didn't install that script correctly. If you type address of the script directly in address bar (i.e. http://www.hometownusatitle.com/cgi-bin/order.pl ), and try to access it, you'll get complete script source, which means that script cannot be executed for some reason...

so you think its a permissions fault on the cgi-bin directory?

MAX

Something like that. You should contact your system administrator...

cool.. thanks Max...



MAX

It's a windows box you sure perl is even installed?



.:[ Never resist a perfect moment ]:.

yes.. it is installed....

MAX

Hi Ducati,

Does the script have a shebang line at the very top? It looked like it was missing from the source. You're also going to have a problem with this bit of code:

# Retrieve Date

e"t_date;

I'm guessing it should be:

# Retrieve Date

&get_date;

Regards,
Charlie

[This message has been edited by Piper (edited 07-05-2002).]

I thought Windows Server doesn't need schebang thing?????

MAX

It really depends on how you have it set up and what www server you run. If you have .pl and .cgi files associated with the perl binary and you're running IIS then you shouldn't need it. Do you have other perl scripts running correctly on this server? Have you tried renaming the script to order.cgi?

~CP

yup.. I tried both... cgi and pl

nothing works... =(

MAX

I think you're on the right track. It downloads now instead of displaying the source code in the browser You need to fix your shebang line still. You have C:\Perl and it should be more like #!C:/perl. You also have a problem with one of your array defs. Look for this line (about line 105): @recipient_addresses = (molly@hometownusatitle.com); and change it to @recipient_addresses = ['molly\@hometownusatitle.com'];. That's all I had to do to get it working for me locally. There are LOTS of other problems with this particular script though, you might consider taking a look at a more secure alternative here: http://nms-cgi.sourceforge.net/ . This server is running IIS, correct?

~CP

The script still doesn't work for me (source code is showed directly in web browser).

Now, under IIS shebang line is not used at all (so it is unnecessary). It is only used on Unix systems and by Apache under Windows systems. So, that's not the problem. Script cannot be executed for some reason, and as I've already said, Ducati, you should contact your system administrator.

BTW1 Syntax errors are a completely different thing. They don't have any influence on script execution. If there are syntax errors, web server will show "500 Internal Server Error" message, but it will still execute the script (it won't show its source).

BTW2 Ducati, since that web site is running under IIS, why don't you consider using ASP?

Piper... I think its Apache under Windows machine...

Max: I can't use ASP... they want this one

I will fix those and see if it works ;D

MAX

I've just checked www.hometownusatitle.com domain and it is running under MS IIS 4.0, so it's not Apache...

damn, I thought I was the only one who noticed the missing shebang line...


Code - CGI - links - DHTML - Javascript - Perl - programming - Magic - http://www.twistedport.com
ICQ: 67751342

I think Mr. Max hit the nail on the head, you need to contact your admin. I don't think IIS is properly configured to run perl scripts on this server. As long as you take care of the errors that were poited out, this script should run without any problems.

~Charlie