Apache is a powerful and flexible web server that implements the latest HTTP protocols. It is highly configurable, customizable through modules, provides full source code, and runs on many operating systems. The document then provides details on installing and configuring Apache, including the steps for installation and descriptions of various configuration directives.

1. APACHE

3. INSTALLATIONS & CONFIGURATIIONS -PRESENTED BY H. ANKUSH. JAIN

4. INSTALLATION

12. CONFIGURATIONS

16. 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. 3.AccessConfig directive

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

18. 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> 4.AccessFileName directive

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

20. 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 5.AddDefaultCharset directive

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

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

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

24. 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. 8.AuthName directive

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

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

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

28. 11.BindAddress directive 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

36. 17.DefaultType directive There will be times when the server is asked to provide a document whose type cannot be determined by its MIME types mappings. The server must inform the client of the content-type of the document, so in the event of an unknown type it uses the DefaultType. For example: DefaultType image/gif

42. 20.EBCDICConvert The EBCDICConvert directive maps the given filename extensions to the specified conversion setting (On or Off). File extensions may be specified with or without a leading dot

46. 23.<FilesMatch> The <FilesMatch> directive provides for access control by filename, just as the <Files> directive does. However, it accepts a regular expression. For example: <FilesMatch &quot;(gif|jpe?g|png)$&quot;> would match most common Internet graphics formats.

48. 24.HostnameLookups directive This directive enables DNS lookups so that host names can be logged (and passed to CGIs/SSIs in REMOTE_HOST). At least one of the ip addresses in the forward lookup must match the original address. (In &quot;tcpwrappers&quot; terminology this is called PARANOID.)

53. 27.<IfModule> directive Syntax: <IfModule [!]module-name> ... </IfModule> Default: None Context: all Status: Core Compatibility: IfModule is only available in 1.2 and later.

54. 27.<IfModule> directive The <IfModule test>...</IfModule> section is used to mark directives that are conditional. The directives within an IfModule section are only processed if the test is true. If test is false, everything between the start and end markers is ignored. The test in the <IfModule> section directive can be one of two forms: * module name * !module name

58. 30.<LimitExcept> directive <LimitExcept> and </LimitExcept> are used to enclose a group of access control directives which will then apply to any HTTP access method not listed in the arguments; i.e., it is the opposite of a <Limit> section and can be used to control both standard and nonstandard/unrecognized methods. See the documentation for <Limit> for more details.For

60. THANK YOU