Bug 50362

Summary: apache-1.3.19-5 has problems with ExecCGI option
Product: [Retired] Red Hat Linux Reporter: Justin Moore <jdm2d>
Component: apacheAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-31 00:44:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Apache config
none
Prints environment to stdout none

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 ***