Re: Porting DC-Dot to Windows

Try to leave only

print "Content-Type: text/html; charset=UTF-8\n\n";
[download]

before the actual output. The HTTP headers are sent by the webserver itself.

UPD:
If this does not help, try the following script:

print "Content-Type: text/plain; charset=UTF-8\n\n";
print "Hello, world!\n";
[download]

and describe what happens. Of course you may need to add a proper shebang line to the top of your script.

s;;Just-me-not-h-Ni-m-P-Ni-lm-I-ar-O-Ni;;tr?IerONim-?HAcker ?d;print

Comment on Re: Porting DC-Dot to Windows Select or Download Code

Replies are listed 'Best First'.
Re^2: Porting DC-Dot to Windows by willyyam (Priest) on Jul 17, 2006 at 20:31 UTC
The first suggestion, to leave off the HTTP response header, didn't change my result. The second suggestion provides meaningful feedback though. I built the Hello World script as you suggested, and it would not execute with the name "test.pl" - I got the same error as before. However, when I changed the extension to cgi, I got a web page with the content "Hello, world!", which is very exciting. I changed the extention of dcdot.pl to dcdot.cgi, but I get the same error. I cleared the cache and tried again, in case, but still not joy. Still, this confirms that I have IIS configured to interpret Perl scripts, which is a good first step.	[reply]
Re^3: Porting DC-Dot to Windows by Ieronim (Friar) on Jul 17, 2006 at 22:12 UTC
Your script can die from an unexpected error. Try `CGI::Carp qw(fatalsToBrowser)`. Your script can generate warnings before the headers are printed. Some webservers break the execution of the script in this case. Check the output of your script again! `Content/type...` must be the first line it prints. `s;;Just-me-not-h-Ni-m-P-Ni-lm-I-ar-O-Ni;;tr?IerONim-?HAcker ?d;print`	[reply] [d/l] [select]