Apache Server 2.0.53

[Wender]

Hallo,
irgendwie komme ich mit den Apache Server 2.0.53 nicht klar.
Auch der Documentation/FAQ hilft mir nicht weiter von http://apache.org/

Meine genauere Problem ist:
Ich habe Apache an meinem PC installiert und möchte den Server starten. Ich habe jetzt auch connect gemacht Apache 2, zu den Ordner: \Apache Group\Apache2 Dateien angelegt.

Irgendwie kann ich das durch meine IP-Adresse nicht erreichen. Und benütze einen Router (Gateway).

Danke auch in Vorraus!
Wender

[Ashura]

Hallo Wender.

Irgendwie kann ich das durch meine IP-Adresse nicht erreichen. Und benütze einen Router (Gateway).

Die da wäre? Ist der Apache über "localhost" bzw. "127.0.0.1" erreichbar?

Gruß, Ashura

[Wender]

Nein, ist es nicht.
Die IP-Adresse geht nicht und wenn ich dies eingebe:
localhost dann kommt die seite:
http://search.msn.com/results.aspx?srch=105&FORM=AS5&q=localhost

Gruß:
Wender

[Wender]

Hallo!
Aber unter den URL: http://127.0.0.1.:8080 kann ich bei mir dies erreichen:

If you can see this, it means that the installation of the Apache web server software on this system was successful. You may now add content to this directory and replace this page.

--------------------------------------------------------------------------------

Seeing this instead of the website you expected?
This page is here because the site administrator has changed the configuration of this web server. Please contact the person responsible for maintaining this server with questions. The Apache Software Foundation, which wrote the web server software this site administrator is using, has nothing to do with maintaining this site and cannot help resolve configuration issues.

--------------------------------------------------------------------------------

The Apache documentation has been included with this distribution.

You are free to use the image below on an Apache-powered web server. Thanks for using Apache!

Gruß:
Wender

[Johannes Zeller]

Hallo Wender,

Aber unter den URL: http://127.0.0.1.:8080 kann ich bei mir dies erreichen:

Das bedeutet, dass dein Apache nicht wie normalerweise vorgesehen auf Port 80, sondern auf Port 8080 auf Anfragen wartet. Guck mal bitte, was in deiner httpd.conf (oder wie auf deinem System die Konfigurationsdatei für den Apachen heißt) für Listen und für BindAddress steht.

Schöne Grüße,

Johannes

[Ashura]

Hallo Wender.

localhost dann kommt die seite:
http://search.msn.com/results.aspx?srch=105&FORM=AS5&q=localhost

Dann wurde der Apache in der Tat noch nicht richtig eingerichtet.
Aber normalerweise sollte der Apache nach der Installation sofort lauffähig sein.

Hast du einen gültigen "DocumentRoot" in deiner httpd.conf festgelegt?
Was steht unter "C:\WINDOWS\system32\drivers\etc\Hosts" (keine Dateiendung) ?
Gibt es sonst irgend eine Fehlermeldung seitens des Überwachungsprogrammes?

Gruß, Ashura

[Wender]

Hm, bin also kein Profi. ;) Hier finde ich: C:\WINDOWS\system32\drivers\etc\Hosts

127.0.0.1       localhost #      102.54.94.97     rhino.acme.com #       38.25.63.10     x.acme.com

Unter httpd.conf steht:

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:http://httpd.apache.org/docs-2.0/ 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 "logs/foo.log"

with ServerRoot set to "G:/Program Files/Apache Group/Apache2" will be interpreted by the

server as "G:/Program Files/Apache Group/Apache2/logs/foo.log".

NOTE: Where filenames are specified, you must use forward slashes

instead of backslashes (e.g., "c:/apache" instead of "c:\apache").

If a drive letter is omitted, the drive on which Apache.exe is located

will be used by default.  It is recommended that you always supply

an explicit drive letter in absolute paths, however, to avoid

confusion.

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:http://httpd.apache.org/docs-2.0/mod/mpm_common.html#lockfile);

you will save yourself a lot of trouble.

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

ServerRoot "G:/Program Files/Apache Group/Apache2"

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

applications.

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

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

#ScoreBoardFile logs/apache_runtime_status

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

identification number when it starts.

PidFile logs/httpd.pid

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)

WinNT MPM

ThreadsPerChild: constant number of worker threads in the server process

MaxRequestsPerChild: maximum  number of requests a server process serves

<IfModule mpm_winnt.c> ThreadsPerChild 250 MaxRequestsPerChild  0 </IfModule>

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

ports, instead of the default. See also the <VirtualHost>

directive.

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

prevent Apache from glomming onto all bound IP addresses (0.0.0.0)

#Listen 12.34.56.78:80 Listen 8080

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 access_module modules/mod_access.so LoadModule actions_module modules/mod_actions.so LoadModule alias_module modules/mod_alias.so LoadModule asis_module modules/mod_asis.so LoadModule auth_module modules/mod_auth.so #LoadModule auth_anon_module modules/mod_auth_anon.so #LoadModule auth_dbm_module modules/mod_auth_dbm.so #LoadModule auth_digest_module modules/mod_auth_digest.so LoadModule autoindex_module modules/mod_autoindex.so #LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule cgi_module modules/mod_cgi.so #LoadModule dav_module modules/mod_dav.so #LoadModule dav_fs_module modules/mod_dav_fs.so LoadModule dir_module modules/mod_dir.so LoadModule env_module modules/mod_env.so #LoadModule expires_module modules/mod_expires.so #LoadModule file_cache_module modules/mod_file_cache.so #LoadModule headers_module modules/mod_headers.so LoadModule imap_module modules/mod_imap.so LoadModule include_module modules/mod_include.so #LoadModule info_module modules/mod_info.so LoadModule isapi_module modules/mod_isapi.so LoadModule log_config_module modules/mod_log_config.so LoadModule mime_module modules/mod_mime.so #LoadModule mime_magic_module modules/mod_mime_magic.so #LoadModule proxy_module modules/mod_proxy.so #LoadModule proxy_connect_module modules/mod_proxy_connect.so #LoadModule proxy_http_module modules/mod_proxy_http.so #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule negotiation_module modules/mod_negotiation.so #LoadModule rewrite_module modules/mod_rewrite.so LoadModule setenvif_module modules/mod_setenvif.so #LoadModule speling_module modules/mod_speling.so #LoadModule status_module modules/mod_status.so #LoadModule unique_id_module modules/mod_unique_id.so LoadModule userdir_module modules/mod_userdir.so #LoadModule usertrack_module modules/mod_usertrack.so #LoadModule vhost_alias_module modules/mod_vhost_alias.so #LoadModule ssl_module modules/mod_ssl.so

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

<VirtualHost> definition.  These values also provide defaults for

any <VirtualHost> containers you may define later in the file.

All of these directives may appear inside <VirtualHost> containers,

in which case these default settings will be overridden for the

virtual host being defined.

ServerAdmin: Your address, where problems with the server should be

e-mailed.  This address appears on some server-generated pages, such

as error documents.  e.g. [e-mail]

ServerAdmin [e-mail]

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

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 "G:/Program Files/Apache Group/Apache2/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

features.

<Directory />     Options FollowSymLinks     AllowOverride None </Directory>

Note that from this point forward you must specifically allow

particular features to be enabled - so if something's not working as

you might expect, make sure that you have specifically enabled it

below.

This should be changed to whatever you set DocumentRoot to.

<Directory "G:/Program Files/Apache Group/Apache2/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

http://httpd.apache.org/docs-2.0/mod/core.html#options

for more information.

Options Indexes FollowSymLinks

AllowOverride controls what directives may be placed in .htaccess files.

It can be "All", "None", or any combination of the keywords:

#   Options FileInfo AuthConfig Limit

AllowOverride None

Controls who can get stuff from this server.

Order allow,deny     Allow from all

</Directory>

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

directory if a ~user request is received.  Be especially careful to use

proper, forward slashes here.  On Windows NT, "Personal/My Website"

is a more appropriate choice.

UserDir "My Documents/My Website"

Control access to UserDir directories.  The following is an example

for a site where these directories are restricted to read-only.

You must correct the path for the root to match your system's configured

user directory location, e.g. "C:/WinNT/profiles/*/My Documents/My Website"

or whichever, as appropriate.

#<Directory "C:/Documents and Settings/*/My Documents/My Website"> #    AllowOverride FileInfo AuthConfig Limit #    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec #    <Limit GET POST OPTIONS PROPFIND> #        Order allow,deny #        Allow from all #    </Limit> #    <LimitExcept GET POST OPTIONS PROPFIND> #        Order deny,allow #        Deny from all #    </LimitExcept> #</Directory>

DirectoryIndex: sets the file that Apache will serve if a directory

is requested.

The index.html.var file (a type-map) is used to deliver content-

negotiated documents.  The MultiViews Option can be used for the

same purpose, but it is much slower.

DirectoryIndex index.html index.html.var

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

for additional configuration directives.  See also the AllowOverride

directive.

AccessFileName .htaccess

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

viewed by Web clients.

<Files ~ "^.ht">     Order allow,deny     Deny from all </Files>

TypesConfig describes where the mime.types file (or equivalent) is

to be found.

TypesConfig conf/mime.types

DefaultType is the default MIME type the server will use for a document

if it cannot otherwise determine one, such as from filename extensions.

If your server contains mostly text or HTML documents, "text/plain" is

a good value.  If most of your content is binary, such as applications

or images, you may want to use "application/octet-stream" instead to

keep browsers from trying to display binary files as though they are

text.

DefaultType text/plain

The mod_mime_magic module allows the server to use various hints from the

contents of the file itself to determine its type.  The MIMEMagicFile

directive tells the module where the hint definitions are located.

<IfModule mod_mime_magic.c>     MIMEMagicFile conf/magic </IfModule>

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

e.g., www.apache.org (on) or 204.62.129.132 (off).

The default is off because it'd be overall better for the net if people

had to knowingly turn this feature on, since enabling it means that

each client request will result in AT LEAST one lookup request to the

nameserver.

HostnameLookups Off

EnableMMAP: Control whether memory-mapping is used to deliver

files (assuming that the underlying OS supports it).

The default is on; turn this off if you serve from NFS-mounted

filesystems.  On some systems, turning it off (regardless of

filesystem) can improve performance; for details, please see

http://httpd.apache.org/docs-2.0/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.0/mod/core.html#enablesendfile

#EnableSendfile off

ErrorLog: The location of the error log file.

If you do not specify an ErrorLog directive within a <VirtualHost>

container, error messages relating to that virtual host will be

logged here.  If you do define an error logfile for a <VirtualHost>

container, that host's errors will be logged there and not here.

ErrorLog logs/error.log

LogLevel: Control the number of messages logged to the error.log.

Possible values include: debug, info, notice, warn, error, crit,

alert, emerg.

LogLevel warn

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

container, they will be logged here.  Contrariwise, if you do

define per-<VirtualHost> access logfiles, transactions will be

logged therein and not in this file.

CustomLog logs/access.log common

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

following directives.

#CustomLog logs/referer.log referer #CustomLog logs/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 logs/access.log combined

ServerTokens

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/ "G:/Program Files/Apache Group/Apache2/icons/"

<Directory "G:/Program Files/Apache Group/Apache2/icons">     Options Indexes MultiViews     AllowOverride None     Order allow,deny     Allow from all </Directory>

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))?(/.*)?$ "G:/Program Files/Apache Group/Apache2/manual$1"

<Directory "G:/Program Files/Apache Group/Apache2/manual">     Options Indexes     AllowOverride None     Order allow,deny     Allow from all

<Files *.html>         SetHandler type-map     </Files>

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

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/ "G:/Program Files/Apache Group/Apache2/cgi-bin/"

"G:/Program Files/Apache Group/Apache2/cgi-bin" should be changed to whatever your ScriptAliased

CGI directory exists, if you have that configured.

<Directory "G:/Program Files/Apache Group/Apache2/cgi-bin">     AllowOverride None     Options None     Order allow,deny     Allow from all </Directory>

Redirect allows you to tell clients about documents which used to exist in

your server's namespace, but do not anymore. This allows you to tell the

clients where to look for the relocated document.

Example:

Redirect permanent /foo http://www.example.com/bar

Directives controlling the display of server-generated directory listings.

IndexOptions: Controls the appearance of server-generated directory

listings.

IndexOptions FancyIndexing VersionSort

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

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 http://www.iana.org/assignments/character-sets 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).

See http://www.iana.org/assignments/character-sets

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 (Mosaic/X 2.1+) 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/missing_handler.pl" #ErrorDocument 402 http://www.example.com/subscription_info.html

Putting this all together, we can internationalize error responses.

We use Alias to redirect any /error/HTTP_<error>.html.var response to

our collection of by-error message multi-language collections.  We use

includes to substitute the appropriate text.

You can modify the messages' appearance without changing any of the

default HTTP_<error>.html.var files by adding the line:

#   Alias /error/include/ "/your/include/path/"

which allows you to create your own set of files by starting with the

@exp_errordir@/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/ "@exp_errordir@/"

#    <Directory "@exp_errordir@"> #        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 #    </Directory>

#    ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var #    ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var #    ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var #    ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var #    ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var #    ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var #    ErrorDocument 410 /error/HTTP_GONE.html.var #    ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var #    ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var #    ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var #    ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var #    ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var #    ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var #    ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var #    ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var #    ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var #    ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var

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

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

Bring in additional module-specific configurations

<IfModule mod_ssl.c>     Include conf/ssl.conf </IfModule>

Section 3: Virtual Hosts

VirtualHost: If you want to maintain multiple domains/hostnames on your

machine you can setup VirtualHost containers for them. Most configurations

use only name-based virtual hosts so the server doesn't need to worry about

IP addresses. This is indicated by the asterisks in the directives below.

Please see the documentation at

URL:http://httpd.apache.org/docs-2.0/vhosts/

for further details before you try to setup virtual hosts.

You may use the command line option '-S' to verify your virtual host

configuration.

Use name-based virtual hosting.

#NameVirtualHost *:80

VirtualHost example:

Almost any Apache directive may go into a VirtualHost container.

The first VirtualHost section is used for requests without a known

server name.

#<VirtualHost *:80> #    ServerAdmin [e-mail] #    DocumentRoot /www/docs/dummy-host.example.com #    ServerName dummy-host.example.com #    ErrorLog logs/dummy-host.example.com-error_log #    CustomLog logs/dummy-host.example.com-access_log common #</VirtualHost>

Und Fehlermeldungen gibt es keine. Allerdings wie gesagt kann ich den Manual Ordner hier erreichen: http://127.0.0.1:8080/manual/

Gruß: Wender

[Ashura]

Hallo Wender.

127.0.0.1       localhost
#      102.54.94.97     rhino.acme.com
#       38.25.63.10     x.acme.com

Ist in in Ordnung, das ist Standard.

Unter httpd.conf steht:

Du musst nicht alles posten. ;)

Das ist ein Kommentar

#Listen 12.34.56.78:80
Listen 8080

Ein Beispielwert steht in dem Kommentar darüber.
Also

Listen 80

ServerName -:8080

Gib hier lieber einen Namen an und den oben erwähnten Standarport an:

Bsp: www.domain.test:80

Gruß, Ashura

[Johannes Zeller]

Hallo Wender und Ashura,

#Listen 12.34.56.78:80
Listen 8080

Ein Beispielwert steht in dem Kommentar darüber.
Also

Listen 80

Falls du den Server erstmal zum testen nur lokal laufen lassen willst, mach daraus ein:

Listen 127.0.0.1:80

Mit dieser Einstellung nimmt er keine Anfragen aus dem Internet entgegen, was der Sicherheit förderlich sein dürfte, wenn du nicht sowieso hinter einem Router sitzt.

ServerName -:8080

Gib hier lieber einen Namen an und den oben erwähnten Standarport an:

Bsp: www.domain.test:80

Das sollte hier wohl sinnigerweise localhost oder Wenders DynDNS-Adresse sein.

Schöne Grüße,

Johannes

[MudGuard]

Hi,

Falls du den Server erstmal zum testen nur lokal laufen lassen willst, mach daraus ein:
Listen 127.0.0.1:80

Aufgrund des Kenntnisstandes von Wender wäre alles andere derzeit Wahnsinn …

cu,
Andreas

[Wenders]

Hallo,
http://www.dyndns.org/ kenne ich. Bin schon seit 3 Jahren da registriert, und habe das für den alten Server benützt, da meine IP-Adresse bei jeden Einwahl sich andert.
Ne, ich kenn schon mit FTP-Server's aus :) *Bin ne Programmierer*

Trotzdem geht der Apache noch nicht, dass andere leute bei meine jetzige IP das sehen kann. Hab den List grad zu 80 geandert.

Gruß:
Wenders

[Wender]

Alles klar. Jetzt hab ich dann das, wenn ich Apache starten möchte: Error: The requested operation has failed

Hab den folgenden in den Configuration:

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:http://httpd.apache.org/docs-2.0/ 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 "logs/foo.log"

with ServerRoot set to "G:/Program Files/Apache Group/Apache2" will be interpreted by the

server as "G:/Program Files/Apache Group/Apache2/logs/foo.log".

NOTE: Where filenames are specified, you must use forward slashes

instead of backslashes (e.g., "c:/apache" instead of "c:\apache").

If a drive letter is omitted, the drive on which Apache.exe is located

will be used by default.  It is recommended that you always supply

an explicit drive letter in absolute paths, however, to avoid

confusion.

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:http://httpd.apache.org/docs-2.0/mod/mpm_common.html#lockfile);

you will save yourself a lot of trouble.

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

ServerRoot "G:/Program Files/Apache Group/Apache2"

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

applications.

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

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

#ScoreBoardFile logs/apache_runtime_status

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

identification number when it starts.

PidFile logs/httpd.pid

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)

WinNT MPM

ThreadsPerChild: constant number of worker threads in the server process

MaxRequestsPerChild: maximum  number of requests a server process serves

<IfModule mpm_winnt.c> ThreadsPerChild 250 MaxRequestsPerChild  0 </IfModule>

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

ports, instead of the default. See also the <VirtualHost>

directive.

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

prevent Apache from glomming onto all bound IP addresses (0.0.0.0)

#Listen 12.34.56.78:80 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 access_module modules/mod_access.so LoadModule actions_module modules/mod_actions.so LoadModule alias_module modules/mod_alias.so LoadModule asis_module modules/mod_asis.so LoadModule auth_module modules/mod_auth.so #LoadModule auth_anon_module modules/mod_auth_anon.so #LoadModule auth_dbm_module modules/mod_auth_dbm.so #LoadModule auth_digest_module modules/mod_auth_digest.so LoadModule autoindex_module modules/mod_autoindex.so #LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule cgi_module modules/mod_cgi.so #LoadModule dav_module modules/mod_dav.so #LoadModule dav_fs_module modules/mod_dav_fs.so LoadModule dir_module modules/mod_dir.so LoadModule env_module modules/mod_env.so #LoadModule expires_module modules/mod_expires.so #LoadModule file_cache_module modules/mod_file_cache.so #LoadModule headers_module modules/mod_headers.so LoadModule imap_module modules/mod_imap.so LoadModule include_module modules/mod_include.so #LoadModule info_module modules/mod_info.so LoadModule isapi_module modules/mod_isapi.so LoadModule log_config_module modules/mod_log_config.so LoadModule mime_module modules/mod_mime.so #LoadModule mime_magic_module modules/mod_mime_magic.so #LoadModule proxy_module modules/mod_proxy.so #LoadModule proxy_connect_module modules/mod_proxy_connect.so #LoadModule proxy_http_module modules/mod_proxy_http.so #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule negotiation_module modules/mod_negotiation.so #LoadModule rewrite_module modules/mod_rewrite.so LoadModule setenvif_module modules/mod_setenvif.so #LoadModule speling_module modules/mod_speling.so #LoadModule status_module modules/mod_status.so #LoadModule unique_id_module modules/mod_unique_id.so LoadModule userdir_module modules/mod_userdir.so #LoadModule usertrack_module modules/mod_usertrack.so #LoadModule vhost_alias_module modules/mod_vhost_alias.so #LoadModule ssl_module modules/mod_ssl.so

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

<VirtualHost> definition.  These values also provide defaults for

any <VirtualHost> containers you may define later in the file.

All of these directives may appear inside <VirtualHost> containers,

in which case these default settings will be overridden for the

virtual host being defined.

ServerAdmin: Your address, where problems with the server should be

e-mailed.  This address appears on some server-generated pages, such

as error documents.  e.g. [e-mail]

ServerAdmin [e-mail]

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.domain.test: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 "G:/Program Files/Apache Group/Apache2/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

features.

<Directory />     Options FollowSymLinks     AllowOverride None </Directory>

Note that from this point forward you must specifically allow

particular features to be enabled - so if something's not working as

you might expect, make sure that you have specifically enabled it

below.

This should be changed to whatever you set DocumentRoot to.

<Directory "G:/Program Files/Apache Group/Apache2/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

http://httpd.apache.org/docs-2.0/mod/core.html#options

for more information.

Options Indexes FollowSymLinks

AllowOverride controls what directives may be placed in .htaccess files.

It can be "All", "None", or any combination of the keywords:

#   Options FileInfo AuthConfig Limit

AllowOverride None

Controls who can get stuff from this server.

Order allow,deny     Allow from all

</Directory>

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

directory if a ~user request is received.  Be especially careful to use

proper, forward slashes here.  On Windows NT, "Personal/My Website"

is a more appropriate choice.

UserDir "My Documents/My Website"

Control access to UserDir directories.  The following is an example

for a site where these directories are restricted to read-only.

You must correct the path for the root to match your system's configured

user directory location, e.g. "C:/WinNT/profiles/*/My Documents/My Website"

or whichever, as appropriate.

#<Directory "C:/Documents and Settings/*/My Documents/My Website"> #    AllowOverride FileInfo AuthConfig Limit #    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec #    <Limit GET POST OPTIONS PROPFIND> #        Order allow,deny #        Allow from all #    </Limit> #    <LimitExcept GET POST OPTIONS PROPFIND> #        Order deny,allow #        Deny from all #    </LimitExcept> #</Directory>

DirectoryIndex: sets the file that Apache will serve if a directory

is requested.

The index.html.var file (a type-map) is used to deliver content-

negotiated documents.  The MultiViews Option can be used for the

same purpose, but it is much slower.

DirectoryIndex index.html index.html.var

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

for additional configuration directives.  See also the AllowOverride

directive.

AccessFileName .htaccess

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

viewed by Web clients.

<Files ~ "^.ht">     Order allow,deny     Deny from all </Files>

TypesConfig describes where the mime.types file (or equivalent) is

to be found.

TypesConfig conf/mime.types

DefaultType is the default MIME type the server will use for a document

if it cannot otherwise determine one, such as from filename extensions.

If your server contains mostly text or HTML documents, "text/plain" is

a good value.  If most of your content is binary, such as applications

or images, you may want to use "application/octet-stream" instead to

keep browsers from trying to display binary files as though they are

text.

DefaultType text/plain

The mod_mime_magic module allows the server to use various hints from the

contents of the file itself to determine its type.  The MIMEMagicFile

directive tells the module where the hint definitions are located.

<IfModule mod_mime_magic.c>     MIMEMagicFile conf/magic </IfModule>

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

e.g., www.apache.org (on) or 204.62.129.132 (off).

The default is off because it'd be overall better for the net if people

had to knowingly turn this feature on, since enabling it means that

each client request will result in AT LEAST one lookup request to the

nameserver.

HostnameLookups Off

EnableMMAP: Control whether memory-mapping is used to deliver

files (assuming that the underlying OS supports it).

The default is on; turn this off if you serve from NFS-mounted

filesystems.  On some systems, turning it off (regardless of

filesystem) can improve performance; for details, please see

http://httpd.apache.org/docs-2.0/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.0/mod/core.html#enablesendfile

#EnableSendfile off

ErrorLog: The location of the error log file.

If you do not specify an ErrorLog directive within a <VirtualHost>

container, error messages relating to that virtual host will be

logged here.  If you do define an error logfile for a <VirtualHost>

container, that host's errors will be logged there and not here.

ErrorLog logs/error.log

LogLevel: Control the number of messages logged to the error.log.

Possible values include: debug, info, notice, warn, error, crit,

alert, emerg.

LogLevel warn

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

container, they will be logged here.  Contrariwise, if you do

define per-<VirtualHost> access logfiles, transactions will be

logged therein and not in this file.

CustomLog logs/access.log common

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

following directives.

#CustomLog logs/referer.log referer #CustomLog logs/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 logs/access.log combined

ServerTokens

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/ "G:/Program Files/Apache Group/Apache2/icons/"

<Directory "G:/Program Files/Apache Group/Apache2/icons">     Options Indexes MultiViews     AllowOverride None     Order allow,deny     Allow from all </Directory>

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))?(/.*)?$ "G:/Program Files/Apache Group/Apache2/manual$1"

<Directory "G:/Program Files/Apache Group/Apache2/manual">     Options Indexes     AllowOverride None     Order allow,deny     Allow from all

<Files *.html>         SetHandler type-map     </Files>

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

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/ "G:/Program Files/Apache Group/Apache2/cgi-bin/"

"G:/Program Files/Apache Group/Apache2/cgi-bin" should be changed to whatever your ScriptAliased

CGI directory exists, if you have that configured.

<Directory "G:/Program Files/Apache Group/Apache2/cgi-bin">     AllowOverride None     Options None     Order allow,deny     Allow from all </Directory>

Redirect allows you to tell clients about documents which used to exist in

your server's namespace, but do not anymore. This allows you to tell the

clients where to look for the relocated document.

Example:

Redirect permanent /foo http://www.example.com/bar

Directives controlling the display of server-generated directory listings.

IndexOptions: Controls the appearance of server-generated directory

listings.

IndexOptions FancyIndexing VersionSort

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

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 http://www.iana.org/assignments/character-sets 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).

See http://www.iana.org/assignments/character-sets

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 (Mosaic/X 2.1+) 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/missing_handler.pl" #ErrorDocument 402 http://www.example.com/subscription_info.html

Putting this all together, we can internationalize error responses.

We use Alias to redirect any /error/HTTP_<error>.html.var response to

our collection of by-error message multi-language collections.  We use

includes to substitute the appropriate text.

You can modify the messages' appearance without changing any of the

default HTTP_<error>.html.var files by adding the line:

#   Alias /error/include/ "/your/include/path/"

which allows you to create your own set of files by starting with the

@exp_errordir@/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/ "@exp_errordir@/"

#    <Directory "@exp_errordir@"> #        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 #    </Directory>

#    ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var #    ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var #    ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var #    ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var #    ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var #    ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var #    ErrorDocument 410 /error/HTTP_GONE.html.var #    ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var #    ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var #    ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var #    ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var #    ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var #    ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var #    ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var #    ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var #    ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var #    ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var

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

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

Bring in additional module-specific configurations

<IfModule mod_ssl.c>     Include conf/ssl.conf </IfModule>

Section 3: Virtual Hosts

VirtualHost: If you want to maintain multiple domains/hostnames on your

machine you can setup VirtualHost containers for them. Most configurations

use only name-based virtual hosts so the server doesn't need to worry about

IP addresses. This is indicated by the asterisks in the directives below.

Please see the documentation at

URL:http://httpd.apache.org/docs-2.0/vhosts/

for further details before you try to setup virtual hosts.

You may use the command line option '-S' to verify your virtual host

configuration.

Use name-based virtual hosting.

#NameVirtualHost *:80

VirtualHost example:

Almost any Apache directive may go into a VirtualHost container.

The first VirtualHost section is used for requests without a known

server name.

#<VirtualHost *:80> #    ServerAdmin [e-mail] #    DocumentRoot /www/docs/dummy-host.example.com #    ServerName dummy-host.example.com #    ErrorLog logs/dummy-host.example.com-error_log #    CustomLog logs/dummy-host.example.com-access_log common #</VirtualHost>

Ich hab das zuerstmal zu www.domain.test:80 erganzt. Soll ich statt Domain die IP-Adresse eingeben? Da ich möchte nur, dass das nur mit IP Adresse erreichbar ist.

Und wie können das die anderen Leute sehen durch meine IP-Adresse?

Gruß: Wender

[Ashura]

Hallo Wender.

Alles klar. Jetzt hab ich dann das, wenn ich Apache starten möchte:
Error: The requested operation has failed

Hab den folgenden in den Configuration:

Bitte unterlasse es fortan, deine gesamte httpd.conf zu posten.
Poste teile davon und wenn möglich mit den Codeblöcken <code lang=apache></code> (< und > durch [ und ] ersetzen)

ServerName -:www.domain.test:80

Der ServerName lautet nach wie vor "-" mit einem ungültigen Port obendrein.

Ich hab das zuerstmal zu www.domain.test:80 erganzt. Soll ich statt Domain die IP-Adresse eingeben? Da ich möchte nur, dass das nur mit IP Adresse erreichbar ist.

servername:port, siehe auch Johannes' Post.

Und wie können das die anderen Leute sehen durch meine IP-Adresse?

Was können andere Leute sehen?

Gruß, Ashura

[Johannes Zeller]

Hallo Wender,

Du brauchst wirklich nicht immer die ganze Konfigurationsdatei einzubinden. Es reicht wenn du die relevanten Stellen angibts. In deinem Fall sind das ja einfach die Zeilen, die du verändert hast.

Solltest du trotzdem mal in die Gelegenheit kommen, dass du überhaupt keine Ahnung hast, welche Stelle einer Konfigurationsdatei für dein Problem verantwortlich ist, solltest du sie irgendwo hochladen und dann verlinken. Wenn du gerade keinen Online-Webserver zur Verfügung hast, kannst du das über http://phpfi.com/ oder einen ähnlichen Service machen.

ServerName -:www.domain.test:80

Hier liegt der Fehler. Das -: muss weg.

Ich hab das zuerstmal zu www.domain.test:80 erganzt. Soll ich statt Domain die IP-Adresse eingeben? Da ich möchte nur, dass das nur mit IP Adresse erreichbar ist.

Das kannst du da nicht einstellen. Wie ich schon erklärt habe, solltest du deine lokale IP-Adresse oder deinen DynDNS-Host angeben. Natürlich kannst du auch irgendeine andere, nicht vergeben Domain verwenden.

Und wie können das die anderen Leute sehen durch meine IP-Adresse?

Was genau meinst du damit jetzt?

Schöne Grüße,

Johannes

[Wender]

So, danke für eure Hilfe.
Na, Danke MudGuard! Ich habe früher mit anderen Proxys-Server gearbeitet.

Ich kann jetzt das unter:
http://127.0.0.1
localhost
erreichen.

Allerdings meinte ich damit, wie können die andere leute meinen page sehen durch meine IP-Nummer? Unter andere leute meine ich: mit einen anderen Internet-Verbindung und nicht durch http://127.0.0.1-localhost.

Gruß:
Wenders

[Johannes Zeller]

Hallo Wender,

Na, Danke MudGuard! Ich habe früher mit anderen Proxys-Server gearbeitet.

Andreas hat es keineswegs böse gemeint. Selbst wenn du früher mit anderen Webservern gearbeitet hast (wieso erwähnst du hier »Proxy-Server«?) sind deine Kenntnisse in Bezug auf den Apache wirklich noch so mager, das auch ich dir eine wirklich sichere Konfiguration nicht zutraue. Das was du hier nachfragst ist eigentlich elementare Konfiguration. Aber es hat ja schließlich jeder von uns auch mal klein angefangen.

Ich kann jetzt das unter:
http://127.0.0.1
localhost
erreichen.

Allerdings meinte ich damit, wie können die andere leute meinen page sehen durch meine IP-Nummer? Unter andere leute meine ich: mit einen anderen Internet-Verbindung und nicht durch http://127.0.0.1-localhost.

Erst mal gar nicht. Und das ist gut so[tm]. Bevor du dich mit deinem Webserver der feindlichen Welt des Internets präsentierst solltest du erstmal ein paar Erfahrungen damit lokal sammeln.

Wenn du diese Anweisung

Listen 127.0.0.1:80

durch

Listen 80

ersetzt, ist dein Server theoretisch für Jeden erreichbar. Das heißt Jeder, der deine aktuelle IP-Adresse kennt. Er kann dann auf deine Seiten über http://<deine.ip-adresse>/ zugreifen. Ich würde dir aber sehr davon abraten, das jetzt schon so einzurichten.

Echte[tm] Server, die in einem Rechenzentrum stehen, haben natürlich eine feste IP-Adresse. Deshalb kann man die diesem Server zugewiesenen Domains fest im DNS eintragen. Wenn du für deinen eigenen Rechner auch eine Domain-Adresse haben willst, musst die Zuweisung Domain -> IP-Adresse bei jedem Verbindungsaufbau geändert werden. Ein Dienst, der solche Domains anbietet, ist z.B. http://www.dyndns.org/.

Schöne Grüße,

Johannes

[Dennis]

Hi Johannes,

Listen 80

ersetzt, ist dein Server theoretisch für Jeden erreichbar.

Ähm, aber auch nur theoretisch - wenn du beispielsweise hinter einem Router sitzt musst du diesem noch sagen, dass er Anfragen von außen auf Port 80 auf deine interne IP, Port 80 umleiten soll. Dazu gibt es normalerweise im Konfigurationsmenü des Routers einen Punkt NAT (Network Adress Translation) oder auch Portumleitung genannt.

MfG, Dennis.

[Dennis]

Hi Wender,

Nein, ist es nicht.
Die IP-Adresse geht nicht und wenn ich dies eingebe:
localhost dann kommt die seite:
http://search.msn.com/results.aspx?srch=105&FORM=AS5&q=localhost

Hast du auch mal versucht, das mit einem Browser aufzurufen? (Nein, der IE ist kein Browser.) Da gibt oft eine genauere Fehlermeldung...

Du sitzt aber schon an dem PC, auf dem der Apache installiert ist, oder? Und du bist auch sicher, dass der Apache läuft und auf Anfragen auf Port 80 hört?

MfG, Dennis.