Reading
If you haven't already, please make sure that you have read chapters 12-21 in LAH, and chapter 13 in WS2008.
Web services and email
Two of the most popular services visibly provided by servers are email and web-type services.
Full email
setups generally consists of an MTA such as sendmail or postfix, a delivery agent such as procmail or dropmail, a pop/imap
server, and perhaps a webmail interface such as openwebmail, Outlook Web Access (OWA), horde, or squirrelmail.
They may also include
various spam and virus programs, such as MailScanner, spamassassin, avis, clamav, dcc, razor, and many others, and
other mail types of mail filters such as the popular milter library programs (e.g., milter-ahead).
Web services generally center around an Apache web server, some
CGI-friendly regime such as Perl (anywhere from embedded Perl
to mod_perl with any of the numerous CGI packages), Python,
PHP, Ruby, JSP, ASP, and a database such as MySQL, Postgresql, Oracle,
or SQLite. It may also include other bits such as SOAP or RSS
services.
Email: sendmail
Sendmail functions as a MTA (and also a RFC 2476 MSA). It is generally configured to listen to port 25 (and 587 for MSA functions, and maybe on 465 for SSL connections (if so, usually requires authentication like an MSA)), and the configuration files are now generally stored in /etc/mail.
The primary configuration for administrators typically is /etc/mail/sendmail.mc This contains m4 directives to control the creation of /etc/mail/sendmail.cf
Sendmail is quite powerful. A common application for sendmail is to serve
as a gateway mail server.
(You can also do this type of thing with Exchange; see Microsoft's
website for a document called ``Using a Windows SMTP Relay Server in a Perimeter Network'' which gives an overview, and for details, look at ``How to Configure a Windows Server 2003 Server as a Relay Server or Smart Host''.)
One quite clever idea came from MailScanner's author, Julian Field at the University of Southampton. Email going into sendmail is put into a queue, and instead of the usual process of another sendmail process acting as a queue handler to deliver it, MailScanner first processes the mail (looking for spam and viruses, and comparing it against blacklists and whitelists), and then enqueues the message into a different queue directory for the second sendmail queue handler to find. (You can often view mail queues with the alias ``mailq'' which actually is ``sendmail -bp'' (or postfix's ``postqueue -f''.)
As we saw from the .mc files, sendmail doesn't actually do local delivery of email. Ordinary delivery is typically by
procmail (other candidates include the old binmail program or dropmail.
procmail is a very powerful mail delivery agent; it can be configured to do many, many things. See http://www.procmail.org for ``recipes''. For instance, a typical procmail recipe might look like:
:0
* ^From: unpleasant@user.com
/dev/null
:0:
${DEFAULT}
Headsup: procmail is very picky about such items as colons. A single missing colon can be very bad since it might be one that indicates that a mailbox is to be locked before it receives a delivery -- and failing to lock a shared mailbox file might prove unpleasant.
Finally, you have to decide one (or perhaps two more) things about delivery: do you want email to go into a traditional
ymbox, which is just one long file of email separated by the delimiter ^From .*\n or do you want to use the
more modern maildir approach, where each email is written to a separate file? I think that the latter is preferable. If you
do choose to go with mbox format, you will also have to make sure that your locking mechanisms for procmail, imap/pop,
and any other client software such as openwebmail all agree to a common locking mechanism.
Main SMTP commands
- HELO / EHLO
- MAIL FROM:
- RCPT TO:
- DATA
- QUIT
Example over port 25 with SMTP
$ telnet mail.cs.fsu.edu 25
Trying 128.186.120.4...
Connected to mail.cs.fsu.edu.
Escape character is '^]'.
220 mail.cs.fsu.edu ESMTP Postfix
ehlo sophie.cs.fsu.edu
250-mail.cs.fsu.edu
250-PIPELINING
250-SIZE 20000000
250-VRFY
250-ETRN
250-STARTTLS
250-XVERP
250 8BITMIME
mail from:
250 Ok
rcpt to:
250 Ok
data
data
354 End data with .
Subject: test
this is a test
.
250 Ok: queued as 62F28F2F8B
helo cs.fsu.edu
250 mail.cs.fsu.edu
quit
221 Bye
Connection closed by foreign host.
Example over port 465 with SMTPS
$ openssl s_client -connect SOMESERVER.com:465
CONNECTED(00000004)
depth=0 /C=US/ST=State/L=Locality/O=Org/CN=SOMESERVER.com/emailAddress=postmaster@SOMESERVER.com
verify error:num=18:self signed certificate
verify return:1
depth=0 /C=US/ST=State/L=Locality/O=Org/CN=SOMESERVER.com/emailAddress=postmaster@SOMESERVER.com
verify return:1
---
Certificate chain
0 s:/C=US/ST=State/L=Locality/O=Org/CN=SOMESERVER.com/emailAddress=postmaster@SOMESERVER.com
i:/C=US/ST=State/L=Locality/O=Org/CN=SOMESERVER.com/emailAddress=postmaster@SOMESERVER.com
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIG6zCCBNOgAwIBAgIJAJ0jGHcUbbn3MA0GCSqGSIb3DQEBBQUAMIGpMQswCQYD
[...]
gFfs6T2dG8rxVEVusqJ5LLBWpol+VF1PMWv+GTevnmr//GdpVqmSC8WoHRLOcsG8
V+p5QtYlfg/dgnOdutslxJYRRfiaya5wZ6v+6GSpjA9ATALU2uNv+vnFqictz2o=
-----END CERTIFICATE-----
subject=/C=US/ST=State/L=Locality/O=Org/CN=SOMESERVER.com/emailAddress=postmaster@SOMESERVER.com
issuer=/C=US/ST=State/L=Locality/O=Org/CN=SOMESERVER.com/emailAddress=postmaster@SOMESERVER.com
---
No client certificate CA names sent
---
SSL handshake has read 2730 bytes and written 346 bytes
---
New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA
Server public key is 4096 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1
Cipher : DHE-RSA-AES256-SHA
Session-ID: 5622E6CCB91C3F50B0F110CAD51AB664B24445B4D15330F3F0F2A0001AF62066
Session-ID-ctx:
Master-Key: E8129E24CC49492FF3EB73391E0D17C9716CCAB77976B387FAA6C54FA426E38CD4DDDF901449C356FFA5FBE3CF1FFA43
Key-Arg : None
Krb5 Principal: None
Start Time: 1288105044
Timeout : 300 (sec)
Verify return code: 18 (self signed certificate)
---
220 SOMESERVER.com ESMTP
helo sophie.cs.fsu.edu
250 SOMESERVER.com
mail from:
250 2.1.0 Ok
rcpt to:
554 5.7.1 : Client host rejected: Access denied
helo sophie.cs.fsu.edu
250 SOMESERVER.com
quit
221 2.0.0 Bye
read:errno=0
Configuring Postfix
There are two primary files for configuring Postfix, main.cf and
master.cf
The file main.cf contains all of the optional bits that you might
want to set, including to consult other sources of data such as flat files,
GDB database files, and relational databases.
Here's a relatively unconfigured version of main.cf.
What are some of the changes that we might make to that file?
#
# down around line 110, change the list of interfaces we listen to include all interfaces:
#
#inet_interfaces = localhost # original value
inet_interfaces = all # new value
#
# down around line 240, if this is an isolated machine, change the mynetworks_style to only
# accept this machine as its "mynetworks"
#
mynetworks_style = host
#
# VIRTUAL hosting changes: if we are going to do virtual hosting (something that Postfix is
# natively quite good at), some changes we might want to make
#
virtual_mailbox_base = /PATH_TO_VIRTUAL/mail
virtual_mailbox_domains = pgsql:/etc/postfix/virtual_mailbox_domains.cf
virtual_mailbox_maps = pgsql:/etc/postfix/virtual_mailbox_maps.cf
virtual_alias_maps = pgsql:/etc/postfix/virtual_aliases.cf
virtual_minimum_uid = 30000
virtual_uid_maps = static:30000
virtual_gid_maps = static:30000
#
# if we support "user+mailbox" addressing, we need this
#
recipient_delimiter = +
#
# if we are doing virtual users, then we need to provide a way for them to
# authenticate to postfix. this method leverages dovecot's authentication, which
# makes sense for virtual users who also use dovecot to have imap/pop access
# to their email.
#
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
smtpd_sasl_auth_enable = yes
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_sasl_authenticated reject_unauth_destination
#
# we probably want to support TLS these days...
#
smtp_tls_session_cache_database = btree:/var/lib/postfix/smtp_tls_session_cache
smtp_tls_security_level = may
smtpd_tls_cert_file = /etc/postfix/cert.pem
smtpd_tls_key_file = /etc/postfix/privkey.pem
smtpd_tls_received_header = yes
smtpd_tls_session_cache_database = btree:/var/lib/postfix/smtpd_tls_session_cache
tls_random_source = dev:/dev/urandom
# Postfix 2.3 and later
smtpd_tls_security_level = may
# Obsolete, but still supported
smtpd_use_tls = yes
#
# spam control, RBLs
#
smtpd_helo_required = yes
strict_rfc821_envelopes = yes
disable_vrfy_command = yes
#
smtpd_client_restrictions =
permit_mynetworks
check_client_access hash:/etc/postfix/client_access
reject_unknown_client_hostname
reject_rbl_client sbl.spamhaus.org
reject_rbl_client xbl.spamhaus.org
sleep 6
reject_unauth_pipelining
#
smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/sender_access
#
# finally, tell postfix where amavisd-new is found
#
content_filter = smtp-SOMEFILTER:[127.0.0.1]:SOMEPORT
#
# allow bigger messages
#
message_size_limit = 50000000
And now, master.cf
Here's a typical master.cf. As the man page for master(5) puts it:
Postfix services are implemented by daemon processes. These run in the background under control of the master(8) process. The master.cf
configuration file defines how a client program connects to a service, and what daemon program runs when a service is requested.
Most daemon processes are short-lived and terminate voluntarily after serving max_use clients, or after inactivity for max_idle or more
units of time.
[ ... and on down a bit ... ]
Each logical line defines a single Postfix service. Each service is identified by its name and type as described below. When
multiple lines specify the same service name and type, only the last one is remembered. Otherwise, the order of master.cf service
definitions does not matter.
Here are some changes that one might make to a master.cf file:
#
# Send general email to a local spam filter running as a daemon; this could be spamd, amavisd,
# MailScanner, spamassassin, ...
#
127.0.0.1:smtp inet n - n - - smtpd
-o content_filter=
#
# Exempt email that comes in from MSA or SMTPS (assumes both require authentication, see above),
# and also email that comes over the loopback interface
#
submission inet n - n - - smtpd
-o content_filter=
-o smtpd_enforce_tls=yes
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=permit_sasl_authenticated,reject
smtps inet n - n - - smtpd
-o content_filter=
-o smtpd_tls_wrappermode=yes
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=permit_sasl_authenticated,reject
127.0.0.1:smtp inet n - n - - smtpd
-o content_filter=
#
# how to handle spam filter
#
smtp-FILTER unix - - n - 2 smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=no
-o max_use=20
127.0.0.1:10025 inet n - n - - smtpd
-o smtpd_client_restrictions=permit_mynetworks,reject
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o smtpd_data_restrictions=reject_unauth_pipelining
-o mynetworks=127.0.0.0/8
-o smtpd_error_sleep_time=0
-o smtpd_soft_error_limit=1001
-o smtpd_hard_error_limit=1000
-o smtpd_client_connection_count_limit=0
-o smtpd_client_connection_rate_limit=0
-o receive_override_options=no_header_body_checks,no_unknown_recipient_checks
Maildirs, from Dr. Bernstein (see http://cr.yp.to/proto/maildir.html)
Maildirs are safer in many ways that the traditional mbox format. On LAH p. 549, the problems with traditional mailbox locking are discussed, as they are on the maildir webpage.
Maildirs keep every email message in a separate file, and never use any type of locking mechanism.
Traditional mailbox (mbox) format is not safe over NFS.
Every maildir setup will have the subdirectories tmp, new, and cur, and may have others. Mail is first delivered to tmp, then safely moved to new. It may have others, also.
HOW A MESSAGE IS DELIVERED
The tmp directory is used to ensure reliable delivery, as
discussed here.
A program delivers a mail message in six steps. First, it
chdir()s to the maildir directory. Second, it stat()s the
name tmp/time.pid.host, where time is the number of seconds
since the beginning of 1970 GMT, pid is the program's
process ID, and host is the host name. Third, if stat()
returned anything other than ENOENT, the program sleeps for
two seconds, updates time, and tries the stat() again, a
limited number of times. Fourth, the program creates
tmp/time.pid.host. Fifth, the program NFS-writes the
message to the file. Sixth, the program link()s the file to
new/time.pid.host. At that instant the message has been
successfully delivered.
[ ... ]
NFS-writing means (1) as usual, checking the number of bytes
returned from each write() call; (2) calling fsync() and
checking its return value; (3) calling close() and checking
its return value. (Standard NFS implementations handle
fsync() incorrectly but make up for it by abusing close().)
imap and pop
dovecot: an increasingly popular imap and pop server is dovecot, which handles mbox and maildir
format with aplomb. It also handles virtual users quite well, including those existing only in databases.
courier: also popular.
cyrus: uses its own mailbox format; it is more formidable to configure than other imap setups.
What is imap/pop? These are protocols that allow a user to remotely retrieve email from a mailhost. imap (RFC 3501), unlike
pop (RFC 1939), supports the idea of separate folders on the server machine, and it has more functionality built in. Generally, you leave your mail messages on an imap server, and you retrieve them from a pop server.
The main commands for POP are
- USER username
- PASS password
- LIST
- RETR item
- DELE item
- QUIT
- RSET
IMAP commands are ``tagged''. This means that you need to put a short, unique identifier before you use a command; the response to that command will use the same tag. The main commands for IMAP checking are
- [tag] LOGIN username password
- [tag] SELECT mailbox
- [tag] LIST "" *
- [tag] LOGOUT
Email Clients
There are two types of clients: (1) those that read email via a protocol such as IMAP, POP, or the ``Microsoft'' way, and (2) those that access mail via a filesystem.
Web clients: The very popular squirrelmail (http://www.squirrelmail.org) is an example of type (1) that uses IMAP. openwebmail (http://www.openwebmail.org) is an example of (2). It reads directly from either MBOX or Maildir format.
Dedicated interface clients: most of these now handle both file stores and IMAP/POP. Examples include Outlook, Thunderbird, Evolution, Sylpheed, Eudora, Pegasus, and a host of others.
Working on the latter setups can be interesting since the client can silently be going to entirely different machines also for its email.
I have worked on a setup where just determining where the client email was coming from required using
tcpdump and lots of patience; in that case, a single user was having a problem accessing his mailbox: it turned out that the client interface (a very old version of a web email client) could not handle bad headers in email messages; it could not handle very large messages; and it was configured to terminate any handler that took longer than 30 seconds, so it could not ever handle a mailbox that had a large number of messages to move -- it used POP instead of IMAP, and thus ended up initially doing RETR, then DELE after it had pulled the messages into a maildir-like format.
Web services and email: web services
An important web service is simple delivery of html over http (hypertext
transfer protocol).
The current version of http in use is 1.1, defined in RFC 2616. (There was an early stab at an http 1.2, but it didn't jell.)
Netcraft survey
The most popular webserver is the Apache webserver, with an overall 46% market share according to Netcraft's current webserver survey, and
powers 67% of the most active sites.
http://news.netcraft.com/archives/web_server_survey.html
Apache has two versions, 1.3 and the 2.x versions, but 1.3 is now considered a ``legacy'' system and Apache now recommends:
``Apache 1.3.41 is the current stable release of the Apache 1.3 family.
We strongly recommend that users of all earlier versions, including 1.3
family release, upgrade to to the current 2.2 version as soon as possible.''
http://www.apache.org/dist/httpd/Announcement1.3.html
Conversations over http
What does a typical conversation look like? Here's one request and answer for a page:
Hypertext Transfer Protocol
GET /rfcs/rfc2612.html HTTP/1.1
Request Method: GET
Request URI: /rfcs/rfc2612.html
Request Version: HTTP/1.1
Host: www.faqs.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12)
Gecko/20060202 Red Hat/1.7.12-1.1.3.4.centos3
Accept: text/xml,application/xml,application/xhtml+xml,text/html;
q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Hypertext Transfer Protocol
HTTP/1.1 200 OK
Request Version: HTTP/1.1
Response Code: 200
Date: Thu, 23 Feb 2006 16:26:31 GMT
Server: Apache
Last-Modified: Thu, 23 Feb 2006 07:01:53 GMT
ETag: "5f8977-910a-43fd5de1"
Accept-Ranges: bytes
Content-Length: 37130
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
Line-based text data: text/html
< !DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
< HTML>
< HEAD>
< TITLE>RFC 2612 (rfc2612) - The CAST-256 Encryption Algorithm< /TITLE>
< META name="description" content="RFC 2612 - The CAST-256 Encryption
Algorithm">
< script language="JavaScript1.2">
function erfc(s)
{document.write("< A href="/rfccomment.php?rfcnum="+s+""
target="_blank" onclick="window.open('/rfccomment.php?rfcnum="+s+"',
'Popup','toolbar=no,location=no,status=no,menubar=no,scrollbars=yes,
resizable=yes,width=680,height=530,left=30
//-->
< /script>
< /HEAD>
< BODY BGCOLOR="#ffffff" TEXT="#000000">
< P ALIGN=CENTER>< IMG SRC="/images/library.jpg" HEIGHT=62 WIDTH=150 BORDER="0"
ALIGN="MIDDLE" ALT="">< /P>
< H1 ALIGN=CENTER>RFC 2612 (RFC2612)< /H1>
< P ALIGN=CENTER>Internet RFC/STD/FYI/BCP Archives< /P>
< DIV ALIGN=CENTER>[ < a href="/rfcs/">RFC Index< /a> | < A HREF="/rfcs/rfcsearch.html">
RFC Search< /A> | < a href="/faqs/">Usenet FAQs< /a> | < a href="/contrib/">Web FAQs< /a>
| < a href="/docs/">Documents< /a> | < a href="http://www.city-data.com/"
< P>
< STRONG>Alternate Formats:< /STRONG>
< A HREF="/ftp/rfc/rfc2612.txt">rfc2612.txt< /A> |
< A HREF="/ftp/rfc/pdf/rfc2612.txt.pdf">rfc2612.txt.pdf< /A>< /DIV>
< p align=center>< script language="JavaScript">< !--
erfc("2612");
// -->< /script>< /p>
< h3 align=center>RFC 2612 - The CAST-256 Encryption Algorithm< /h3>
< HR SIZE=2 NOSHADE>
< TT>
Network Working Group C. Adams
Request for Comments: 2612 J. Gilchrist
Category: Informational Entrust Technologies
June 1999
The CAST-256 Encryption Algorithm
Status of this Memo
Another HTTP Request
Here's a request and ``not modified'' answer for a page:
Hypertext Transfer Protocol
GET /rfcs/rfc2616.html HTTP/1.1
Request Method: GET
Request URI: /rfcs/rfc2616.html
Request Version: HTTP/1.1
Host: www.faqs.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12)
Gecko/20060202 Red Hat/1.7.12-1.1.3.4.centos3
Accept: text/xml,application/xml,application/xhtml+xml,text/html;
q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://www.google.com/search?num=100&hl=en&lr=&q=http+protocol+rfc&btnG=Search
If-Modified-Since: Thu, 23 Feb 2006 07:01:53 GMT
If-None-Match: ``5f897b-63239-43fd5de1''
Cache-Control: max-age=0
Hypertext Transfer Protocol
HTTP/1.1 304 Not Modified
Request Version: HTTP/1.1
Response Code: 304
Date: Thu, 23 Feb 2006 16:11:36 GMT
Server: Apache
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
ETag: "5f897b-63239-43fd5de1"
Encoding and chunking
While in theory encoding allows for any type of arbitrary
encoding of the body, http level encoding in practice is used to allow a server to optimize its use of
bandwidth by optionally choosing when it would like to compress or gzip a body.
Chunking is almost the reverse: it instead embeds redundant information into the message
body to let the client make decisions about buffering and early rendering of data. If chunking occurs,
it is usually for dynamically generated data.
Configuring Apache
Where you put your configuration data varies widely; while /etc/httpd is certainly common,
you also might see /etc/apache2 and other places. Also widely varying is where you might find
your actual html files, the ``documentroot''. On Redhat machines, /var/www/html has been the default directory.
On OpenSuse, you would see /srv/www/htdocs.
The most important configuration file is httpd.conf
httpd.conf from 2.2 distribution
# #
# # This is the main Apache server configuration file. It contains the
# # configuration directives that give the server its instructions.
# # See < URL:http://httpd.apache.org/docs/2.2/> for detailed information.
# # In particular, see
# # < URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# # for a discussion of each configuration directive.
# #
# #
# # Do NOT simply read the instructions in here without understanding
# # what they do. They're here only as hints or reminders. If you are unsure
# # consult the online docs. You have been warned.
# #
# # The configuration directives are grouped into three basic sections:
# # 1. Directives that control the operation of the Apache server process as a
# # whole (the 'global environment').
# # 2. Directives that define the parameters of the 'main' or 'default' server,
# # which responds to requests that aren't handled by a virtual host.
# # These directives also provide default values for the settings
# # of all virtual hosts.
# # 3. Settings for virtual hosts, which allow Web requests to be sent to
# # different IP addresses or hostnames and have them handled by the
# # same Apache server process.
# #
# # Configuration and logfile names: If the filenames you specify for many
# # of the server's control files begin with "/" (or "drive:/" for Win32), the
# # server will use that explicit path. If the filenames do *not* begin
# # with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# # with ServerRoot set to "/etc/httpd" will be interpreted by the
# # server as "/etc/httpd/logs/foo.log".
# #
# ### Section 1: Global Environment
# #
# # The directives in this section affect the overall operation of Apache,
# # such as the number of concurrent requests it can handle or where it
# # can find its configuration files.
# #
# #
# # Don't give away too much information about all the subcomponents
# # we are running. Comment out this line if you don't mind remote sites
# # finding out what major optional modules you are running
# ServerTokens OS
# #
# # ServerRoot: The top of the directory tree under which the server's
# # configuration, error, and log files are kept.
# #
# # NOTE! If you intend to place this on an NFS (or otherwise network)
# # mounted filesystem then please read the LockFile documentation
# # (available at < URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>);
# # you will save yourself a lot of trouble.
# #
# # Do NOT add a slash at the end of the directory path.
# #
# ServerRoot "/etc/httpd"
# #
# # PidFile: The file in which the server should record its process
# # identification number when it starts.
# #
# PidFile run/httpd.pid
# #
# # Timeout: The number of seconds before receives and sends time out.
# #
# Timeout 120
# #
# # KeepAlive: Whether or not to allow persistent connections (more than
# # one request per connection). Set to "Off" to deactivate.
# #
# KeepAlive Off
# #
# # MaxKeepAliveRequests: The maximum number of requests to allow
# # during a persistent connection. Set to 0 to allow an unlimited amount.
# # We recommend you leave this number high, for maximum performance.
# #
# MaxKeepAliveRequests 100
# #
# # KeepAliveTimeout: Number of seconds to wait for the next request from the
# # same client on the same connection.
# #
# KeepAliveTimeout 15
# ##
# ## Server-Pool Size Regulation (MPM specific)
# ##
# # prefork MPM
# # StartServers: number of server processes to start
# # MinSpareServers: minimum number of server processes which are kept spare
# # MaxSpareServers: maximum number of server processes which are kept spare
# # ServerLimit: maximum value for MaxClients for the lifetime of the server
# # MaxClients: maximum number of server processes allowed to start
# # MaxRequestsPerChild: maximum number of requests a server process serves
# < IfModule prefork.c>
# StartServers 8
# MinSpareServers 5
# MaxSpareServers 20
# ServerLimit 256
# MaxClients 256
# MaxRequestsPerChild 4000
# < /IfModule>
# # worker MPM
# # StartServers: initial number of server processes to start
# # MaxClients: maximum number of simultaneous client connections
# # MinSpareThreads: minimum number of worker threads which are kept spare
# # MaxSpareThreads: maximum number of worker threads which are kept spare
# # ThreadsPerChild: constant number of worker threads in each server process
# # MaxRequestsPerChild: maximum number of requests a server process serves
# < IfModule worker.c>
# StartServers 2
# MaxClients 150
# MinSpareThreads 25
# MaxSpareThreads 75
# ThreadsPerChild 25
# MaxRequestsPerChild 0
# < /IfModule>
# #
# # Listen: Allows you to bind Apache to specific IP addresses and/or
# # ports, in addition to the default. See also the < VirtualHost>
# # directive.
# #
# # Change this to Listen on specific IP addresses as shown below to
# # prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
# #
# #Listen 12.34.56.78:80
# #
# # Dynamic Shared Object (DSO) Support
# #
# # To be able to use the functionality of a module which was built as a DSO you
# # have to place corresponding `LoadModule' lines at this location so the
# # directives contained in it are actually available _before_ they are used.
# # Statically compiled modules (those listed by `httpd -l') do not need
# # to be loaded here.
# #
# # Example:
# # LoadModule foo_module modules/mod_foo.so
# #
# LoadModule auth_basic_module modules/mod_auth_basic.so
# LoadModule auth_digest_module modules/mod_auth_digest.so
# LoadModule authn_file_module modules/mod_authn_file.so
# LoadModule authn_alias_module modules/mod_authn_alias.so
# LoadModule authn_anon_module modules/mod_authn_anon.so
# LoadModule authn_dbm_module modules/mod_authn_dbm.so
# LoadModule authn_default_module modules/mod_authn_default.so
# LoadModule authz_host_module modules/mod_authz_host.so
# LoadModule authz_user_module modules/mod_authz_user.so
# LoadModule authz_owner_module modules/mod_authz_owner.so
# LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
# LoadModule authz_dbm_module modules/mod_authz_dbm.so
# LoadModule authz_default_module modules/mod_authz_default.so
# LoadModule ldap_module modules/mod_ldap.so
# LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
# LoadModule include_module modules/mod_include.so
# LoadModule log_config_module modules/mod_log_config.so
# LoadModule logio_module modules/mod_logio.so
# LoadModule env_module modules/mod_env.so
# LoadModule ext_filter_module modules/mod_ext_filter.so
# LoadModule mime_magic_module modules/mod_mime_magic.so
# LoadModule expires_module modules/mod_expires.so
# LoadModule deflate_module modules/mod_deflate.so
# LoadModule headers_module modules/mod_headers.so
# LoadModule usertrack_module modules/mod_usertrack.so
# LoadModule setenvif_module modules/mod_setenvif.so
# LoadModule mime_module modules/mod_mime.so
# LoadModule dav_module modules/mod_dav.so
# LoadModule status_module modules/mod_status.so
# LoadModule autoindex_module modules/mod_autoindex.so
# LoadModule info_module modules/mod_info.so
# LoadModule dav_fs_module modules/mod_dav_fs.so
# LoadModule vhost_alias_module modules/mod_vhost_alias.so
# LoadModule negotiation_module modules/mod_negotiation.so
# LoadModule dir_module modules/mod_dir.so
# LoadModule actions_module modules/mod_actions.so
# LoadModule speling_module modules/mod_speling.so
# LoadModule userdir_module modules/mod_userdir.so
# LoadModule alias_module modules/mod_alias.so
# LoadModule rewrite_module modules/mod_rewrite.so
# LoadModule proxy_module modules/mod_proxy.so
# LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
# LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
# LoadModule proxy_http_module modules/mod_proxy_http.so
# LoadModule proxy_connect_module modules/mod_proxy_connect.so
# LoadModule cache_module modules/mod_cache.so
# LoadModule suexec_module modules/mod_suexec.so
# LoadModule disk_cache_module modules/mod_disk_cache.so
# LoadModule cgi_module modules/mod_cgi.so
# #
# # The following modules are not loaded by default:
# #
# #LoadModule cern_meta_module modules/mod_cern_meta.so
# #LoadModule asis_module modules/mod_asis.so
# #
# # Load config files from the config directory "/etc/httpd/conf.d".
# #
#Include conf.d/*.conf
Include conf.d/ssl.conf
# #
# # ExtendedStatus controls whether Apache will generate "full" status
# # information (ExtendedStatus On) or just basic information (ExtendedStatus
# # Off) when the "server-status" handler is called. The default is Off.
# #
# #ExtendedStatus On
# #
# # If you wish httpd to run as a different user or group, you must run
# # httpd as root initially and it will switch.
# #
# # User/Group: The name (or #number) of the user/group to run httpd as.
# # . On SCO (ODT 3) use "User nouser" and "Group nogroup".
# # . On HPUX you may not be able to use shared memory as nobody, and the
# # suggested workaround is to create a user www and use that user.
# # NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
# # when the value of (unsigned)Group is above 60000;
# # don't use Group #-1 on these systems!
# #
User apache
Group apache
# ### Section 2: 'Main' server configuration
# #
# # The directives in this section set up the values used by the 'main'
# # server, which responds to any requests that aren't handled by a
# # < VirtualHost> definition. These values also provide defaults for
# # any < VirtualHost> containers you may define later in the file.
# #
# # All of these directives may appear inside < VirtualHost> containers,
# # in which case these default settings will be overridden for the
# # virtual host being defined.
# #
# #
# # ServerAdmin: Your address, where problems with the server should be
# # e-mailed. This address appears on some server-generated pages, such
# # as error documents. e.g. admin@your-domain.com
# #
# ServerAdmin root@localhost
# #
# # ServerName gives the name and port that the server uses to identify itself.
# # This can often be determined automatically, but we recommend you specify
# # it explicitly to prevent problems during startup.
# #
# # If this is not set to valid DNS name for your host, server-generated
# # redirections will not work. See also the UseCanonicalName directive.
# #
# # If your host doesn't have a registered DNS name, enter its IP address here.
# # You will have to access it by its address anyway, and this will make
# # redirections work in a sensible way.
# #
# #ServerName www.example.com:80
# #
# # UseCanonicalName: Determines how Apache constructs self-referencing
# # URLs and the SERVER_NAME and SERVER_PORT variables.
# # When set "Off", Apache will use the Hostname and Port supplied
# # by the client. When set "On", Apache will use the value of the
# # ServerName directive.
# #
# UseCanonicalName Off
# #
# # DocumentRoot: The directory out of which you will serve your
# # documents. By default, all requests are taken from this directory, but
# # symbolic links and aliases may be used to point to other locations.
# #
# DocumentRoot "/var/www/html"
# #
# # Each directory to which Apache has access can be configured with respect
# # to which services and features are allowed and/or disabled in that
# # directory (and its subdirectories).
# #
# # First, we configure the "default" to be a very restrictive set of
# # features.
# #
# < Directory />
# Options FollowSymLinks
# AllowOverride None
# < /Directory>
# #
# # Note that from this point forward you must specifically allow
# # particular features to be enabled - so if something's not working as
# # you might expect, make sure that you have specifically enabled it
# # below.
# #
# #
# # This should be changed to whatever you set DocumentRoot to.
# #
# < Directory "/var/www/html">
# #
# # Possible values for the Options directive are "None", "All",
# # or any combination of:
# # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# #
# # Note that "MultiViews" must be named *explicitly* --- "Options All"
# # doesn't give it to you.
# #
# # The Options directive is both complicated and important. Please see
# # http://httpd.apache.org/docs/2.2/mod/core.html#options
# # for more information.
# #
# Options Indexes FollowSymLinks
# #
# # AllowOverride controls what directives may be placed in .htaccess files.
# # It can be "All", "None", or any combination of the keywords:
# # Options FileInfo AuthConfig Limit
# #
# AllowOverride None
# #
# # Controls who can get stuff from this server.
# #
# Order allow,deny
# Allow from all
# < /Directory>
# #
# # UserDir: The name of the directory that is appended onto a user's home
# # directory if a ~user request is received.
# #
# # The path to the end user account 'public_html' directory must be
# # accessible to the webserver userid. This usually means that ~userid
# # must have permissions of 711, ~userid/public_html must have permissions
# # of 755, and documents contained therein must be world-readable.
# # Otherwise, the client will only receive a "403 Forbidden" message.
# #
# # See also: http://httpd.apache.org/docs/misc/FAQ.html#forbidden
# #
# < IfModule mod_userdir.c>
# #
# # UserDir is disabled by default since it can confirm the presence
# # of a username on the system (depending on home directory
# # permissions).
# #
# UserDir disabled
# #
# # To enable requests to /~user/ to serve the user's public_html
# # directory, remove the "UserDir disabled" line above, and uncomment
# # the following line instead:
# #
# #UserDir public_html
# < /IfModule>
# #
# # Control access to UserDir directories. The following is an example
# # for a site where these directories are restricted to read-only.
# #
# #< Directory /home/*/public_html>
# # AllowOverride FileInfo AuthConfig Limit
# # Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# # < Limit GET POST OPTIONS>
# # Order allow,deny
# # Allow from all
# # < /Limit>
# # < LimitExcept GET POST OPTIONS>
# # Order deny,allow
# # Deny from all
# # < /LimitExcept>
# #< /Directory>
# #
# # DirectoryIndex: sets the file that Apache will serve if a directory
# # is requested.
# #
# # The index.html.var file (a type-map) is used to deliver content-
# # negotiated documents. The MultiViews Option can be used for the
# # same purpose, but it is much slower.
# #
# DirectoryIndex index.html index.html.var
# #
# # AccessFileName: The name of the file to look for in each directory
# # for additional configuration directives. See also the AllowOverride
# # directive.
# #
# AccessFileName .htaccess
# #
# # The following lines prevent .htaccess and .htpasswd files from being
# # viewed by Web clients.
# #
# < Files ~ "^\.ht">
# Order allow,deny
# Deny from all
# < /Files>
# #
# # TypesConfig describes where the mime.types file (or equivalent) is
# # to be found.
# #
# TypesConfig /etc/mime.types
# #
# # DefaultType is the default MIME type the server will use for a document
# # if it cannot otherwise determine one, such as from filename extensions.
# # If your server contains mostly text or HTML documents, "text/plain" is
# # a good value. If most of your content is binary, such as applications
# # or images, you may want to use "application/octet-stream" instead to
# # keep browsers from trying to display binary files as though they are
# # text.
# #
# DefaultType text/plain
# #
# # The mod_mime_magic module allows the server to use various hints from the
# # contents of the file itself to determine its type. The MIMEMagicFile
# # directive tells the module where the hint definitions are located.
# #
# < IfModule mod_mime_magic.c>
# # MIMEMagicFile /usr/share/magic.mime
# MIMEMagicFile conf/magic
# < /IfModule>
# #
# # HostnameLookups: Log the names of clients or just their IP addresses
# # e.g., www.apache.org (on) or 204.62.129.132 (off).
# # The default is off because it'd be overall better for the net if people
# # had to knowingly turn this feature on, since enabling it means that
# # each client request will result in AT LEAST one lookup request to the
# # nameserver.
# #
# HostnameLookups Off
# #
# # EnableMMAP: Control whether memory-mapping is used to deliver
# # files (assuming that the underlying OS supports it).
# # The default is on; turn this off if you serve from NFS-mounted
# # filesystems. On some systems, turning it off (regardless of
# # filesystem) can improve performance; for details, please see
# # http://httpd.apache.org/docs/2.2/mod/core.html#enablemmap
# #
# #EnableMMAP off
# #
# # EnableSendfile: Control whether the sendfile kernel support is
# # used to deliver files (assuming that the OS supports it).
# # The default is on; turn this off if you serve from NFS-mounted
# # filesystems. Please see
# # http://httpd.apache.org/docs/2.2/mod/core.html#enablesendfile
# #
# #EnableSendfile off
# #
# # ErrorLog: The location of the error log file.
# # If you do not specify an ErrorLog directive within a < VirtualHost>
# # container, error messages relating to that virtual host will be
# # logged here. If you *do* define an error logfile for a < VirtualHost>
# # container, that host's errors will be logged there and not here.
# #
# ErrorLog logs/error_log
# #
# # LogLevel: Control the number of messages logged to the error_log.
# # Possible values include: debug, info, notice, warn, error, crit,
# # alert, emerg.
# #
# #LogLevel warn
# LogLevel debug
# #
# # The following directives define some format nicknames for use with
# # a CustomLog directive (see below).
# #
# LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
# LogFormat "%h %l %u %t \"%r\" %>s %b" common
# LogFormat "%{Referer}i -> %U" referer
# LogFormat "%{User-agent}i" agent
# # "combinedio" includes actual counts of actual bytes received (%I) and sent (%O); this
# # requires the mod_logio module to be loaded.
# #LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
# #
# # The location and format of the access logfile (Common Logfile Format).
# # If you do not define any access logfiles within a < VirtualHost>
# # container, they will be logged here. Contrariwise, if you *do*
# # define per-< VirtualHost> access logfiles, transactions will be
# # logged therein and *not* in this file.
# #
# #CustomLog logs/access_log common
# #
# # If you would like to have separate agent and referer logfiles, uncomment
# # the following directives.
# #
# #CustomLog logs/referer_log referer
# #CustomLog logs/agent_log agent
# #
# # For a single logfile with access, agent, and referer information
# # (Combined Logfile Format), use the following directive:
# #
# CustomLog logs/access_log combined
# #
# # Optionally add a line containing the server version and virtual host
# # name to server-generated pages (internal error documents, FTP directory
# # listings, mod_status and mod_info output etc., but not CGI generated
# # documents or custom error documents).
# # Set to "EMail" to also include a mailto: link to the ServerAdmin.
# # Set to one of: On | Off | EMail
# #
# ServerSignature On
# #
# # Aliases: Add here as many aliases as you need (with no limit). The format is
# # Alias fakename realname
# #
# # Note that if you include a trailing / on fakename then the server will
# # require it to be present in the URL. So "/icons" isn't aliased in this
# # example, only "/icons/". If the fakename is slash-terminated, then the
# # realname must also be slash terminated, and if the fakename omits the
# # trailing slash, the realname must also omit it.
# #
# # We include the /icons/ alias for FancyIndexed directory listings. If you
# # do not use FancyIndexing, you may comment this out.
# #
# Alias /icons/ "/var/www/icons/"
# < Directory "/var/www/icons">
# Options Indexes MultiViews FollowSymLinks
# AllowOverride None
# Order allow,deny
# Allow from all
# < /Directory>
# #
# # WebDAV module configuration section.
# #
# < IfModule mod_dav_fs.c>
# # Location of the WebDAV lock database.
# DAVLockDB /var/lib/dav/lockdb
# < /IfModule>
# #
# # ScriptAlias: This controls which directories contain server scripts.
# # ScriptAliases are essentially the same as Aliases, except that
# # documents in the realname directory are treated as applications and
# # run by the server when requested rather than as documents sent to the client.
# # The same rules about trailing "/" apply to ScriptAlias directives as to
# # Alias.
# #
# ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
# #
# # "/var/www/cgi-bin" should be changed to whatever your ScriptAliased
# # CGI directory exists, if you have that configured.
# #
# < Directory "/var/www/cgi-bin">
# AllowOverride None
# Options None
# Order allow,deny
# Allow from all
# < /Directory>
# #
# # Redirect allows you to tell clients about documents which used to exist in
# # your server's namespace, but do not anymore. This allows you to tell the
# # clients where to look for the relocated document.
# # Example:
# # Redirect permanent /foo http://www.example.com/bar
# #
# # Directives controlling the display of server-generated directory listings.
# #
# #
# # IndexOptions: Controls the appearance of server-generated directory
# # listings.
# #
# IndexOptions FancyIndexing VersionSort NameWidth=* HTMLTable Charset=UTF-8
# #
# # AddIcon* directives tell the server which icon to show for different
# # files or filename extensions. These are only displayed for
# # FancyIndexed directories.
# #
# AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
# AddIconByType (TXT,/icons/text.gif) text/*
# AddIconByType (IMG,/icons/image2.gif) image/*
# AddIconByType (SND,/icons/sound2.gif) audio/*
# AddIconByType (VID,/icons/movie.gif) video/*
# AddIcon /icons/binary.gif .bin .exe
# AddIcon /icons/binhex.gif .hqx
# AddIcon /icons/tar.gif .tar
# AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
# AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
# AddIcon /icons/a.gif .ps .ai .eps
# AddIcon /icons/layout.gif .html .shtml .htm .pdf
# AddIcon /icons/text.gif .txt
# AddIcon /icons/c.gif .c
# AddIcon /icons/p.gif .pl .py
# AddIcon /icons/f.gif .for
# AddIcon /icons/dvi.gif .dvi
# AddIcon /icons/uuencoded.gif .uu
# AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
# AddIcon /icons/tex.gif .tex
# AddIcon /icons/bomb.gif core
# AddIcon /icons/back.gif ..
# AddIcon /icons/hand.right.gif README
# AddIcon /icons/folder.gif ^^DIRECTORY^^
# AddIcon /icons/blank.gif ^^BLANKICON^^
# #
# # DefaultIcon is which icon to show for files which do not have an icon
# # explicitly set.
# #
# DefaultIcon /icons/unknown.gif
# #
# # AddDescription allows you to place a short description after a file in
# # server-generated indexes. These are only displayed for FancyIndexed
# # directories.
# # Format: AddDescription "description" filename
# #
# #AddDescription "GZIP compressed document" .gz
# #AddDescription "tar archive" .tar
# #AddDescription "GZIP compressed tar archive" .tgz
# #
# # ReadmeName is the name of the README file the server will look for by
# # default, and append to directory listings.
# #
# # HeaderName is the name of a file which should be prepended to
# # directory indexes.
# ReadmeName README.html
# HeaderName HEADER.html
# #
# # IndexIgnore is a set of filenames which directory indexing should ignore
# # and not include in the listing. Shell-style wildcarding is permitted.
# #
# IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
# #
# # DefaultLanguage and AddLanguage allows you to specify the language of
# # a document. You can then use content negotiation to give a browser a
# # file in a language the user can understand.
# #
# # Specify a default language. This means that all data
# # going out without a specific language tag (see below) will
# # be marked with this one. You probably do NOT want to set
# # this unless you are sure it is correct for all cases.
# #
# # * It is generally better to not mark a page as
# # * being a certain language than marking it with the wrong
# # * language!
# #
# # DefaultLanguage nl
# #
# # Note 1: The suffix does not have to be the same as the language
# # keyword --- those with documents in Polish (whose net-standard
# # language code is pl) may wish to use "AddLanguage pl .po" to
# # avoid the ambiguity with the common suffix for perl scripts.
# #
# # Note 2: The example entries below illustrate that in some cases
# # the two character 'Language' abbreviation is not identical to
# # the two character 'Country' code for its country,
# # E.g. 'Danmark/dk' versus 'Danish/da'.
# #
# # Note 3: In the case of 'ltz' we violate the RFC by using a three char
# # specifier. There is 'work in progress' to fix this and get
# # the reference data for rfc1766 cleaned up.
# #
# # Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl)
# # English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de)
# # Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja)
# # Korean (ko) - Luxembourgeois* (ltz) - Norwegian Nynorsk (nn)
# # Norwegian (no) - Polish (pl) - Portugese (pt)
# # Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv)
# # Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW)
# #
# AddLanguage ca .ca
# AddLanguage cs .cz .cs
# AddLanguage da .dk
# AddLanguage de .de
# AddLanguage el .el
# AddLanguage en .en
# AddLanguage eo .eo
# AddLanguage es .es
# AddLanguage et .et
# AddLanguage fr .fr
# AddLanguage he .he
# AddLanguage hr .hr
# AddLanguage it .it
# AddLanguage ja .ja
# AddLanguage ko .ko
# AddLanguage ltz .ltz
# AddLanguage nl .nl
# AddLanguage nn .nn
# AddLanguage no .no
# AddLanguage pl .po
# AddLanguage pt .pt
# AddLanguage pt-BR .pt-br
# AddLanguage ru .ru
# AddLanguage sv .sv
# AddLanguage zh-CN .zh-cn
# AddLanguage zh-TW .zh-tw
# #
# # LanguagePriority allows you to give precedence to some languages
# # in case of a tie during content negotiation.
# #
# # Just list the languages in decreasing order of preference. We have
# # more or less alphabetized them here. You probably want to change this.
# #
# LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW
# #
# # ForceLanguagePriority allows you to serve a result page rather than
# # MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# # [in case no accepted languages matched the available variants]
# #
# ForceLanguagePriority Prefer Fallback
# #
# # Specify a default charset for all content served; this enables
# # interpretation of all content as UTF-8 by default. To use the
# # default browser choice (ISO-8859-1), or to allow the META tags
# # in HTML content to override this choice, comment out this
# # directive:
# #
# AddDefaultCharset UTF-8
# #
# # AddType allows you to add to or override the MIME configuration
# # file mime.types for specific file types.
# #
# #AddType application/x-tar .tgz
# #
# # AddEncoding allows you to have certain browsers uncompress
# # information on the fly. Note: Not all browsers support this.
# # Despite the name similarity, the following Add* directives have nothing
# # to do with the FancyIndexing customization directives above.
# #
# #AddEncoding x-compress .Z
# #AddEncoding x-gzip .gz .tgz
# # If the AddEncoding directives above are commented-out, then you
# # probably should define those extensions to indicate media types:
# #
# AddType application/x-compress .Z
# AddType application/x-gzip .gz .tgz
# #
# # MIME-types for downloading Certificates and CRLs
# #
# AddType application/x-x509-ca-cert .crt
# AddType application/x-pkcs7-crl .crl
# #
# # AddHandler allows you to map certain file extensions to "handlers":
# # actions unrelated to filetype. These can be either built into the server
# # or added with the Action directive (see below)
# #
# # To use CGI scripts outside of ScriptAliased directories:
# # (You will also need to add "ExecCGI" to the "Options" directive.)
# #
# #AddHandler cgi-script .cgi
# #
# # For files that include their own HTTP headers:
# #
# #AddHandler send-as-is asis
# #
# # For type maps (negotiated resources):
# # (This is enabled by default to allow the Apache "It Worked" page
# # to be distributed in multiple languages.)
# #
# AddHandler type-map var
# #
# # Filters allow you to process content before it is sent to the client.
# #
# # To parse .shtml files for server-side includes (SSI):
# # (You will also need to add "Includes" to the "Options" directive.)
# #
# AddType text/html .shtml
# AddOutputFilter INCLUDES .shtml
# #
# # Action lets you define media types that will execute a script whenever
# # a matching file is called. This eliminates the need for repeated URL
# # pathnames for oft-used CGI file processors.
# # Format: Action media/type /cgi-script/location
# # Format: Action handler-name /cgi-script/location
# #
# #
# # Customizable error responses come in three flavors:
# # 1) plain text 2) local redirects 3) external redirects
# #
# # Some examples:
# #ErrorDocument 500 "The server made a boo boo."
# #ErrorDocument 404 /missing.html
# #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
# #ErrorDocument 402 http://www.example.com/subscription_info.html
# #
# #
# # Putting this all together, we can internationalize error responses.
# #
# # We use Alias to redirect any /error/HTTP_< error>.html.var response to
# # our collection of by-error message multi-language collections. We use
# # includes to substitute the appropriate text.
# #
# # You can modify the messages' appearance without changing any of the
# # default HTTP_< error>.html.var files by adding the line:
# #
# # Alias /error/include/ "/your/include/path/"
# #
# # which allows you to create your own set of files by starting with the
# # /var/www/error/include/ files and
# # copying them to /your/include/path/, even on a per-VirtualHost basis.
# #
# Alias /error/ "/var/www/error/"
# < IfModule mod_negotiation.c>
# < IfModule mod_include.c>
# < Directory "/var/www/error">
# AllowOverride None
# Options IncludesNoExec
# AddOutputFilter Includes html
# AddHandler type-map var
# Order allow,deny
# Allow from all
# LanguagePriority en es de fr
# ForceLanguagePriority Prefer Fallback
# < /Directory>
# # ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
# # ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
# # ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
# # ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
# # ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
# # ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
# # ErrorDocument 410 /error/HTTP_GONE.html.var
# # ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
# # ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
# # ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
# # ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
# # ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
# # ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
# # ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
# # ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
# # ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
# # ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var
# < /IfModule>
# < /IfModule>
# #
# # The following directives modify normal HTTP response behavior to
# # handle known problems with browser implementations.
# #
# BrowserMatch "Mozilla/2" nokeepalive
# BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
# BrowserMatch "RealPlayer 4\.0" force-response-1.0
# BrowserMatch "Java/1\.0" force-response-1.0
# BrowserMatch "JDK/1\.0" force-response-1.0
# #
# # The following directive disables redirects on non-GET requests for
# # a directory that does not include the trailing slash. This fixes a
# # problem with Microsoft WebFolders which does not appropriately handle
# # redirects for folders with DAV methods.
# # Same deal with Apple's DAV filesystem and Gnome VFS support for DAV.
# #
# BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
# BrowserMatch "MS FrontPage" redirect-carefully
# BrowserMatch "^WebDrive" redirect-carefully
# BrowserMatch "^WebDAVFS/1.[0123]" redirect-carefully
# BrowserMatch "^gnome-vfs/1.0" redirect-carefully
# BrowserMatch "^XML Spy" redirect-carefully
# BrowserMatch "^Dreamweaver-WebDAV-SCM1" redirect-carefully
# #
# # Allow server status reports generated by mod_status,
# # with the URL of http://servername/server-status
# # Change the ".example.com" to match your domain to enable.
# #
# #< Location /server-status>
# # SetHandler server-status
# # Order deny,allow
# # Deny from all
# # Allow from .example.com
# #< /Location>
# #
# # Allow remote server configuration reports, with the URL of
# # http://servername/server-info (requires that mod_info.c be loaded).
# # Change the ".example.com" to match your domain to enable.
# #
# #< Location /server-info>
# # SetHandler server-info
# # Order deny,allow
# # Deny from all
# # Allow from .example.com
# #< /Location>
# #
# # Proxy Server directives. Uncomment the following lines to
# # enable the proxy server:
# #
# #< IfModule mod_proxy.c>
# #ProxyRequests On
# #
# #< Proxy *>
# # Order deny,allow
# # Deny from all
# # Allow from .example.com
# #< /Proxy>
# #
# # Enable/disable the handling of HTTP/1.1 "Via:" headers.
# # ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# # Set to one of: Off | On | Full | Block
# #
# #ProxyVia On
# #
# # To enable a cache of proxied content, uncomment the following lines.
# # See http://httpd.apache.org/docs/2.2/mod/mod_cache.html for more details.
# #
# #< IfModule mod_disk_cache.c>
# # CacheEnable disk /
# # CacheRoot "/var/cache/mod_proxy"
# #< /IfModule>
# #
# #< /IfModule>
# # End of proxy directives.
# ### Section 3: Virtual Hosts
# #
# # VirtualHost: If you want to maintain multiple domains/hostnames on your
# # machine you can setup VirtualHost containers for them. Most configurations
# # use only name-based virtual hosts so the server doesn't need to worry about
# # IP addresses. This is indicated by the asterisks in the directives below.
# #
# # Please see the documentation at
# # < URL:http://httpd.apache.org/docs/2.2/vhosts/>
# # for further details before you try to setup virtual hosts.
# #
# # You may use the command line option '-S' to verify your virtual host
# # configuration.
# #
# # Use name-based virtual hosting.
# #
# #NameVirtualHost *:80
# #
# # NOTE: NameVirtualHost cannot be used without a port specifier
# # (e.g. :80) if mod_ssl is being used, due to the nature of the
# # SSL protocol.
# #
# #
# # VirtualHost example:
# # Almost any Apache directive may go into a VirtualHost container.
# # The first VirtualHost section is used for requests without a known
# # server name.
# #
# #< VirtualHost *:80>
# # ServerAdmin webmaster@dummy-host.example.com
# # DocumentRoot /www/docs/dummy-host.example.com
# # ServerName dummy-host.example.com
# # ErrorLog logs/dummy-host.example.com-error_log
# # CustomLog logs/dummy-host.example.com-access_log common
# #< /VirtualHost>
# # Include websites/testsite
# < VirtualHost *:443>
# DocumentRoot /var/www/testsite
# ServerName http://sophie.cs.fsu.edu
# SSLProtocol all
# SSLEngine on
# SSLCertificateFile /etc/httpd/conf/ssl/sophie.cs.fsu.edu.crt
# SSLCertificateKeyFile /etc/httpd/conf/ssl/sophie.cs.fsu.edu.key
# SSLVerifyClient none
# SSLProxyEngine off
# < IfModule mime.c>
# AddType application/x-x509-ca-cert .crt
# AddType application/x-pkcs7-crl .crl
# < /IfModule>
# < /VirtualHost>
nginx
Fortunately, you don't have to use Apache. Apache is now a monster-sized server that
provides good but not great service.
nginx on the other hand is fast. It was designed from the beginning to handle the
C10k problem. To accomplish this, it uses an event-driven model
rather than threading.
Configuring nginx
#######################################################################
#
# This is the main Nginx configuration file.
#
# More information about the configuration options is available on
# * the English wiki - http://wiki.nginx.org/Main
# * the Russian documentation - http://sysoev.ru/nginx/
#
#######################################################################
#----------------------------------------------------------------------
# Main Module - directives that cover basic functionality
#
# http://wiki.nginx.org/NginxHttpMainModule
#
#----------------------------------------------------------------------
user nginx;
worker_processes 1;
error_log /var/log/nginx/error.log;
pid /var/run/nginx.pid;
#----------------------------------------------------------------------
# Events Module
#
# http://wiki.nginx.org/NginxHttpEventsModule
#
#----------------------------------------------------------------------
events {
worker_connections 1024;
}
#----------------------------------------------------------------------
# HTTP Core Module
#
# http://wiki.nginx.org/NginxHttpCoreModule
#
#----------------------------------------------------------------------
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
sendfile on;
#tcp_nopush on;
keepalive_timeout 65;
#gzip on;
# Load config files from the /etc/nginx/conf.d directory
include /etc/nginx/conf.d/*.conf;
#
# The default server
#
server {
listen 80;
server_name _;
#charset koi8-r;
access_log /var/logs/nginx/host.access.log main;
location / {
root /usr/share/nginx/html;
index index.html index.htm;
}
error_page 404 /404.html;
location = /404.html {
root /usr/share/nginx/html;
}
# redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html;
}
# proxy the PHP scripts to Apache listening on 127.0.0.1:80
#
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#}
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# root html;
# fastcgi_pass 127.0.0.1:9000;
# fastcgi_index index.php;
# fastcgi_param SCRIPT_FILENAME /scripts$fastcgi_script_name;
# include fastcgi_params;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
}
}
Generally, you would want to put each virtual server in its own file, something like this:
#
# A virtual host using mix of IP-, name-, and port-based configuration
#
server {
server_name www.cs.fsu.edu alias cs.fsu.edu;
location / {
root /www/var/www.cs.fsu.edu/html;
index index.html index.htm;
access_log /var/logs/nginx/www.cs.fsu.edu.access.log main gzip;
error_log /var/logs/nginx/www.cs.fsu.edu.error.log crit;
}
}
Setting up SSL is pretty pleasant, also:
#
# HTTPS server configuration
#
server {
listen 443;
server_name www.cs.fsu.edu alias cs.fsu.edu;
ssl on;
ssl_certificate /etc/pki/public/cert.pem;
ssl_certificate_key /etc/pki/private/cert.key;
ssl_session_timeout 5m;
ssl_protocols SSLv2 SSLv3 TLSv1;
ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
ssl_prefer_server_ciphers on;
location / {
root /var/www/www.cs.fsu.edu/html;
index index.html index.htm;
access_log /var/logs/nginx/www.cs.fsu.edu.s.access.log main gzip;
error_log /var/logs/nginx/www.cs.fsu.edu.s.error.log crit;
}
}
