APACHE

1. APACHE

2. What is Apache? • is a powerful, flexible, HTTP/1.1 compliant web server • implements the latest protocols, including HTTP/1.1 (RFC2616) • is highly configurable and extensible with third-party modules • can be customised by writing 'modules' using the Apache module API • provides full source code and comes with an unrestrictive license • runs on Windows NT/9x, Netware 5.x and above, OS/2, and most versions of Unix, as well as several other operating systems • is actively being developed • encourages user feedback through new ideas, bug reports and patches • implements many frequently requested features, including:

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

4. INSTALLATION

5. Step 1: Double-Click the Apache Executable and Get the Welcome Screen • Click Next

6. Step 2: Read the License • Make sure there's nothing that you can't agree to. Once you accept, you'll be held to the terms of the license.

7. Step 3: Read the README File • Scan the readme file to make sure there aren't any late minute bugs that would make this version crash on your computer.

8. Step 4: Provide Your Server Information • Fill in your Network Domain, server name, and administrator's email address. If this is not going to be hosted on the Internet, you can use "localhost" (without the quotation marks) as the network and server name.

9. Step 5: Typical Setup? • I usually select custom, so I know exactly what is being installed. But choosing typical is a lot faster.

10. Step 6: Review Custom Options • If you chose "Custom" review the options you have. Don't turn off any required modules. I recommend reading the description of all other modules, so you know what is being installed.

11. Step 7: You're Done • Click Finish and go check out your new Apache Web server.

12. CONFIGURATIONS

13. 1.AcceptFilter directive Syntax: AcceptFilter on|off Default: AcceptFilter on Context: server config Status: core Compatibility: AcceptFilter is available in Apache 1.3.22 and later AcceptFilter controls a BSD specific filter optimization

14. 2.AcceptMutex directive AcceptMutex directive Syntax: AcceptMutex uslock|pthread|sysvsem|fcntl|flock|os2sem|tpfcore|none|default Default: AcceptMutex default Context: server config Status: core Compatibility: AcceptMutex is available in Apache 1.3.21 and later. AcceptMutex controls which accept() mutex method Apache will us

15. 3.AccessConfig directive Syntax: AccessConfig file-path|directory-path|wildcard-path Default: AccessConfig conf/access.conf Context: server config, virtual host Status: core Compatibility: The ability to specify a directory, rather than a file name, is only available in Apache 1.3.13 and later. This directive will be eliminated in version 2.0.

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 "Top Secret" 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.48BindAddress can be used as an alternative method for supporting virtual hosts using multiple independent servers, instead of using <VirtualHost> sections

29. 12.BS2000Account directive Syntax: BS2000Account account Default: none Context: server config Status: core Compatibility: BS2000Account is only available for BS2000 machines, as of Apache 1.3 and later.

30. 12.BS2000Account directive BS2000Account directive is available for BS2000 hosts only.It must be used to define the account number for the non-privileged apache server user (which was configured using the User directive).

31. 13.CGICommandArgs directive Syntax: CGICommandArgs On|Off Default: CGICommandArgs On Context: directory, .htaccess Override: Options Status: core Compatibility: Available in Apache 1.3.24 and later.

32. 14.ClearModuleList directive Syntax: ClearModuleList Context: server config Status: core Compatibility: ClearModuleList is only available in Apache 1.2 and later. This directive clears the list. It is assumed that the list will then be re-populated using the AddModule directive.

33. 15.ContentDigest directive Syntax: ContentDigest on|off Default: ContentDigest off Context: server config, virtual host, directory, .htaccess Override: Options Status: experimental Compatibility: ContentDigest is only available in Apache 1.1 and later This directive enables the generation of Content-MD5 headers as defined in RFC1864 respectively RFC2068

34. 16.CoreDumpDirectory directive Syntax: CoreDumpDirectory directory-path Default: the same location as ServerRoot Context: server config Status: core This controls the directory to which Apache attempts to switch before dumping core.

35. 17.DefaultType directive Syntax: DefaultType MIME-type Default: DefaultType text/plain Context: server config, virtual host, directory, .htaccess Override: FileInfo Status: core

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

37. 18.DirectoryMatch <DirectoryMatch> Syntax: <DirectoryMatch regex> ... </DirectoryMatch> Context: server config, virtual host Status: Core. Compatibility: Available in Apache 1.3 and late

38. 18.DirectoryMatch <DirectoryMatch> and </DirectoryMatch> are used to enclose a group of directives which will apply only to the named directory and sub-directories of that directory, the same as <Directory>. However, it takes as an argument a regular expression. For example: <DirectoryMatch "^/www/.*/[0-9]{3}">

39. 19.DocumentRoot directive DocumentRoot directive Syntax: DocumentRoot directory-path Default: DocumentRoot /usr/local/apache/htdocs Context: server config, virtual host Status: core This directive sets the directory from which httpd will serve files.

40. 19.DocumentRoot directive Unless matched by a directive like Alias, the server appends the path from the requested URL to the document root to make the path to the document. Example: DocumentRoot /usr/web then an access to http://www.my.host.com/index.html refers to /usr/web/index.html.

41. 20.EBCDICConvert Syntax: EBCDICConvert On|Off[=direction] extension [extension] ... Context: server config, virtual host, directory, .htaccess Status: core Override: FileInfo Compatibility: The configurable EBCDIC conversion is only available in Apache 1.3.19 and later.

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

43. 21.EnableExceptionHook directive Syntax: EnableExceptionHook on|off Default: EnableExceptionHook off Context: server config Status: core Compatibility: EnableExceptionHook is available in Apache 1.3.30 and later EnableExceptionHook controls whether or not an exception hook implemented by a module will be called after a child process crash.

44. 22.<Files> directive Syntax: <Files filename> ... </Files> Context: server config, virtual host, .htaccess Status: core Compatibility: only available in Apache 1.2 and above The <Files> directive provides for access control by filename.

45. 23.<FilesMatch> Syntax: <FilesMatch regex> ... </FilesMatch> Context: server config, virtual host, .htaccess Status: core Compatibility: only available in Apache 1.3 and above. The <FilesMatch> directive provides for access control by filename, just as the <Files> directive does. However, it accepts a regular expression. For example: <FilesMatch "\.(gif|jpe?g|png)$"> would match most common Internet graphics formats.

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 "\.(gif|jpe?g|png)$"> would match most common Internet graphics formats.

47. 24.HostnameLookups directive Syntax: HostnameLookups on|off|double Default: HostnameLookups off Context: server config, virtual host, directory Status: core Compatibility: double available only in Apache 1.3 and above. Compatibility: Default was on prior to Apache 1.3.

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 "tcpwrappers" terminology this is called PARANOID.)

49. 25.IdentityCheck directive Syntax: IdentityCheck on|off Default: IdentityCheck off Context: server config, virtual host, directory Status: core This directive enables RFC1413-compliant logging of the remote user name for each connection, where the client machine runs identd or something similar. This information is logged in the access log.

50. 26.<IfDefine> directive Syntax: <IfDefine [!]parameter-name> ... </IfDefine> Default: None Context: all Status: Core Compatibility: <IfDefine> is only available in 1.3.1 and later.