Access to apache config file?

I’ve asked DH support to see my Apache httpd.conf for sake of learning and they asked me specifically what I was interested about and they fowarded me only those setting (** Vserver: MaxClients to 70, MaxSpareServers to 17, MinSpareServers to 3, StartServers to 3).

Would be viewing the whole file some sort of trade secret?

Is there a way for me to access it directly?

Use promo code US97OFF to get maximum discounts!
Use o código de promoção US97OFF para descontos de até US97!

The config file has all the virtual hosts listed, plus who knows what. It’s best to stop people from nosing around shared server config settings.

If you’re on a Mac, you already have an Apache server installed. If you’re on Windows, you can always partition your drive and install Linux.


Unless you were running on a dedicated server, there’s no reason for you to view the apache config file on DH. As sdayman suggested, if you want to see an apache config file, just download and install/setup apache yourself either in Windows or in Linux. As support suggested, you can always ask to see certain values if they concern you - but you cannot ask to have them changed, as that would affect everyone else using that instance of Apache as well.

Why do you need to see DH’s apache config file anyways?

Chips N Cheese - Custom PHP installs and the like!

Even though apache snobs hate it, .htaccess files can accomplish a lot of the same things a server config can. Mostly the capabilities of .htaccess are undocumented, so looking in the source code of the apache server (modules, libs, etc.) is really my favorite way to find new ideas.

Of course another recommended way to learn is to install an apache server on your own computer… any BSD/linux flavor is easy to install on, and if you get some experience administering multiple apache installs and everything that goes with it (suexex, virtualhosts, etc.) then you’ll be able to guess the contents of a httpd.conf with minimal excitement. The DreamHost admins are pretty hardcore talented, so maybe don’t shoot for the moon.


Based upon the NCSA server configuration files originally by Rob McCool.

This is the main Apache server configuration file. It contains the

configuration directives that give the server its instructions.

See URL: for detailed information about

the directives.

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 “log/foo.log”

with ServerRoot set to “/usr/local/dh/apache2/template” will be interpreted by the

server as “/usr/local/dh/apache2/template/log/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.

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:;

you will save yourself a lot of trouble.

Do NOT add a slash at the end of the directory path.

ServerRoot “/usr/local/dh/apache2/template”

The accept serialization lock file MUST BE STORED ON A LOCAL DISK.

<IfModule !mpm_winnt.c>
<IfModule !mpm_netware.c>
#LockFile log/accept.lock

ScoreBoardFile: File used to store internal server process information.

If unspecified (the default), the scoreboard will be stored in an

anonymous shared memory segment, and will be unavailable to third-party


If specified, ensure that no two invocations of Apache share the same

scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.

<IfModule !mpm_netware.c>
<IfModule !perchild.c>
#ScoreBoardFile log/apache_runtime_status

PidFile: The file in which the server should record its process

identification number when it starts.

<IfModule !mpm_netware.c>
PidFile var/run/

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

Timeout 300

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

MaxClients: maximum number of server processes allowed to start

MaxRequestsPerChild: maximum number of requests a server process serves

StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0

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 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0

perchild MPM

NumServers: constant number of server processes

StartThreads: initial number of worker threads in each server process

MinSpareThreads: minimum number of worker threads which are kept spare

MaxSpareThreads: maximum number of worker threads which are kept spare

MaxThreadsPerChild: maximum number of worker threads in each server process

MaxRequestsPerChild: maximum number of connections per server process

NumServers 5 StartThreads 5 MinSpareThreads 5 MaxSpareThreads 10 MaxThreadsPerChild 20 MaxRequestsPerChild 0


ThreadsPerChild: constant number of worker threads in the server process

MaxRequestsPerChild: maximum number of requests a server process serves

ThreadsPerChild 250 MaxRequestsPerChild 0


StartThreads: how many threads do we initially spawn?

MaxClients: max number of threads we can have (1 thread == 1 client)

MaxRequestsPerThread: maximum number of requests each thread will process

StartThreads 10 MaxClients 50 MaxRequestsPerThread 10000

NetWare MPM

ThreadStackSize: Stack size allocated for each worker thread

StartThreads: Number of worker threads launched at server startup

MinSpareThreads: Minimum number of idle threads, to handle request spikes

MaxSpareThreads: Maximum number of idle threads

MaxThreads: Maximum number of worker threads alive at the same time

MaxRequestsPerChild: Maximum number of requests a thread serves. It is

recommended that the default value of 0 be set for this

directive on NetWare. This will allow the thread to

continue to service requests indefinitely.

ThreadStackSize 65536 StartThreads 250 MinSpareThreads 25 MaxSpareThreads 250 MaxThreads 1000 MaxRequestsPerChild 0 MaxMemFree 100


StartServers: Number of server processes to maintain

MinSpareThreads: Minimum number of idle threads per process,

to handle request spikes

MaxSpareThreads: Maximum number of idle threads per process

MaxRequestsPerChild: Maximum number of connections per server process

StartServers 2 MinSpareThreads 5 MaxSpareThreads 10 MaxRequestsPerChild 0

Listen: Allows you to bind Apache to specific IP addresses and/or

ports, instead of the default. See also the


Change this to Listen on specific IP addresses as shown below to

prevent Apache from glomming onto all bound IP addresses (


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.


LoadModule foo_module modules/

LoadModule access_module lib/modules/
LoadModule auth_module lib/modules/
LoadModule auth_anon_module lib/modules/
LoadModule auth_dbm_module lib/modules/
LoadModule auth_digest_module lib/modules/
LoadModule cache_module lib/modules/
LoadModule ext_filter_module lib/modules/
LoadModule include_module lib/modules/
LoadModule deflate_module lib/modules/
LoadModule log_config_module lib/modules/
LoadModule log_forensic_module lib/modules/
LoadModule logio_module lib/modules/
LoadModule env_module lib/modules/
LoadModule mime_magic_module lib/modules/
LoadModule cern_meta_module lib/modules/
LoadModule expires_module lib/modules/
LoadModule headers_module lib/modules/
LoadModule usertrack_module lib/modules/
LoadModule unique_id_module lib/modules/
LoadModule setenvif_module lib/modules/

LoadModule ssl_module lib/modules/

LoadModule mime_module lib/modules/
LoadModule dav_module lib/modules/
LoadModule status_module lib/modules/
LoadModule autoindex_module lib/modules/
LoadModule asis_module lib/modules/
LoadModule info_module lib/modules/
LoadModule suexec_module lib/modules/
LoadModule cgi_module lib/modules/
LoadModule dav_fs_module lib/modules/
LoadModule vhost_alias_module lib/modules/
LoadModule negotiation_module lib/modules/
LoadModule dir_module lib/modules/
LoadModule imap_module lib/modules/
LoadModule actions_module lib/modules/
LoadModule speling_module lib/modules/
LoadModule userdir_module lib/modules/
LoadModule alias_module lib/modules/
LoadModule rewrite_module lib/modules/

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

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.

<IfModule !mpm_winnt.c>
<IfModule !mpm_netware.c>

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 nobody
Group #-1

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.


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.


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 “/usr/local/dh/apache2/template/htdocs”

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


Options FollowSymLinks AllowOverride None

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


This should be changed to whatever you set DocumentRoot to.

<Directory “/usr/local/dh/apache2/template/htdocs”>

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

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

UserDir: The name of the directory that is appended onto a user’s home

directory if a ~user request is received.

UserDir public_html

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 Indexes

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.html.var

AccessFileName: The name of the file to look for in each directory

for additional configuration directives. See also the AllowOverride


AccessFileName .htaccess

The following lines prevent .htaccess and .htpasswd files from being

viewed by Web clients.

<Files ~ “^.ht”>
Order allow,deny
Deny from 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


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 etc/magic

HostnameLookups: Log the names of clients or just their IP addresses

e.g., (on) or (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


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

#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

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

You need to enable mod_logio.c to use %I and %O

#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 log/access_log common

If you would like to have agent and referer logfiles, uncomment the

following directives.

#CustomLog log/referer_log referer
#CustomLog log/agent_log agent

If you prefer a single logfile with access, agent, and referer information

(Combined Logfile Format) you can use the following directive.

#CustomLog log/access_log combined


This directive configures what you return as the Server HTTP response

Header. The default is ‘Full’ which sends information about the OS-Type

and compiled in modules.

Set to one of: Full | OS | Minor | Minimal | Major | Prod

where Full conveys the most information, and Prod the least.

ServerTokens Full

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/ “/usr/local/dh/apache2/template/share/icons/”

<Directory “/usr/local/dh/apache2/template/share/icons”>
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all

This should be changed to the ServerRoot/manual/. The alias provides

the manual, even if you choose to move your DocumentRoot. You may comment

this out if you do not care for the documentation.

AliasMatch ^/manual(?:/(?:de|en|es|fr|ja|ko|ru))?(/.*)?$ “/usr/local/dh/apache2/template/manual$1”

<Directory “/usr/local/dh/apache2/template/manual”>
Options Indexes
AllowOverride None
Order allow,deny
Allow from all

<Files *.html>
SetHandler type-map

SetEnvIf Request_URI ^/manual/(de|en|es|fr|ja|ko|ru)/ prefer-language=$1
RedirectMatch 301 ^/manual(?:/(de|en|es|fr|ja|ko|ru)){2,}(/.*)?$ /manual/$1$2

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


ScriptAlias /cgi-bin/ “/usr/local/dh/apache2/template/cgi-bin/”

# # Additional to mod_cgid.c settings, mod_cgid has Scriptsock # for setting UNIX socket for communicating with cgid. # #Scriptsock var/run/cgisock

“/usr/local/dh/apache2/template/cgi-bin” should be changed to whatever your ScriptAliased

CGI directory exists, if you have that configured.

<Directory “/usr/local/dh/apache2/template/cgi-bin”>
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.


Redirect permanent /foo

Directives controlling the display of server-generated directory listings.

IndexOptions: Controls the appearance of server-generated directory


IndexOptions FancyIndexing VersionSort

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


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

Commonly used filename extensions to character sets. You probably

want to avoid clashes with the language extensions, unless you

are good at carefully testing your setup after each change.

See for the

official list of charset names and their respective RFCs.

AddCharset ISO-8859-1 .iso8859-1 .latin1
AddCharset ISO-8859-2 .iso8859-2 .latin2 .cen
AddCharset ISO-8859-3 .iso8859-3 .latin3
AddCharset ISO-8859-4 .iso8859-4 .latin4
AddCharset ISO-8859-5 .iso8859-5 .latin5 .cyr .iso-ru
AddCharset ISO-8859-6 .iso8859-6 .latin6 .arb
AddCharset ISO-8859-7 .iso8859-7 .latin7 .grk
AddCharset ISO-8859-8 .iso8859-8 .latin8 .heb
AddCharset ISO-8859-9 .iso8859-9 .latin9 .trk
AddCharset ISO-2022-JP .iso2022-jp .jis
AddCharset ISO-2022-KR .iso2022-kr .kis
AddCharset ISO-2022-CN .iso2022-cn .cis
AddCharset Big5 .Big5 .big5

For russian, more than one charset is used (depends on client, mostly):

AddCharset WINDOWS-1251 .cp-1251 .win-1251
AddCharset CP866 .cp866
AddCharset KOI8-r .koi8-r .koi8-ru
AddCharset KOI8-ru .koi8-uk .ua
AddCharset ISO-10646-UCS-2 .ucs2
AddCharset ISO-10646-UCS-4 .ucs4
AddCharset UTF-8 .utf8

The set below does not map to a specific (iso) standard

but works on a fairly wide range of browsers. Note that

capitalization actually matters (it should not, but it

does for some browsers).


for a list of sorts. But browsers support few.

AddCharset GB2312 .gb2312 .gb
AddCharset utf-7 .utf7
AddCharset utf-8 .utf8
AddCharset big5 .big5 .b5
AddCharset EUC-TW .euc-tw
AddCharset EUC-JP .euc-jp
AddCharset EUC-KR .euc-kr
AddCharset shift_jis .sjis

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

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 server-parsed imagemap files:

#AddHandler imap-file map

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/”
#ErrorDocument 402

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

/usr/local/dh/apache2/template/share/error/include/ files and copying them to /your/include/path/,

even on a per-VirtualHost basis. The default include files will display

your Apache version number and your ServerAdmin email address regardless

of the setting of ServerSignature.

The internationalized error documents require mod_alias, mod_include

and mod_negotiation. To activate them, uncomment the following 30 lines.

Alias /error/ “/usr/local/dh/apache2/template/share/error/”

<Directory “/usr/local/dh/apache2/template/share/error”>

AllowOverride None

Options IncludesNoExec

AddOutputFilter Includes html

AddHandler type-map var

Order allow,deny

Allow from all

LanguagePriority en cs de es fr it ja ko nl pl pt-br ro sv tr

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 “^WebDrive” redirect-carefully
BrowserMatch “^WebDAVFS/1.[012]” redirect-carefully
BrowserMatch “^gnome-vfs” redirect-carefully

Allow server status reports generated by mod_status,

with the URL of http://servername/server-status

Change the “” to match your domain to enable.

#<Location /server-status>

SetHandler server-status

Order deny,allow

Deny from all

Allow from


Allow remote server configuration reports, with the URL of

http://servername/server-info (requires that mod_info.c be loaded).

Change the “” to match your domain to enable.

#<Location /server-info>

SetHandler server-info

Order deny,allow

Deny from all

Allow from


Bring in additional module-specific configurations

Include etc/ssl.conf

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


Use name-based virtual hosting.

#NameVirtualHost *:80

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>


DocumentRoot /www/docs/


ErrorLog log/

CustomLog log/ common

AskApache Web Development Blog

Usually, vhosts and SSL are partitioned out into separate config files, for ease of maintenance and automation (you know DH is not going to touch / sync those by hand :slight_smile: ). I’d never suggest wanting to see those sorts of config files.

Apache2 strongly recommends granularity, and for a reason. I’d think it possible to put some general info that paying customers -should- be able to see out to a separate file, and set it (alone) xx4.

I would love to find some code to show compiled in modules, as well as “loaded” modules. Not looking for trade secrets, but as I have things that are vhosted here at DH on different apache instances, it would help in the debugging when I can’t get something in a .htaccess to work properly.

Naturally I don’t want to make this output world readable. I don’t do that with <?php phpinfo(); ?> either . . .

I know that security through obscurity is no real defense, but I see not reason to give away server settings nor paths, etc. to the general public; I’ll agree on that much.

DH has a vested interest in not giving away too much of what they’ve tweaked, etc. but I’m looking for minor detail, and would rather not be bothered with asking support, and bothering them too for the most minor of things. It’d be up to DH of course as to what was “on the table” there.

responses to this thread will be emailed to me, thanks.

I bet you can find lots about what DH is up to using
$ ls -Rl /etc/apt/
$ man apt-get
and --list-uris and looking at the diffs in those directories where the .debs are stored…

Appreciate the reply, I’m not trying for “insider” knowledge, heh.

I’ve been more used to Yum and rpm, etc. but you’re right.

Support checked for me and found no differences in the packages, they had to go into each conf file and copy out the module contents, which they sent to me. Accomodating, and stuff!

Thanks, got some features working on that I was looking for.

responses to this thread will be emailed to me, thanks.

Our Apache configuration files aren’t in the repository… sorry. That being said, I’d be more than happy to answer any questions you’ve got about our configuration.