httpdocs folder chmoded to 750??

[Traged1]

When adding new domains I have noticed that the new httpdocs folders are chmod 750 / rwx r-x ---

This did not cause a problem until I tried to execute an asp script which I am using Sun One ASP/ChiliASP to serve.

When the httpdocs folder is chmodded to 750 the CASP server returns a 403 forbidden for any ASP pages on that domain.

A simple chmod 755 httpdocs fixes the problem, but I have 400+ domains and add new domains on a daily basis.

Why would SW-Soft all of the sudden start using 750 over 755 on the httpdocs, previous versions of PLESK have all used 755, even in the .skel folders the httpdocs folders are all 755 even in PLESK 7.5.1. But when you add the new domain httpdocs is 750?

Anyone got any idea's?

 

[Cranky]

You could report it as a bug to bugreport[at]sw-soft.com and temporarily setup a cron job to chmod the directory on all domains.

chmod 755 /home/httpd/vhosts/*/httpdocs/

 

[Mirco@]

Why? This is not a bug

 

[Traged1]

Thanks, I will report it as a possible bug as it does not appear to be correct to me.

 

[Cranky]

Originally posted by Mirco
Why? This is not a bug

Because if it's causing problems for users then it needs to get to the people who read email sent to bugreport@.

 

[thunder@]

I know this is an old topic, but it seems to be a bug to me. How is it not? It changes all of my domains permissions when a new one is added. And what is the point of a placeholder if that permison (blocked to public) is supposed to be used? I am getting very aggrivated with this software.

 

[ProfiTiger]

The 403-Error is described and fixed in http://swforum.sun.com/jive/thread.jspa?threadID=52321&tstart=75
It is a problem of the way, plesk handles apache2/httpd.conf.
Try the second post in this thread, it is the way I could fix the damn 403-error on my server. And httpdocs stay at 750
Greetings,
ProfiTiger

 

[ProfiTiger]

In addition to my last post:
I think 750 for httpdocs is ok and secure, since the visitors should not browse (read) in the httpdocs folder. Its the httpd2-service and not "anyone", who is reading files in this folder to show them in the browser.