On Fri, Jan 23, 2009 at 6:44 PM, Buck Golemon <[email protected]> wrote:
> Brian Mearns <mearns.b <at> gmail.com> writes:
>
>>
>> On Thu, Jan 22, 2009 at 8:16 PM, Buck Golemon <buck.golemon <at> amd.com>
> wrote:
>> > works just fine:
>> > http://pdweb.ca.atitech.com/beg/foo.sh
>> >
>> > doesn't work:
>> > http://pdweb.ca.atitech.com/~bgolemon/foo.sh
>> >
>> >
>> > Here's the relevant configuration.
>> > <IfModule mod_userdir.c>
>> >    UserDir public_html
>> >    UserDir disabled root
>> > </IfModule>
>> > Alias /beg/ "/user/bgolemon/public_html/"
>> > <Directory "/user/bgolemon/public_html/">
>> >    Options ExecCGI
>> >    SetHandler cgi-script
>> >    AllowOverride None
>> >    Allow from all
>> >    Order allow,deny
>> > </Directory>
>> >
> ...
>> >
>> >
>> > Are there any known issues with this? How can I get this to work? This
> makes me
>> > feel like either the cgi-script handler or the UserDir module is broken.
>> >
>> > Thanks in advance,
>> > --Buck
>>
>> Are you able to access anything in your userdir?
>>
>> You might need another Directory tag for "~bgolemon".
>> -Brian
>>
>
> Thanks for the reply, but if I remove the SetHandler directive above, it
> displays the file in plaintext just fine. It means both that the UserDir
> functions ok by itself, and that the <Directory> section above is being 
> applied
> to my home dir.
>
> --Buck

Hm. About the only other thing I can think of is a permissions issue.
I assumed it would always execute scripts as the same user as apache,
but maybe for userdirs, it's switching users? Sorry, can't think of
anything else that might cause this.

-Brian

-- 
Feel free to contact me using PGP Encryption:
Key Id: 0x3AA70848
Available from: http://pgp.mit.edu/

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
   "   from the digest: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to