Apache is an open source web server software that runs on over half of all internet servers. The document provides instructions on downloading, installing, and configuring Apache on Windows and Linux systems. It also lists and describes 30 different Apache configuration directives that can be used to customize the server setup.

1. What's Apache? Apache is open source, powerful, free and runs on more than half of all Internet servers. Let's take a quick look at how to get your Apache server up and running.

2. Downloading Apache Obviously, the first thing you need to do is download the necessary source files. Various mirrors provide the download, so where you get the files is largely a matter of preference. (I tend to download from mirrors because there's not as much traffic as on the main site.) The files are available from the Apache Web site, as well.

3. Apache installation and setup Now that you've downloaded the software, you can begin the installation, which you'll handle completely from the command line. First, extract the files with the following commands: $ tar -xvzf apache-version.tar.gz $ cd apache-version/

4. Apache installation and setup cont. Now that the source is untarred and ready to go, you can begin the configuration, which offers a wide range of customisation options. If you run the command ./configure --help you can see a list of Apache's configuration options, which are divided into various sections: * General options * Stand-alone options * Installation layout options * Configuration options * suEXEC options * Deprecated options

7. The next option relates to the type of setup. As shown below, make sure “complete” is selected and click “next”.

9. To test the Apache installation go to http://127.0.0.1/ using a web browser of your choice. If you can see the “Test Page for Apache Installation” (like the one shown in the image below) you have successfully installed Apache.

10. Apache Configurations

14. This feature can be disabled using: AccessConfig /dev/null Or, on Win32 servers, AccessConfig nul Historically, this file only contained <Directory> sections; in fact it can now contain any server directive allowed in the server config context. However, since Apache version 1.3.4, the default access.conf file which ships with Apache contains only comments.

15. 4.AccessFileName directive Syntax: AccessFileName filename [filename] ... Default: AccessFileName .htaccess Context: server config, virtual host Status: core Compatibility: AccessFileName can accept more than one filename only in Apache 1.3 and later

16. For example: AccessFileName .acl before returning the document /usr/local/web/index.html, the server will read /.acl, /usr/.acl, /usr/local/.acl and /usr/local/web/.acl for directives, unless they have been disabled with <Directory /> AllowOverride None </Directory>

17. 5.AddDefaultCharset directive Syntax: AddDefaultCharset On|Off|charset Context: all Status: core Default: AddDefaultCharset Off Compatibility: AddDefaultCharset is only available in Apache 1.3.12 and later

18. AddDefaultCharset On enables Apache's internal default charset of iso-8859-1 as required by the directive. You can also specify an alternate charset to be used. For example: AddDefaultCharset utf-8

19. 6.AddModule directive Syntax: AddModule module [module] ... Context: server config Status: core Compatibility: AddModule is only available in Apache 1.2 and later For example: AddModule mod_include.c

20. 7.AllowOverride directive Syntax: AllowOverride All|None|directive-type [directive-type] ... Default: AllowOverride All Context: directory Status: core AllowOverride is only valid in <Directory> sections, not in <Location> or <Files> sections, as implied by the Context section above

21. 8.AuthName directive AuthName directive Syntax: AuthName auth-domain Context: directory, .htaccess Override: AuthConfig Status: cor sets the name of the authorization realm for a directory

22. It must be accompanied by AuthType and Require directives, and directives such as AuthUserFile and AuthGroupFile to work. For example: AuthName &quot;Top Secret&quot; The string provided for the AuthName is what will appear in the password dialog provided by most browsers.

23. 9.AuthDigestRealmSeed directive Syntax: AuthDigestRealmSeed secret-real-string Context: directory, .htaccess Override: AuthConfig Status: core sets a per realm secret nonce prefix which is used to ensure that a captured username, password and realm string during a Digest exchange cannot be replayed at other places.

24. 10.AuthType directive Syntax: AuthType Basic|Digest Context: directory, .htaccess Override: AuthConfig Status: core This directive selects the type of user authentication for a directory. Only Basic and Digest are currently implemented. It must be accompanied by AuthName and Require directives, and directives such as AuthUserFile and AuthGroupFile to work.

25. 11.BindAddress directive BindAddress directive Syntax: BindAddress *|IP-address|domain-name Default: BindAddress * Context: server config Status: core Compatibility: BindAddress is deprecated and will be eliminated in Apache 2.0.

26. For example: BindAddress 192.168.15.48 BindAddress can be used as an alternative method for supporting virtual hosts using multiple independent servers, instead of using <VirtualHost> sections

54. Thank you