Tuesday, November 9, 2010

Tutorials Server Web on Linux ( Part 1)

Installation server WebPackage web server programs can we take away from the installation CD that is using the Apache Web server, namely Apache version 1.3.12. Apache Web Server package can be installed using following command:
# Rpm-ivh apache-1.3.12.rpm
When installation is complete then the files to note are:
  1. httpd.conf
  2. access.conf
  3. srm.conf
each of the above files will be discussed later.

Apache Configuration
Httpd.conf
Here are the contents of the httpd.conf file:
1.ServerType. Which describes the server configuration, whether run through inetd or run independently.
When you are standing only, then the server will be run manually.
2.ServerRoot. A directory path where the stored configuration file, the file error.
3.PidFile. The file that stores the number of apache processes running.
4.ResourceConfig and AccessConfig. The contents of the file is the configuration for the directory source
(Access.conf) and configuration of access permissions (srm.conf). The second file is a supplemental (optional), because they can be placed in httpd.conf, or can be placed in each file (access.conf and srm.conf)
5.Timeout. Limit time spent on a assume a connection is lost, ie when there is no response from the client.
6.KeepAlive. The ability of a server receiving requests simultaneously from one connection.
7.MaxKeepAliveRequests. The maximum number of requests received by the server simultaneously.
8.KeepAliveTimeout. Specified time to wait for the next request from one connection.
MinSpareServers and MaxSpareServers. The number of servers needed to serve each request
intake. (normally used for a very busy web site)
9.StartServers. The number of servers run by apache for initialization when the apache first time in execution.
10.MaxClients. The number of simultaneous connections allowed on the server.
11.MaxRequestsPerChild. The number of requests that will be served by the child server before the child turned off the server.
12.BindAddress-Server will automatically translate any address any ip address that is on the server
13.Port. Ports to be in "listen" by the Apache web server.
14.User and Group. User and group that runs the Apache web server.
15.ServerAdmin. The email address of the web server administrator.
16.ServerName. Name servers are tailored to the FQDN (Full Qualified Domain Name), serves as the name of our web server.
17.ErrorLog. Directory and file name where we put the error log of apache.
18.LogLevel. Types of log messages that are logged by the web server. There are several categories that will be recorded in the log file, which is emerg (emergency), alert, crit (critical), errors, warn, debug.
19.LogFormat. This section determine log file format and also gives the "nickname" for that format.
This section has been provided by default by apache, and should not have to be changed (unless you are
definitely know what you do:))
20.CustomLog. Log in configured to record each access request from the client. Also used
to record by default VirtualHost configuration (see VirtualHost)
21.ServerSignature. Web Server Signature commonly occurs when the file is searched and not found at ftp. (On, off and email)
22.UseCanonicalName. This section to configure Apache server to make reference to his own use and Port accordance Server Name in httpd.conf, if set off, then the server will
respond in accordance with client request.
23.HostnameLookups. This command will me log IP address of every client that accesses our server. It is recommended that this section is set off to site2 very busy, because it will be able to create log files become large.

Files srm.conf
Srm.conf files are also used to manage problems associated with the directory, Document Root, UserDir, DirectoryIndex, MIME (Multi purpose Internet Mail Extension), ScriptAlias, CGI-script and definitions of other extensions, such as PHP, Perl and others. The contents of srm.conf are:

1.DocumenRoot. Path of the directory containing the main document files from our site.
2.UserDir. Directory for users who are usually located in the home directory of the user. URL used to access the http://server.kita.com/ ~ user <- use a ~.
3.DirectoryIndex. First file will be accessed by the client when the client will access our web server.
4.FancyIndexing. A way of displaying the contents of a directory on the server. Using fancy style or not. Once this configuration is usually followed by defining the path looking icons that will be used for indexing.
5.AccessFileName. Defining a file access that will be used to protect a directory. Usually called. Httaccess (signs. Means the file on the hidden and for the sake of security, the file name httaccess replaced)
6.Alias. Directory alias is used for some specific directory, eg cgi-bin.
7.DefaultType. Default type of each document that is on our web server.


    Other related articles:

No comments:

Post a Comment