Difference between revisions of "Talk:Apache HTTP Server"
(→userdir disable: re)
m (Kynikos moved page Talk:Apache HTTP server to Talk:Apache HTTP Server: the official name has a capital "S")
Revision as of 02:21, 24 August 2014
Keep getting PID-errors: systemd: 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
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)
Move to Apache
As most of the non-Apache content is now in PHP and MySQL, I think that this article should be moved to Apache. This better describes the content of this page, and is more in line with other wiki titles.
- I think it can make sense, but the content should be adapted, e.g. the introduction, the "Installation" section, the links at the bottom, the sections tree...
- Then, isn't "Apache HTTP Server" the full official name of the application?
- -- Kynikos (talk) 03:10, 18 August 2014 (UTC)
- Yes, you are right on both points. If we decide to do the move, I will gladly adapt the content, making it more suitable for the new title.
- I am not sure what to do about the name, though. "Apache HTTP Server" is indeed the correct name, but it is widely known as "Apache", even the package is called just . I guess the full name is more correct, though.
- --Lonaowna (talk) 20:53, 18 August 2014 (UTC)
- Besides being more correct, it's also safer: "Apache HTTP Server" contains "Apache", so those searching for the short name will find it anyway; the opposite wouldn't work (without relying on a redirect).
- The PHP and MariaDB stuff could be either moved to their articles or put into a new "LAMP" section aimed at explaining how to make everything work together (mainly with links to the relevant articles).
- Nobody else has shown interest in these few days, I'm in favour, but maybe you want to wait a couple of days longer to avoid wasting effort in case late objections are raised.
- -- Kynikos (talk) 00:56, 20 August 2014 (UTC)
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)
I think that section need add:
#LoadModule userdir_module modules/mod_userdir.so
to fully disable userdir.
- According to :
- "User directory substitution is not active by default in versions 2.1.4 and later. In earlier versions, UserDir public_html was assumed if no UserDir directive was present."
- So I think it is safe to just not include the conf. --Lonaowna (talk) 18:20, 23 August 2014 (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 in AUR fixes this. this is simply php recompiled.
- You can also get PHP to work by using the
mod_mpm_preforkas 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. 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! :)