Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
These are really opened ended questions. How do you configure SELinux for HTTP? Well that depends on what HTTP you're doing. Do you allow private web sites in /home/user/public_html? Do you use CGI? PHP?
Run "getsebool -a | grep http" to see what SELinux parameters can be tuned, and that may give you a start on what you need to change.
What platform are you using? RHEL or CentOS?
Perhaps you could also explain a little more about what you want to achieve with your second question?
These are really opened ended questions. How do you configure SELinux for HTTP? Well that depends on what HTTP you're doing. Do you allow private web sites in /home/user/public_html? Do you use CGI? PHP?
Run "getsebool -a | grep http" to see what SELinux parameters can be tuned, and that may give you a start on what you need to change.
What platform are you using? RHEL or CentOS?
Perhaps you could also explain a little more about what you want to achieve with your second question?
I agree with blacky...
Also, along with the "sebool" commands, you need to set the directory options correctly...
If you doc root is NOT in /var/www/html (like in /web for example) the you need to set the directory correctly.
Use...
Code:
root@host# ll -dZ /var/www/html
This will show you what you need to set your directory as...this is just a piece, as blacky has mentioned you need to set your sebool's correctly as well
This might sound silly ... but, as per my understanding:
Shouldn't one install a WebServer/Application Server if they want to be able to serve HTTP pages hosted on the machine?
I've interpreted the question to mean:- "What needs to be tweaked in SELinux for Apache to work?" So my assumption is that Apache HTTPD is already installed and running, but SELinux needs tweaking for it to work properly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.