Apache is a powerful web server. apache serves html/css/cgi/pl out of the box, and other languages/frameworks via extensions.
|debug||No||No||Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml.|
|doc||No||Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally|
|ldap||No||Add LDAP support (Lightweight Directory Access Protocol).|
|selinux||No||No, unless selected by default.||!!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur|
|ssl||Yes||Add support for Secure Socket Layer connections.|
|static||No||!!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically.|
|threads||No||Add threads support for various packages. Usually pthreads.|
If you want to enable any of the above use flags, create a file called /etc/portage/package.use/apache and add the options that you want to enable to it. For example:
www-servers/apache ssl threads
After you have configured the USE flags that you want to build Apache with, emerge it:
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.
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
To start apache immediately:
root # rc-service apache2 start
To start apache upon boot:
root # rc-update add apache2
The Apache documentation describes
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 & so on
/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 @ http://127.0.0.1/test.html the text from rewrite.html should be loaded.