501 Not Implemented
Cannot do POST is supported via CGI/API programs only. with this URL /clienttracker.pl.
Most likely, this was an attempt to execute a CGI program located in an area not configured to hold executable CGI programs. Please contact the server administrator at
I assume that I put the script into the cgi-win directory. Does anyone have any ideas? Need more information?
Thanks,
Eric
#!/usr/local/bin/perl /*or what ever*/
Are you sure it is correct?
-- Zak
A quick search on "501 error" provides a number of similar problems mentioning domain and IP issues on Win-NT. Check that out.
I suspect that your script is terminating early when it receives no parameters and doesn't even run the code that produces the error.
Your script may also be written to accept GET but not POST.
My suggestion is to run that script from the browser to eliminate the command window and output redirection issues.
Run it with no parameters first:
[domain.com...]
Then run it with command line parameters:
[domain.com...]
Then try to POST to it from an HTML form.
The standard PERL code to accept a POST is:
sub ParseForm {
read ( STDIN, $buffer, $ENV{'CONTENT_LENGTH'} );
@pairs = split( /&/, $buffer );
foreach $pair ( @pairs ) {
( $name, $value ) = split( /=/, $pair );
$value =~ tr/+/ /;
$value =~ s/%([a-fA-F0-9][a-fA-F0-9])/pack("C", hex($1))/eg;
$value =~ s/~!/ ~!/g;
$form{$name} = $value;
}
}
Check if something like that is in there.
If all that fails to enlighten you...
One brute-force method for identifying the line that's causing an error in a third-party script is "DROP the STOP":
print "Content-type: text/html\n\nOK\n\n"; exit;
Systematically move that line down your script and keep running it until you get the error.
The bad line will be just above it.
website pro perl [groups-beta.google.com]
shows a ton of old discussions of people having issues getting perl scripts to work with this webserver.
there is nobody out there who knows how this webserver works?
Regrettably I've had LOTS of experience with them, but the problem is it's too complex to communicate what you need to do in a post. Plus there are things I'd rather forget. :-)
Either you have to be an administrator or able to VNC into the box. Dig around long enough and you'll find setup areas/programs for managing the domains and specifically the properties and directories of each domain. Once you find it, it's like any other windows program, you right-click the object to access properties (be it a domain or directory) and set permissions accordingly. There's a GUI somewhere where you also determine WHICH extensions are executable as scripts. I think that's the absolute worst part about trying to develop on a Windblows server, from FTP you have no ability to control permissions, it has to be done by an admin.
Mail presents some . . . issues as well.
Sorry for not having more, but a lot of it has faded in memory.
The server does not report syntax errors in your code the way Apache would, so if your code still has problems you will need to turn on logging and attempt to decode what went wrong from the output( if there is any ).
