On 12/11/2012 1:12 PM, Eric Covener wrote:
> On Tue, Dec 11, 2012 at 1:01 PM, Toni Moreno <toni.moreno@xxxxxxxxx> wrote:
>> I would be happy to know another way to upload files for any users on the
>> system through HTTPS.
>
> mod_fcgid doesn't do this for you. If you POST to a fastcgi, read the
> post body in whatever direct way your language provides. Don't try to
> figure out what temporary file the server may have created in the
> background and read it as a file.
>
>
>> But the question is why mod_fcgid changes apache umask ? is the correct way
>> to proceed , a undefined configuration , or a bug?
>
> Read your systems manual entry for "mkstemp". This family of
> functions doesn't create files with the just the umask masked off, it
> explicitly controls them.
>
Toni, to add to what Eric said above, I think most of us are trying to
understand why you are attempting to control file permissions at the
Apache layer (or worse, the OS layer).
Applications should be portable. If you move your application to another
server, it should function the same way. By attempting to control the
initial permissions with which Apache creates files, you are violating a
fundamental tenet of the portability principle.
If I read your original post correctly, PHP should have the permissions
required to call chmod('/tmp/fcgid.tmp.PEozaa/', octdec('0644)). Problem
solved.
-Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|