Bug 50362 - apache-1.3.19-5 has problems with ExecCGI option
Summary: apache-1.3.19-5 has problems with ExecCGI option
Status: CLOSED DUPLICATE of bug 47837
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apache
Version: 7.1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-30 19:39 UTC by Justin Moore
Modified: 2007-04-18 16:35 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-07-31 00:44:23 UTC


Attachments (Terms of Use)
Apache config (40.10 KB, text/plain)
2001-07-30 19:41 UTC, Justin Moore
no flags Details
Prints environment to stdout (59 bytes, text/plain)
2001-07-30 19:42 UTC, Justin Moore
no flags Details

Description Justin Moore 2001-07-30 19:39:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.3-12smp i686)

Description of problem:
When I try to run even simple CGIs in a non ScriptAlias'ed directory, I get
"Premature end of script headers".  I have ExecCGI specified for the
directory, and an AddHandler for cgi-scripts.  I've included my httpd.conf
file and a simple cgi that won't work in my directory.  This happened when
I upgraded from 7.0 to 7.1.

How reproducible:
Always

Steps to Reproduce:
1. Configure apache to execute ".cgi" files and set the ExecCGI option for
a user directory.
2. Write a simple CGI to return Content-type header and some text.
3. Go to http://hostname.domain/~user/foo.cgi.

Actual Results:  Apache returns a "403: Forbidden", despite all directories
in the path being mode 755 and the script itself being mode 755.

Expected Results:  It should have printed the environment variables.

Additional info:

Comment 1 Justin Moore 2001-07-30 19:41:16 UTC
Created attachment 25451 [details]
Apache config

Comment 2 Justin Moore 2001-07-30 19:42:43 UTC
Created attachment 25453 [details]
Prints environment to stdout

Comment 3 Michael Schwendt 2001-07-31 00:44:19 UTC
The info here, #bug 47837, fixes your problem most likely.

Comment 4 Justin Moore 2001-07-31 14:53:38 UTC
Turns out to be MIN_GID-blocked by suEXEC.

*** This bug has been marked as a duplicate of 47837 ***


Note You need to log in before you can comment on or make changes to this bug.