Difference between revisions of "Talk:Apache HTTP Server"

From ArchWiki
Jump to: navigation, search
(Move to Apache: re)
m (Signed the comment)
 
(35 intermediate revisions by 16 users not shown)
Line 17: Line 17:
 
Restart httpd and now it should work. --[[User:Nak|Nak]] 17:22, 22 April 2007 (GMT+1)
 
Restart httpd and now it should work. --[[User:Nak|Nak]] 17:22, 22 April 2007 (GMT+1)
  
== Split this article ==
+
== Using SSL ==
  
I hope this is what the page is for.
+
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 [http://blackflag.wordpress.com/2006/06/13/apache2-forcing-all-inbound-traffic-to-ssl/ apache2-forcing-all-inbound-traffic-to-ssl] to be a useful resource in this respect. [[User:Corburn|Corburn]] 13:58, 23 March 2012 (EDT)
 
 
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.
 
 
 
[[User:Harlekin|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.
 
 
 
Thoughts? --[[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 12:01, 17 August 2014 (UTC)
 
 
 
: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?
 
:-- [[User:Kynikos|Kynikos]] ([[User talk: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.
+
== User Directories ==
::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 {{Pkg|apache}}. I guess the full name is more correct, though.
 
::--[[User:Lonaowna|Lonaowna]] ([[User talk: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).
+
Continuing discussion from the main page, you do '''not''' have to make your home directory ''world-readable'' in order to make your ''public_html'' directory available to the web server. To minimize home directory exposure, I generally set the permission for both ''/home/$USER'' and ''/home/$USER/public_html'' to '''0750''' and change the group ownership to '''http'''. E.g.:
:::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.
 
:::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 00:56, 20 August 2014 (UTC)
 
  
== Using SSL ==
+
mkdir -p $HOME/public_html
 +
chmod 0750 $HOME $HOME/public_html
 +
chown $USER:http $HOME $HOME/public_html
  
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 [http://blackflag.wordpress.com/2006/06/13/apache2-forcing-all-inbound-traffic-to-ssl/ apache2-forcing-all-inbound-traffic-to-ssl] to be a useful resource in this respect. [[User:Corburn|Corburn]] 13:58, 23 March 2012 (EDT)
+
That way you have given only '''read''' (descend into) permission to the web server user for both your home directory and your userdir. [[User:Drankinatty|David C. Rankin, J.D.,P.E. -- Rankin Law Firm, PLLC]] ([[User talk:Drankinatty|talk]]) 07:22, 25 August 2015 (UTC)
  
 
== userdir disable ==
 
== userdir disable ==
Line 58: Line 39:
 
[[User:Jabalv|Jabalv]] ([[User talk:Jabalv|talk]]) 18:48, 25 December 2013 (UTC)
 
[[User:Jabalv|Jabalv]] ([[User talk:Jabalv|talk]]) 18:48, 25 December 2013 (UTC)
  
== apache 2.4 upgrade==
+
:According to [http://httpd.apache.org/docs/2.4/mod/mod_userdir.html]:
 
+
:"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."
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[https://aur.archlinux.org/packages/php_zts/] in AUR fixes this. this is simply php recompiled.
+
:So I think it is safe to just not include the conf. --[[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 18:20, 23 August 2014 (UTC)
  
:You can also get PHP to work by using the {{ic|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.[http://www.php.net/manual/en/install.unix.apache2.php] I think way currently described is the "right" way, but I'm not sure about that. --[[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 09:25, 10 March 2014 (UTC)
+
== Which MPM to use with php-fpm and mod_proxy_fcgi? ==
  
== SSL Produces Syntax Errors When Following Guide ==
+
The section about php-fpm and mod_proxy_fcgi does not say which MPM (event, prefork, worker) is optimal for this configuration. If I understand correctly (but I'm not an expert), the default mpm_event_module would be the best choice. It would be good to document this, because users coming from a mod_php / mpm_prefork_module configuration would need to actively switch back to mpm_event_module. --[[User:Marcvangend|Marcvangend]] ([[User talk:Marcvangend|talk]]) 09:24, 23 November 2015 (UTC)
  
Hi everybody,
+
The best MPM to use is to be determined by individual benchmarks. But event MPM should be good as a default.
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:
+
:A good start would be to, at least, describe what MPMs are and what their main use is, since the term is used multiple times in the article. Something like:
 +
:Apache can be configured to use _one_ of several Multi-Processing Modules ([https://httpd.apache.org/docs/2.2/mpm.html MPM]s), which affect performance and the way it allocates resources in response to requests. mpm-prefork: ... mpm-worker: ... mpm-event: ...
 +
:https://tweaked.io/guide/apache2/ has a short summary of MPM specifics; but we should put up something more informative. :--[[User:Nodiscc|Nodiscc]] ([[User talk:Nodiscc|talk]]) 02:54, 18 November 2017 (UTC)
  
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! :)
+
== Removal of Create a key and (self-signed) certificate section ==
  
Thanks,
+
At first, I tried following the suggested [[OpenSSL#Certificates]] section instead (as per recommendation in the banner), but found it confusing, at least in the context of setting up an Apache server. After reading [[OpenSSL#Certificates]] I still wasn't sure which output is which, had to go and check with the man pages, Apache docs and search on the internet to be certain (which defeats the purpose of having it on the wiki).
[[User:Snellsg|Snellsg]] ([[User talk:Snellsg|talk]]) 18:58, 15 March 2014 (UTC)
 
  
:Hi! You need to install {{pkg|openssl}} and uncomment the following line in {{ic|httpd.conf}}:
+
On the other hand, examples provided in current [[Apache HTTP Server#Create a key and (self-signed) certificate]] are short and to the point, relevant to Apache server configuration. '''server.key''' and '''server.crt''' output names are self-explanatory. My vote is for this section to stay as it is and provide a link to [[OpenSSL#Certificates]] for further information. [[User:Romstor|Romstor]] ([[User talk:Romstor|talk]]) 13:04, 25 September 2018 (UTC)
:{{bc|#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. --[[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 19:56, 15 March 2014 (UTC)
 

Latest revision as of 13:04, 25 September 2018

PID-errors

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)

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)

User Directories

Continuing discussion from the main page, you do not have to make your home directory world-readable in order to make your public_html directory available to the web server. To minimize home directory exposure, I generally set the permission for both /home/$USER and /home/$USER/public_html to 0750 and change the group ownership to http. E.g.:

mkdir -p $HOME/public_html
chmod 0750 $HOME $HOME/public_html
chown $USER:http $HOME $HOME/public_html

That way you have given only read (descend into) permission to the web server user for both your home directory and your userdir. David C. Rankin, J.D.,P.E. -- Rankin Law Firm, PLLC (talk) 07:22, 25 August 2015 (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)

According to [1]:
"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)

Which MPM to use with php-fpm and mod_proxy_fcgi?

The section about php-fpm and mod_proxy_fcgi does not say which MPM (event, prefork, worker) is optimal for this configuration. If I understand correctly (but I'm not an expert), the default mpm_event_module would be the best choice. It would be good to document this, because users coming from a mod_php / mpm_prefork_module configuration would need to actively switch back to mpm_event_module. --Marcvangend (talk) 09:24, 23 November 2015 (UTC)

The best MPM to use is to be determined by individual benchmarks. But event MPM should be good as a default.


A good start would be to, at least, describe what MPMs are and what their main use is, since the term is used multiple times in the article. Something like:
Apache can be configured to use _one_ of several Multi-Processing Modules (MPMs), which affect performance and the way it allocates resources in response to requests. mpm-prefork: ... mpm-worker: ... mpm-event: ...
https://tweaked.io/guide/apache2/ has a short summary of MPM specifics; but we should put up something more informative. :--Nodiscc (talk) 02:54, 18 November 2017 (UTC)

Removal of Create a key and (self-signed) certificate section

At first, I tried following the suggested OpenSSL#Certificates section instead (as per recommendation in the banner), but found it confusing, at least in the context of setting up an Apache server. After reading OpenSSL#Certificates I still wasn't sure which output is which, had to go and check with the man pages, Apache docs and search on the internet to be certain (which defeats the purpose of having it on the wiki).

On the other hand, examples provided in current Apache HTTP Server#Create a key and (self-signed) certificate are short and to the point, relevant to Apache server configuration. server.key and server.crt output names are self-explanatory. My vote is for this section to stay as it is and provide a link to OpenSSL#Certificates for further information. Romstor (talk) 13:04, 25 September 2018 (UTC)