Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CGI fails when document root path contains spaces #342

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 1 comment
Open

CGI fails when document root path contains spaces #342

GoogleCodeExporter opened this issue Mar 16, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. download and install MoonGoose
2. download and install Perl interpreter (I use TinyPerl)
3. edit MoonGoose config file :
4. set cgi_interpreter to the path where the Perl exec is located on your 
filesystem
5. uncomment the cgi_pattern line
6. create two folders : "test_one" and "test one"
7. in each folder, create a simple HelloWorld CGI script (print 
"Document-type:text/html\n\n"; print "Hello World!";)
8. start MoonGoose, direct your browser to localhost:8080/test_one then to 
localhost:8080/test%20one and execute the CGI files


What is the expected output? What do you see instead?
expected result is a well functionning CGI script
Instead, you get : internal server error [500]

What version of the product are you using? On what operating system?
using MoonGoose 3.1 on Windows 7 (64 bit version) home edition

Please provide any additional information below.
File access under document root is not a problem, only CGI seems to be affected 
when document root contains one or more space. Perhaps the script path needs to 
be quoted when passed to the CGI interpreter?

Original issue reported on code.google.com by [email protected] on 9 Apr 2012 at 2:17

@GoogleCodeExporter
Copy link
Author

actually it has nothing to do with document root, I'm sorry. Only spaces in the 
path to CGI scripts. Sorry, this post was misnamed.

Original comment by [email protected] on 9 Apr 2012 at 2:25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant