Apache Presentation

2,489 views

Published on

Learn Apache installation with help of screenshots and also learn various configurations in Apache

1 Comment
2 Likes
Statistics
Notes
  • This is very useful I used this presentation for my project
    thank you very much
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
2,489
On SlideShare
0
From Embeds
0
Number of Embeds
64
Actions
Shares
0
Downloads
81
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

Apache Presentation

  1. 1. APACHE
  2. 2. What is Apache? <ul><ul><li>is a powerful, flexible, HTTP/1.1 compliant web server </li></ul></ul><ul><ul><li>implements the latest protocols, including HTTP/1.1 (RFC2616) </li></ul></ul><ul><ul><li>is highly configurable and extensible with third-party modules </li></ul></ul><ul><ul><li>can be customised by writing 'modules' using the Apache module API </li></ul></ul><ul><ul><li>provides full source code and comes with an unrestrictive license </li></ul></ul><ul><ul><li>runs on Windows NT/9x, Netware 5.x and above, OS/2, and most versions of Unix, as well as several other operating systems </li></ul></ul><ul><ul><li>is actively being developed </li></ul></ul><ul><ul><li>encourages user feedback through new ideas, bug reports and patches </li></ul></ul><ul><ul><li>implements many frequently requested features, including: </li></ul></ul>
  3. 3. INSTALLATIONS & CONFIGURATIIONS -PRESENTED BY H. ANKUSH. JAIN
  4. 4. INSTALLATION
  5. 5. Step 1: Double-Click the Apache Executable and Get the Welcome Screen <ul><li>Click Next </li></ul>
  6. 6. Step 2: Read the License <ul><li>Make sure there's nothing that you can't agree to. Once you accept, you'll be held to the terms of the license. </li></ul>
  7. 7. Step 3: Read the README File <ul><li>Scan the readme file to make sure there aren't any late minute bugs that would make this version crash on your computer. </li></ul>
  8. 8. Step 4: Provide Your Server Information <ul><li>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 &quot;localhost&quot; (without the quotation marks) as the network and server name. </li></ul>
  9. 9. Step 5: Typical Setup? <ul><li>I usually select custom, so I know exactly what is being installed. But choosing typical is a lot faster. </li></ul>
  10. 10. Step 6: Review Custom Options <ul><li>If you chose &quot;Custom&quot; 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. </li></ul>
  11. 11. Step 7: You're Done <ul><li>Click Finish and go check out your new Apache Web server. </li></ul>
  12. 12. CONFIGURATIONS
  13. 13. 1.AcceptFilter directive <ul><li>Syntax: AcceptFilter on|off </li></ul><ul><li>Default: AcceptFilter on </li></ul><ul><li>Context: server config </li></ul><ul><li>Status: core </li></ul><ul><li>Compatibility: AcceptFilter is available in Apache 1.3.22 and later </li></ul><ul><li>AcceptFilter controls a BSD specific filter optimization </li></ul>
  14. 14. 2.AcceptMutex directive <ul><li>AcceptMutex directive </li></ul><ul><li>Syntax: AcceptMutex uslock|pthread|sysvsem|fcntl|flock|os2sem|tpfcore|none|default </li></ul><ul><li>Default: AcceptMutex default </li></ul><ul><li>Context: server config </li></ul><ul><li>Status: core Compatibility: AcceptMutex is available in Apache 1.3.21 and later. </li></ul><ul><li>AcceptMutex controls which accept() mutex method Apache will us </li></ul>
  15. 15. 3.AccessConfig directive <ul><li>Syntax: AccessConfig file-path|directory-path|wildcard-path </li></ul><ul><li>Default: AccessConfig conf/access.conf </li></ul><ul><li>Context: server config, virtual host </li></ul><ul><li>Status: core </li></ul><ul><li>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. </li></ul>
  16. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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
  29. 29. 12.BS2000Account directive <ul><li>Syntax: BS2000Account account </li></ul><ul><li>Default: none </li></ul><ul><li>Context: server config </li></ul><ul><li>Status: core </li></ul><ul><li>Compatibility: BS2000Account is only available for BS2000 machines, as of Apache 1.3 and later. </li></ul>
  30. 30. 12.BS2000Account directive <ul><li>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). </li></ul>
  31. 31. 13.CGICommandArgs directive <ul><li>Syntax: CGICommandArgs On|Off </li></ul><ul><li>Default: CGICommandArgs On </li></ul><ul><li>Context: directory, .htaccess </li></ul><ul><li>Override: Options </li></ul><ul><li>Status: core </li></ul><ul><li>Compatibility: Available in Apache 1.3.24 and later. </li></ul>
  32. 32. 14.ClearModuleList directive <ul><li>Syntax: ClearModuleList </li></ul><ul><li>Context: server config </li></ul><ul><li>Status: core </li></ul><ul><li>Compatibility: ClearModuleList is only available in Apache 1.2 and later. </li></ul><ul><li>This directive clears the list. It is assumed that the list will then be re-populated using the AddModule directive. </li></ul>
  33. 33. 15.ContentDigest directive <ul><li>Syntax: ContentDigest on|off </li></ul><ul><li>Default: ContentDigest off </li></ul><ul><li>Context: server config, virtual host, directory, .htaccess </li></ul><ul><li>Override: Options </li></ul><ul><li>Status: experimental </li></ul><ul><li>Compatibility: ContentDigest is only available in Apache 1.1 and later </li></ul><ul><li>This directive enables the generation of Content-MD5 headers as defined in RFC1864 respectively RFC2068 </li></ul>
  34. 34. 16.CoreDumpDirectory directive <ul><li>Syntax: CoreDumpDirectory directory-path </li></ul><ul><li>Default: the same location as ServerRoot </li></ul><ul><li>Context: server config </li></ul><ul><li>Status: core </li></ul><ul><li>This controls the directory to which Apache attempts to switch before dumping core. </li></ul>
  35. 35. 17.DefaultType directive <ul><li>Syntax: DefaultType MIME-type </li></ul><ul><li>Default: DefaultType text/plain </li></ul><ul><li>Context: server config, virtual host, directory, .htaccess </li></ul><ul><li>Override: FileInfo </li></ul><ul><li>Status: core </li></ul>
  36. 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. 37. 18.DirectoryMatch <ul><li><DirectoryMatch> </li></ul><ul><li>Syntax: <DirectoryMatch regex> ... </DirectoryMatch> </li></ul><ul><li>Context: server config, virtual host </li></ul><ul><li>Status: Core. </li></ul><ul><li>Compatibility: Available in Apache 1.3 and late </li></ul>
  38. 38. 18.DirectoryMatch <ul><li><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. </li></ul><ul><li>For example: </li></ul><ul><li><DirectoryMatch &quot;^/www/.*/[0-9]{3}&quot;> </li></ul>
  39. 39. 19.DocumentRoot directive <ul><li>DocumentRoot directive </li></ul><ul><li>Syntax: DocumentRoot directory-path </li></ul><ul><li>Default: DocumentRoot /usr/local/apache/htdocs </li></ul><ul><li>Context: server config, virtual host </li></ul><ul><li>Status: core </li></ul><ul><li>This directive sets the directory from which httpd will serve files. </li></ul>
  40. 40. 19.DocumentRoot directive <ul><li>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. </li></ul><ul><li>Example: </li></ul><ul><li>DocumentRoot /usr/web </li></ul><ul><li>then an access to http://www.my.host.com/index.html refers to /usr/web/index.html. </li></ul>
  41. 41. 20.EBCDICConvert <ul><li>Syntax: EBCDICConvert On|Off[=direction] extension [extension] ... </li></ul><ul><li>Context: server config, virtual host, directory, .htaccess </li></ul><ul><li>Status: core </li></ul><ul><li>Override: FileInfo </li></ul><ul><li>Compatibility: The configurable EBCDIC conversion is only available in Apache 1.3.19 and later. </li></ul>
  42. 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. 43. 21.EnableExceptionHook directive <ul><li>Syntax: EnableExceptionHook on|off </li></ul><ul><li>Default: EnableExceptionHook off </li></ul><ul><li>Context: server config </li></ul><ul><li>Status: core </li></ul><ul><li>Compatibility: EnableExceptionHook is available in Apache 1.3.30 and later </li></ul><ul><li>EnableExceptionHook controls whether or not an exception hook implemented by a module will be called after a child process crash. </li></ul>
  44. 44. 22.<Files> directive <ul><li>Syntax: <Files filename> ... </Files> </li></ul><ul><li>Context: server config, virtual host, .htaccess </li></ul><ul><li>Status: core </li></ul><ul><li>Compatibility: only available in Apache 1.2 and above </li></ul><ul><li>The <Files> directive provides for access control by filename. </li></ul>
  45. 45. 23.<FilesMatch> <ul><li>Syntax: <FilesMatch regex> ... </FilesMatch> </li></ul><ul><li>Context: server config, virtual host, .htaccess </li></ul><ul><li>Status: core Compatibility: only available in Apache 1.3 and above. </li></ul><ul><li>The <FilesMatch> directive provides for access control by filename, just as the <Files> directive does. However, it accepts a regular expression. For example: </li></ul><ul><li><FilesMatch &quot;.(gif|jpe?g|png)$&quot;> would match most common Internet graphics formats. </li></ul>
  46. 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.
  47. 47. 24.HostnameLookups directive <ul><li>Syntax: HostnameLookups on|off|double </li></ul><ul><li>Default: HostnameLookups off </li></ul><ul><li>Context: server config, virtual host, directory </li></ul><ul><li>Status: core </li></ul><ul><li>Compatibility: double available only in Apache 1.3 and above. </li></ul><ul><li>Compatibility: Default was on prior to Apache 1.3. </li></ul>
  48. 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.)
  49. 49. 25.IdentityCheck directive <ul><li>Syntax: IdentityCheck on|off </li></ul><ul><li>Default: IdentityCheck off </li></ul><ul><li>Context: server config, virtual host, directory </li></ul><ul><li>Status: core </li></ul><ul><li>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. </li></ul>
  50. 50. 26.<IfDefine> directive <ul><li>Syntax: <IfDefine [!]parameter-name> ... </IfDefine> </li></ul><ul><li>Default: None </li></ul><ul><li>Context: all </li></ul><ul><li>Status: Core </li></ul><ul><li>Compatibility: <IfDefine> is only available in 1.3.1 and later. </li></ul>
  51. 51. 26.<IfDefine> directive <ul><li>The <IfDefine test>...</IfDefine> section is used to mark directives that are conditional. The directives within an IfDefine section are only processed if the test is true. If test is false, everything between the start and end markers is ignored. </li></ul><ul><li>The test in the <IfDefine> section directive can be one of two forms: </li></ul><ul><li>* parameter-name </li></ul><ul><li>* !parameter-name </li></ul>
  52. 52. 26.<IfDefine> directive <ul><li>The directives within an IfDefine section are only processed if the test is true. If test is false, everything between the start and end markers is ignored. </li></ul><ul><li>The test in the <IfDefine> section directive can be one of two forms: </li></ul><ul><li>* parameter-name </li></ul><ul><li>* !parameter-name </li></ul>
  53. 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. 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
  55. 55. 28.KeepAliveTimeout directive <ul><li>Syntax: KeepAliveTimeout seconds </li></ul><ul><li>Default: KeepAliveTimeout 15 </li></ul><ul><li>Context: server config </li></ul><ul><li>Status: Core </li></ul><ul><li>Compatibility: KeepAliveTimeout is only available in Apache 1.1 and later. </li></ul><ul><li>The number of seconds Apache will wait for a subsequent request before closing the connection. </li></ul>
  56. 56. 29.<Limit> directive <ul><li>Syntax: <Limit method [method] ... > ... </Limit> </li></ul><ul><li>Context: any </li></ul><ul><li>Status: core </li></ul><ul><li>Access controls are normally effective for all access methods, and this is the usual desired behavior. In the general case, access control directives should not be placed within a <limit> section </li></ul>
  57. 57. 30.<LimitExcept> directive <ul><li><LimitExcept> directive </li></ul><ul><li>Syntax: <LimitExcept method [method] ... > ... </LimitExcept> </li></ul><ul><li>Context: any </li></ul><ul><li>Status: core </li></ul><ul><li>Compatibility: Available in Apache 1.3.5 and later </li></ul>
  58. 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
  59. 59. 30.<LimitExcept> directive <ul><li>example: </li></ul><ul><li><LimitExcept POST GET> </li></ul><ul><li>Require valid-user </li></ul><ul><li></LimitExcept> </li></ul>
  60. 60. THANK YOU

×