From Funtoo
Revision as of 00:30, April 23, 2015 by Threesixes (talk | contribs) (more details)
Jump to: navigation, search



We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

Apache is a powerful web server which serves html/css/cgi/pl out of the box, and can serve other languages/frameworks via extensions.

The Apache Homepage says this of Apache:

The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP server for modern operating systems including UNIX and Windows NT. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards.


Configure USE Flags

Depending upon one's personal preferences, flag changes are sometimes necessary. To extend default USE flags in an Apache ebuild, compile a custom flavor. This can be achieved by Portage's package.use. Create a directory /etc/portage/package.use and file called /etc/portage/package.use/apache, and add the USE flags you want. For example:

root # install -d /etc/portage/package.use
www-servers/apache ssl threads

Alternatively, if one prefers a /etc/portage/package.use flat file:

root # echo 'www-servers/apache ssl threads' >> /etc/portage/package.use


After configuring your preferred USE flags, emerge Apache:

root # emerge apache



Many packages have Apache2 USE flags. These USE flags are often required for an application to be supported by Apache. Setting a system wide Apache2 USE flag is a good idea.

   /etc/portage/make.conf - set system wide apache2 useflag


Apache's configuration files are broken up and located in several spots.

  • /etc/conf.d/apache2
  • /etc/apache2/httpd.conf
  • /etc/apache2/modules.d/*
  • /etc/apache2/vhosts.d/*

conf.d controls the init script, adding things to it such as -D SECURITY & -D PHP5 will enable web application fire-walling & the php scripting language.

httpd.conf controls how the server behaves, at the bottom of the file it has directives to include configuration files ending in .conf in /etc/apache2/modules.d and /etc/apache2/vhosts.d


DSO / mod_php

To show which PHP versions are available for Apache on your system:

root # eselect php list apache2
  [1]   php5.5
  [2]   php5.6 *

To select PHP 5.5:

root # eselect php set apache2 php5.5
   /etc/conf.d/apache2 - enable php dso module
"... -D PHP5"

Restart Apache:

root # rc-service apache2 restart

If php code is showing instead of processing server side, ensure you have emerged app-eselect/eselect-php with the apache2 useflag.



php-fpm is untested.

Apache supports php-fpm also, this is the preferred method to serve php.

   /etc/portage/make.conf - enable proxy & fcgi modules
APACHE2_MODULES="actions alias auth_basic auth_digest authn_alias authn_anon authn_core authn_dbm authn_file authz_core authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif socache_shmcb speling status unique_id unixd userdir usertrack vhost_alias proxy proxy_fcgi"
   /etc/conf.d/apache2 - enable proxy module
"... -D PROXY"
   /etc/apache2/httpd.conf - enable proxy & fcgi modules
LoadModule proxy_module modules/
LoadModule proxy_fcgi_module modules/
   /etc/apache2/vhosts.d/00_default_vhost.conf - configure php-fpm vhosts.
ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://$1
DirectoryIndex /index.php

Enabling Security Module

root # emerge mod_security
   /etc/conf.d/apache2 - enable mod_security

Control this module by editing these files, and restarting Apache.

/etc/apache2/modules.d/79_modsecurity.conf & /etc/apache2/modules.d/80_modsecurity-crs.conf


To start Apache immediately:

root # rc-service apache2 start

To start Apache upon boot:

root # rc-update add apache2


What is mod_rewrite?

The Apache documentation describes mod_rewrite as:

The mod_rewrite module uses a rule-based rewriting engine, based on a PCRE regular-expression parser, to rewrite requested URLs on the fly. By default, mod_rewrite maps a URL to a filesystem path. However, it can also be used to redirect one URL to another URL, or to invoke an internal proxy fetch.

Setting it up

mod_rewrite has a reputation of being difficult to set up. mod_rewrite requires following symlinks & Order allow,deny (apache 2.2) or Require all granted (apache 2.4) is set. To test functionality of mod_rewrite we will need to make a few files.


If you want to test this for web applications such as mediawiki adjust the path to /var/www/localhost/htdocs/mediawiki/.htaccess

   /var/www/localhost/htdocs/.htaccess - enable the rewrite engine
RewriteEngine on 
RewriteRule ^test.html$ rewrite.html
   /var/www/localhost/htdocs/test.html - set system wide apache2 useflag
rewrite is not working
   /var/www/localhost/htdocs/rewrite.html - set system wide apache2 useflag
rewrite is working

Then point your browser to You should see that the text from rewrite.html has been loaded.