Difference between revisions of "Talk:Apache HTTP Server"

Revision as of 08:40, 22 March 2014

/srv/http and other issues

It seems that the latest apache-package doesn't create the /srv/httpd directory anymore. Also I have an question about the chmod's:

1. chmod o+x /srv/http
2. chown http:http /srv/http

Or is this better (more secure?):

1. chown http:http /srv/http
2. cd /srv/http
3. chmod 755 /srv/http
4. find . -type f -exec chmod 644 {} \;
5. find . -type d -exec chmod 755 {} \;

Also keep getting PID-errors: systemd[1]: PID file /run/httpd/httpd.pid not readable (yet?) after start. (even when modules/mod_unique_id.so is disabled)

About the PHP Installation, mod_mpm_prefork seems not the best choice: https://serverfault.com/questions/383526/how-do-i-select-which-apache-mpm-to-use/383634#383634 I would vote for mod_proxy_handler

Beta990 (talk) 15:14, 16 March 2014 (UTC)

unique_id_module

If the service httpd don't start, take a look at /var/log/httpd/error_log. If appears this line: -[alert] (EAI 2)Name or service not known: mod_unique_id: unable to find IPv4 address of "myhost" you must uncomment the line: LoadModule unique_id_module. Restart httpd and now it should work. --Nak 17:22, 22 April 2007 (GMT+1)

Split this article

I hope this is what the page is for.

In my opinion setting up LAMP should not contain detailed information about how to set up parts of LAMP. It would be cleaner to only explain how to bring these parts to work together. Especially because of the explanation's integrity. Further more because then users will be able to find a standalone HOWTO for setting up these parts. For example you don't have to read through this page order to get MySQL working. Because of the mentioned integrity I think it would be best to create independent HOWTOs on how to setup MySQL, php and maybe even apache and refer to them from this page.

I've started with MySQL because I know how to setup it and because some parts in this HOWTO are not needed any more and because of that are just confusing.

harlekin 21:13, 13. Mai 2007 (GMT+1)

Using SSL

Could the SSL section be expanded to include how to use .htaccess and mod_rewrite to redirect traffic for certain sections or the whole site? I found apache2-forcing-all-inbound-traffic-to-ssl to be a useful resource in this respect. Corburn 13:58, 23 March 2012 (EDT)

Wrong argument order?

# usermod -aG http piter

Seems like usermod accepts group as first argument and user as second, unlike gpasswd. Please check. axper (talk) 12:06, 30 August 2013 (UTC)

I've removed the entire section as it doesn't add anything compared to the other method. --Lonaowna (talk) 09:33, 10 March 2014 (UTC)

userdir disable

I think that section need add:

#LoadModule userdir_module modules/mod_userdir.so

to fully disable userdir.

Jabalv (talk) 18:48, 25 December 2013 (UTC)

apache 2.4 upgrade

PHP breaks with apache2.4 install due to the PHP not being "threadsafe" by default, and MPM in apache being turned on by default, and is now core apache. PHP_ZTS[1] in AUR fixes this. this is simply php recompiled.

You can also get PHP to work by using the mod_mpm_prefork as described in the first note in the PHP configuration section. You are right that you can also create an thread-safe PHP, but this is not recommended by PHP devs.[2] I think way currently described is the "right" way, but I'm not sure about that. --Lonaowna (talk) 09:25, 10 March 2014 (UTC)

SSL Produces Syntax Errors When Following Guide

Hi everybody, Apache 2.4 sure did a number on a few of my dev servers, but oh well, it's Arch :)

Anyways, I decided to go back to this guide to see if I could simply remove all related packages to the LAMP server, double check that all old conf files are removed, then I started following this guide again to see if I can get my database server running again. (just in-house tracking of some misc. data, nothing too serious...)

So far, I can make it to the SSL configuration portion of Apache just fine, but once I've generated the keys, uncomment the line "Include conf/extra/httpd-ssl.conf", and restart httpd, I get the following errors regarding syntax issues with SSLChiper every time:

AH00526: Syntax error on line 51 of /etc/httpd/conf/extra/httpd-ssl.conf: Invalid command 'SSLCipherSuite', perhaps misspelled or defined by a module not included in the server configuration

I'm not sure if there's another "legacy" portion from the Apache 2.2 that I've since removed, or if there's something that needs fixed on the guide itself. Any advice would be appreciated! :)

Thanks, Snellsg (talk) 18:58, 15 March 2014 (UTC)

Hi! You need to install openssl and uncomment the following line in httpd.conf:

#LoadModule ssl_module modules/mod_ssl.so

This line was uncommented by default in the old config file. I think this was changed with 2.4.

I will add this to the page. --Lonaowna (talk) 19:56, 15 March 2014 (UTC)