Free Essay

It302

In:

Submitted By jrindens
Words 4666
Pages 19
#
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See for detailed information.
# In particular, see
#
# 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 Prod

#
# 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 );
# 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. Note the PIDFILE variable in
# /etc/sysconfig/httpd must be set appropriately if this location is
# changed.
#
PidFile run/httpd.pid

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 60

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# 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 5

##
## 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

StartServers 8
MinSpareServers 5
MaxSpareServers 20
ServerLimit 256
MaxClients 256
MaxRequestsPerChild 4000

# 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

StartServers 4
MaxClients 300
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
MaxRequestsPerChild 0

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#
#Listen 10.0.0.1:80
Listen 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 substitute_module modules/mod_substitute.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_ajp_module modules/mod_proxy_ajp.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
LoadModule version_module modules/mod_version.so

#
# The following modules are not loaded by default:
#
#LoadModule asis_module modules/mod_asis.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule cgid_module modules/mod_cgid.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule unique_id_module modules/mod_unique_id.so
#

#
# Load config files from the config directory "/etc/httpd/conf.d".
#
Include conf.d/*.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
# definition. These values also provide defaults for
# any containers you may define later in the file.
#
# All of these directives may appear inside 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@RFP.com

#
# 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.RFP.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.
#

Options FollowSymLinks ExecCGI AllowOverride ALL

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

# # 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 ExecCGI

# # 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 ALL

# # Controls who can get stuff from this server. # Order allow,deny Allow from all

#
# 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
#

# # 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

#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
#
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
#
# Order allow,deny
# Allow from all
#
#
# Order deny,allow
# Deny from all
#
#

#
# 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.cgi index.php

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

Order allow,deny Deny from all Satisfy All

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

# MIMEMagicFile /usr/share/magic.mime MIMEMagicFile conf/magic

#
# 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
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a
# 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

#
# 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
# container, they will be logged here. Contrariwise, if you *do*
# define per- 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 Off

#
# 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/"

Options Indexes MultiViews FollowSymLinks AllowOverride None Order allow,deny Allow from all

#
# WebDAV module configuration section.
#

# Location of the WebDAV lock database. DAVLockDB /var/lib/dav/lockdb

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

AllowOverride None Options None Order allow,deny Allow from all

#
# 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 .pl

#
# 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_.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_.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/"

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

# 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

#
# 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.
#
#
# SetHandler server-status
# Order deny,allow
# Deny from all
# Allow from .example.com
#

#
# 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.
#
#
# SetHandler server-info
# Order deny,allow
# Deny from all
# Allow from .example.com
#

#
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#
#
#ProxyRequests On
#
#
# Order deny,allow
# Deny from all
# Allow from .example.com
#

#
# 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.
#
#
# CacheEnable disk /
# CacheRoot "/var/cache/mod_proxy"
#
#

#
# 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
#
# 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.
#
#
# ServerAdmin root@server2.RFP.com
# DocumentRoot /www/docs/server2.RFP.com
# ServerName www.RFP.com

#

Similar Documents

Free Essay

It302

...There are some goods in the economy that are required by the public but are not profitable for the businesses. Businesses do not like to invest where profit is not there. Such goods are provided by the government to the people and are known as public goods. Public Goods are freely available to the public and generally have two major characteristics: The good is non rival in consumption i.e. your consumption does not affect my consumption neither it decreases my consumption nor it increases my consumption The good is non excludable i.e. you cannot refrain a person from using that good despite of whether he is paying or not paying for the good. Cup of coffee at coffee shop is there property and you will have to pay for buying it. Hence, it is rival as well as excludable. It is a private good. City fire protection is provided by the government and it is non rival and non excludable. Provided free of cost hence, it is a public good. Polar Bears are a common resource a natural resource or wildlife you can say. Clean Air is non rival and non excludable but not provided by government. Though government can take steps to ensure that air is not polluted by industries and firms. 1. Do corporate managers always act in the best interest of shareholders? • The claim that managers can ignore the interests of shareholders is deduced from the fact that ownership in large corporations is widely dispersed. As a consequence, it is often claimed that individual shareholders cannot control...

Words: 478 - Pages: 2

Free Essay

It302-Unit6B

...IT302-Unit6B- Kaplan University As a consumer when we use a kiosk for a transaction, we expect it to provide us with a level of service or actions at least on a par with a proficient sales person or staff. If this is what we expect when we use a kiosk or similar device, then any design or implementation we are involved in must be done to the same or a higher level. After an introductory exposure to the requirements needed to meet the expectations of those who will be using the kiosk, our efforts need to be directed to create a device that meets or exceeds those expectations. In order to meet these expectations our first step is to thoroughly understand what is anticipated and needed to meet the expectations of potential users. In order to accomplish this we will need to conduct market research to truly find out what is expected by potential customers. Our design will need to attract potential customers and create an interest in products that are promoted or displayed. The clients’ initial impression will be an important part of this task. If the kiosk fails to attract the customers and impress them, it will simply become a device that takes up room. In order to maximize the any benefits that we may receive from the kiosk, we need to select the proper location and provide proper exposure for the kiosk. No matter how well designed it is or the bells and whistles it may have, if it’s in a poor location and lacks exposure...

Words: 677 - Pages: 3

Free Essay

It302-Unit4

...IT302-Unit4- Kaplan University Part 1: Dashboard Design. For the dashboard that I anticipated is required to meet the needs of the task that I discussed in Unit 3, I believe that the best approaches are either a Semantic Network or the use of Scenarios, Flowcharts and Cognitive walkthroughs, and more specifically Scenarios. Although this may be the most productive approach, it is likely that in the process of creating the dashboard that parts of a number of the conceptual designs could contribute to the finished product. While the Semantic Network is comprised of elements that would be useful and productive, particularly by providing ease in exploring the problem space and graphical views, it does not offer us all the information that would be constructive. To accomplish that, I believe the use of Scenarios, Flowcharts and Cognitive walkthroughs would provide us with the most useful means to develop a dashboard adequate to provide the functionality we are seeking. Of these, the use of Scenarios would provide the easiest means to develop a dashboard with the desired functionality initially along with the ability to modify easily as required to accomplish what is needed. By creating scenarios and including them in the early development of the dashboard we will provide ourselves with a means to develop a versatile form that can be easily amended as needed to provide a finished console that provides the full functionality that...

Words: 590 - Pages: 3

Premium Essay

It302-Unit5

...IT302-Unit5- Kaplan University Part 1: Design choice and wireframe. The range of purposes that kiosks serve is broad and varied. From providing information or services to the purchase of an extensive array of goods a kiosk can be and frequently is used to meet the desires and needs of the general public and consumers. In recent years there has been a substantial and steady increase in the frequency that we see or use some form of stand alone kiosk. The wireframe that I considered is more general in nature. This was done to provide flexibility in the design that can be easily used across a broad range of services with minimal modification. It also accommodates easy adjustment for use by disabled individuals. [pic] Part 2: Report of design principles. The final goal in designing a kiosk is to generate a product that will meet the needs of the business or organization that is using it to provide goods or services to its potential clientele. The purpose is to produce a product that is highly intuitive, and also provides clear and concise instructions on the proper use of the kiosk in general and specific features for those patrons that need assistance. The final design is influenced by several factors; • The service it provides and its ultimate function. • Ease of use and convenience for all users including handicapped. • The surroundings it needs to blend with. • Ease...

Words: 807 - Pages: 4

Free Essay

It302-Unit6

...IT302-Unit6A- Kaplan University Part1 – Introduction. The approach I used in unit 5 was a generic design which is flexible in nature with a basic layout planned so it can be easily molded, or modified to fulfill a variety of needs or applications. The wireframe associated with the design is shown without a supporting structure. The associated structure will be dictated by its application and placement. Part 2. WIMP. WIMP is an established approach that has become commonplace in its usage with and basic functionality on kiosks. The term WIMP stands for windows, icons, menus and pointers which are the primary objects used in the presentation of data to the customer or client and the means to communicate with the system. The term was coined by Merzouga Wilberts in 1980 that was part of the working group at Xerox Parc that ultimately developed the Graphical User Interface under the guidance of Allen Kay (Charlotte). Although still used, the term “WIMP” is slowly being overtaken by newer approaches and standards. As stated by Allen Kay, "We've taken the WIMP interface as far as it can go," he added, referring to the Windows-icon-mouse-pull-down menu” (Laurie, 1995). The first and most possibly the largest single item that the user sees is the monitor. Not only is it the most visible item we see whether the kiosk unit is handheld or free standing, it is the device that we depend on most for our visual interaction with...

Words: 1787 - Pages: 8

Premium Essay

Unit 8 It302

...Ariel Ruiz It302 Assignment 8.1 1. Which company originally created NIS under the name Yellow Pages, and then later changed the name since it was owned by “another corporation”? NIS was developed by Sun Microsystems. 2. What configuration file is used to tell Linux which system (NIS, DNS, files, etc.) to use for name resolution, authentication, etc.? The /etc/ncsd.conf configuration file is used to tell Linux which system to use for name resolution, authentication, etc. 3. The file format for an NIS database file is called a dbm. 4. Which Linux file generates two maps in NIS? The /etc/passwd file generates two maps: one indexed by username, the other indexed by UID. These maps are named passwd.byname and passwd.byuid. 5. What utility is used to display raw information from an NIS server? The ypmatch utility or ypcat utility is used to display raw information from an NIS server. 6. Which is the name of the init script for LDAP: ldap or slapd The name of the init script for LDAP is slapd. 7. What is the name for the root, or top level, entry in an LDAP directory? DSE is the root, or top level entry in an LDAP directory. 8. Expand and explain the following acronyms: a. CN = Common Name = is the attribute value used in the Relative Distinguished Name (RDN) b. DC = Domain Component = my-domain c. DN = Distinguished Name = uniquely identifies each entry in an LDAP directory. d. DSE = DSA Specific Entry = is...

Words: 319 - Pages: 2

Premium Essay

It302 Research #1

...IT302 Linux Administration Research #1 I researched three Linux security technologies which are, SELinux, chroot jail and iptables. As you read into this research you will see that they are split up into their own catagories so that it is easy to read information on whichever topic you would like. SELinux As part of its Information Assurance mission, the National Security Agency has long been involved with the computer security research community in investigating a wide range of computer security topics including operating system security. Recognizing the critical role of operating system security mechanisms in supporting security at higher levels, researchers from NSA's National Information Assurance Research Laboratory have been investigating an architecture that can provide the necessary security functionality in a manner that can meet the security needs of a wide range of computing environments. End systems must be able to enforce the separation of information based on confidentiality and integrity requirements to provide system security. Operating system security mechanisms are the foundation for ensuring such separation. Unfortunately, existing mainstream operating systems lack the critical security feature required for enforcing separation: mandatory access control. As a consequence, application security mechanisms are vulnerable to tampering and bypass, and malicious or flawed applications can easily cause failures in system security. The results of several...

Words: 1295 - Pages: 6

Premium Essay

It302 Unit 5

...UNIT 5 PROJECT Human Computer Interaction IT302 Professor Tamara Fudge Charlissia D. Fields Kaplan University Part I. Design Choice and Wireframe: Interface design refers to the element of website/ appliance/ device design that is aimed at creating a favorable environment for interaction between the user and the system and/or the owners of the website/ appliance/ design. In this paper we take a closer look at the principles being utilized to ensure that various aspects of interface have been taken into account at the design stage (Jenifer, 2010). A case study for an online customer care desk for ABC college. Part II. Report of Design Principles: 1. Comprehensibility and Learnability To ensure that the interface in comprehensible and easy to learn, the program shall first of all use language that is simple and which is commonly used in the interface design for education sector. Where a salient feature is used, the design shall ensure that it is positioned strategically in a way the user may derive its usage from its position (Kevin, & John, 2011). 2. Effectiveness/Usefulness Utility The utility/ usefulness of the interface are defined by the ability of the site to help as many clients as possible. Also, the ability for the user to use minimum time on the site is essential. To ensure this is possible, the website is created using very high...

Words: 855 - Pages: 4

Premium Essay

It302-Unit9-.Doc

...IT302-Unit9- Kaplan University Part1: Introduction. The approach I used in unit 5 was a generic design which is flexible in nature with a basic layout planned so it can be easily molded, or modified to fulfill a variety of needs or applications. The wireframe associated with the design is shown without a supporting structure. The associated structure will be dictated by its application and placement. Part 2: Haptic Specifications. Although possibly not needed or beneficial, multiple responses in affirming an action by the user are not particularly undesirable. In many cases the confirmation of an action is not only desirable, but may be mandatory for the benefit of the operator, particularly in the case of a client who has a hearing or vision problem. Feedback from the kiosk to confirm an operation may not only meet the ADA requirements, it may be reassuring to some users who may not need confirmation of an action due to physical reasons, but are simply reassured by having an indication that their actions ware correct and completed. Although the operating system of the kiosk possibly will be capable of additional tasks such as signifying that a keystroke was performed correctly, the use of these features may not be wanted by all users. It would be easy, and probably desirable, to design the system so features can be utilized or not as the user wishes. Through the use of messages, sounds or lighting a key or...

Words: 1152 - Pages: 5

Free Essay

It302 Unit 7

...TEXT AND THE USER INTERFACE IT302 Human Computer Interaction Unit 7 Assignment Kaplan University Part 1: Introduction The interface that was chosen in past assignments was the smartphone. The user can determine how the smartphone is set up, but in general there are some basic designs that every user needs in order to operate their own personal smartphone. These designs consist of icons that a user has memorized. Icons such as settings, home, phone and text are very common on smartphones and are used to help the user personalize their device. Part 2: Commentary Text Commentary text makes system states or system functionality visible (Heim 2008). Text should be readable, in that it is easy for the user of the interface to understand and read. The line spacing is very important when making the text on an interface readable. There are other aspects of the interface that make it readable as well such as: line length, formatting, the width of the margins and the scroll bar (scrolling). The interface should also use words that are common and easy for the user to understand. This just means that the designer of the interface should not use words that are not in most users’ everyday language. An example of this type of word is interface or dialog box. If the designer uses words that have no words that are like them in real life then the users of the interface will not try to make them have a different meaning than that which is intended. The text should...

Words: 1115 - Pages: 5

Free Essay

It302-Unit8-Rapier-John.Doc

...IT302-Unit8- Part1: Introduction. The approach I used in unit 5 was a generic design which is flexible in nature with a basic layout planned so it can be easily molded, or modified to fulfill a variety of needs or applications. The wireframe associated with the design is shown without a supporting structure. The associated structure will be dictated by its application and placement. Part 2: Non-Speech Sounds. Non-speech sounds are a part of our life that we have been exposed to from our youngest days until the present. Over time we learned to understand what they represented and understand more as we were exposed to them. Many key us to an action or event that occurred or is occurring around us even if we can’t or don’t see what sound is in response to. Our ability to interpret non-speech sounds and its connection to vision is a trait that can be effectively used in designing a kiosk. Sound can be employed as a vehicle to attract us to a kiosk, or draw attention to a product or service. While the sound may not directly provide information, it can used to create an interest in a product or service and draw us to it. A certain amount of care is needed in the selection of the sound that is being used to attract customers. Its purpose is to create interest and to support it, but not to take control of the presentation of the product. The same formula can be applied when we are using a kiosk. As well as sounds...

Words: 917 - Pages: 4

Free Essay

It302-Unit7-Rapier-John.Doc

...IT302-Unit7- Kaplan University Part1 – Introduction. The approach I used in unit 5 was a generic design which is flexible in nature with a basic layout planned so it can be easily molded, or modified to fulfill a variety of needs or applications. The wireframe associated with the design is shown without a supporting structure. The associated structure will be dictated by its application and placement. Part 2: Commentary Text. Commentary text should be selectable using different means. The most obvious means of selection is by the use of a designated help button. When touched this will display a help screen to provide a means for the customer to seek assistance. Additionally, this should also be accomplished by clicking the mouse curser on an item or text that information is desired on. All of these means should result in the same basic effect. The commentary text used in the presenting the product to potential customers has the potential of using a variety of text styles and sizes. Also in some cases color will be added to the text for emphasis or used to highlight items or attract the consumers’ interest. When initially presenting an item the text that is to be used will be designed in a manner to catch potential customers’ attention. This can be accomplished through the use of text styles that catch the eye, such as a change in size or creating an emphasis through the use of colors. Using a text style...

Words: 1034 - Pages: 5

Free Essay

It302 Activity 1

...Chapter 2 Installation Overview 1. A Net Boot CD is a way to install a new system from a hard disk or over a network. 2. Three considerations for planning an installation are; a. SELinux improves system security by implementing mandatory access control policies in the Fedora kernel b. Install a Graphical desktop environment (GUI) such as GNOME and/or KDE. c. Install additional software and services packages to fit the need of the user. 3. By default Fedora divides the disk into three partitions, including ‘/boot’ and Logical Volume Manager (LVM). 4. Manual partitioning the hard disk has its advantages, such as being able to isolate a filesystem for security or backup needs. 5. The / (root) partition is the main filesystem on the hard disk. Any new created directories will become part of the root filesystem unless a filesystem is created. 6. The swap partition is where Linux temporarily stores programs and data when it does not have enough RAM to hold all the information it is processing. 7. The /boot partition holds the hernel and other data the system needs when it boots. In order for the /boot partition to work properly it must be one of the first partitions on the disk. 8. The /var (variable) partition holds the bulk of system logs, package information, and accounting data. The /var/log partition is commonly used in a separate partition to isolate system logs from other files in the /var directory. 9. The /home partition is...

Words: 831 - Pages: 4

Free Essay

It302 Final Project

...CH 22 1. Sharing, remote storage, reduce the work load of administrator. 2. # mount bravo:/home /bravo. Home # mount 192.168.1.1:/home /bravo.home # umount /home 3. The showmount command can be used to display a list of directory hierarchies that a server is exporting. 4. $ mount | grep nfs 5. It contains information about major file systems in the system. And it is located in the /etc directory. 6. /opt *.example.com(ro,sync) 7. NFS attribute caching can cause inconsistencies when large numbers of client nodes are asked to access files that have been updated recently and the attribute caching data on the client has not expired. Disabling attribute caching eliminates the problem but may degrade performance for frequent file operations requiring file attribute data. 8. The root_squash option maps root to nfsnobody; all_squash maps all users to nfsnobody. 9. The option requires that the requests originate on an internet port less than 1024. 10. Because it has no disk space, a diskless workstation has no swap space. The only choice is to use NFS. If it did not use NFS for swap space, the workstation would be limited by the amount of its physical memory. 11. Because it resides on the lan and file data and user id values appear unencrypted. 12. The nosuid option forces setuid executable in the mounted directory hierarchy to run with regular permissions on the local system. CH 23 1. smdb, nmbd 2. Set the username map parameter...

Words: 806 - Pages: 4

Free Essay

It302 Reserch 1

...There are many ways to have internet access these days. Coffee shops, libraries, airports and even public buses have free wireless access. With all these free accesses to the World Wide Web, there is also many potential ways for hackers to potentially get your personal information and use it for their gain. There are many ways to combat this situation by using several security measures with Linux programming, which the majority of the software is free. Some of those security technologies are SELinux, TCP Wrappers, IPtables and Chroot Jail to name a few. In basic Linux security, Discretionary Access Control is based practically by users and groups. The process is run by a user and then has access to anything other users has access to, making it not so secure. The U.S. National Security Agency (NSA) developed the SELinux (Security Enhanced Linux) to combat the lack of strong security. The SELinux implements Mandatory Access Control (MAC) in the Linux kernel which enforces policies that limits the user or a program of what they can do. It is designed to prevent process from reading and/or tampering of data and programs. MAC is an important tool for containing security threats made by user errors, hackers or software errors. It’s pretty hard to bypass the security measure since the kernel is checking the MAC rules right after checking the DAC rules on a constant basis. There are three states you can place SELinux to run in; Enforcing, Permissive and Disabled...

Words: 827 - Pages: 4