This is a discussion on Permissions Problems on Virtual Hosts within the Linux Web Servers forums, part of the Web Server and Related Forums category; Hey there. I have a permissions issue after setting to 777, so I'm not clear on what's going ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hey there. I have a permissions issue after setting to 777, so I'm not
clear on what's going on. I have 5 domains on one box. http.conf was configured with each in mind. Now, I get permissions problems everywhere I look. What could be the problem here? Also, how can I trace a mapping for a domain, to show the vhosts are indeed working? Cheers |
|
|||
|
On Thu, 27 May 2004, Rich Fortnum <fortnum@viaduct-productions.com> wrote:
> Hey there. I have a permissions issue after setting to 777, so I'm not > clear on what's going on. 777 permission is very insecure (anybody can create, read, write, modify anything). In particular suexec (or specifying a user/group for vhost) would refuse to serve anything with dir/file permission greater than 755. > I have 5 domains on one box. http.conf was configured with each in mind. > Now, I get permissions problems everywhere I look. > > What could be the problem here? Give the directory for each domain the owner/group of whoever maintains it and not more than 755 permission maximum. All directories in full path would typically need at least 701 permission. > Also, how can I trace a mapping for a domain, to show the vhosts are indeed > working? You could do a custom log that includes "%V" to show the requested vhost. For my nameless default wildcard worm catching vhost I use: LogFormat "%V %h %l %u %t \"%r\" %>s %b" nohost CustomLog /var/log/httpd/nohost_access_log nohost And/or you could have separate log for each vhost. -- David Efflandt - All spam ignored http://www.de-srv.com/ |