This summary provides an overview of the Apache installation and configuration document: 1) Apache Tomcat is an open source software that implements the Java Servlet and JavaServer Pages technologies. 2) The document outlines the steps to install Apache on Ubuntu using apt-get. 3) It describes how to configure Apache including directives for access control, authentication, default types, and more.

1. APACHE INSTALLATION CONFIGURATION - BY MANISH BOTHRA

3. INSTALLATION

4. Installation Apache The first app we will install is the web server Apache . To get started open your console and type: sudo apt-get install apache2 After you put in your password and accept and a short wait you should have a working installation of Apache. To test it point your web browser to http://localhost

8. CONFIGURATION

12. 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.

13. 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

14. 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>

15. 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

16. 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

17. 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

18. 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

19. 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

20. 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.

21. 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.

22. 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.

23. 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.

24. 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