+ Funguje to! Na tomto serveru bì¾í Apache! +
++ Pokud vidíte tuto zprávu, správce tohoto poèítaèe právì úspì¹nì + nainstaloval Apache web server. + Teï je¹tì musí doplnit obsah a nahradit tuto standardní uvítací + stránku, nebo pøesmìrovat server na skuteènou domovskou stránku. +
++
+ Pokud vidíte tuto zprávu místo oèekávané domovské stránky, + kontaktujte, prosím, správce pøíslu¹ného web + serveru. (Zkuste poslat e-mail na adresu + <Webmaster@domain>.) + Pøesto¾e tento server pou¾ívá program Apache, témìø jistì nemá nic + spoleèného s Apache Group, proto prosím neposílejte e-maily o tomto + serveru nebo jeho obsahu autorùm Apache. Pokud to udìláte, budeme + va¹e zprávy ignorovat. ++
+
+ Zde najdete + dokumentaci + Apache (anglicky) obsa¾enou v této distribuci. +
++ Následující logo mù¾e být pou¾ito bez omezení na web serveru s + programem Apache. Dìkujeme za pou¾ití Apache! +
+
+ 
+
+
+
diff --git a/docs/docroot/index.html.hr.iso8859-2 b/docs/docroot/index.html.hr.iso8859-2
new file mode 100644
index 00000000000..7af963d66f6
--- /dev/null
+++ b/docs/docroot/index.html.hr.iso8859-2
@@ -0,0 +1,35 @@
+
+
+
+
+
+ Èestitamo! Apache web poslu¾itelj funkcionira!
+Ukoliko vidite ovu stranicu, to znaèi da je instalacija Apache web poslu¾itelja uspje¹no izvr¹ena na ovom raèunalu. +Sada mo¾ete dodati sadr¾aj u ovaj direktorij te promijeniti ovu stranicu.
+ ++
Oèekivali ste neku drugu stranicu?
+ +Ovu stranica vidite stoga ¹to je administrator ovog poslu¾itelja promijenio +konfiguraciju. Apache Softver Fondacija napisala je softver koji koristi +administrator ovog web poslu¾itelja i nije odgovorna za odr¾avanje ovog poslu¾itelja. Molimo vas da za sva pitanja kontaktirate odgovornu +osobu za odr¾avanje ovog poslu¾itelja.
+ ++
Ovdje se nalazi Dokumentacija o Apache web poslu¾itelju +(engleski).
+ +Donju slièicu mo¾ete slobodno koristiti na stranicama ovog veb poslu¾itelja. +Hvala vam ¹to koristite Apache!
+ ++ Det gjekk bra! Apache er no installert på denne maskina! +
++ Dersom du kan sjå denne sida, har den eller dei som driv denne nettstaden + installert Apache vevtenar. + No må denne testsida erstattast med verkeleg innhald. +
++
+ Dersom du hadde venta å sjå ei anna side enn denne, bør du + ta kontakt med den som er ansvarleg for denne nettstaden + (Prøv å sende e-post til <webmaster@domene>.) + Sjølv om denne nettstaden vert kjørt på Apache, har den ingen annan + tilknytning til Apache-gruppa, som har utvikla programvaren. + Ver snill og ikkje send e-post om denne nettstaden eller + innhaldet du finn her til utviklarane i Apache-gruppa. + I så tilfelle vil førespurnaden ignorerast. ++
+
+ Dokumentasjon + for Apache er inkludert i denne pakka. +
++ Logoen under kan brukast på kva som helst av maskiner som køyrer Apache. + Takk for at du nyttar Apache! +
+
+
+
+
+
diff --git a/docs/docroot/index.html.po.iso8859-2 b/docs/docroot/index.html.po.iso8859-2
new file mode 100644
index 00000000000..8b030bd6516
--- /dev/null
+++ b/docs/docroot/index.html.po.iso8859-2
@@ -0,0 +1,40 @@
+
+
+
+
+ +Je¿eli strona ta jest widoczna, oznacza to poprawn± instalacjê serwera Apache. Mo¿na ju¿ zamieniæ zawarto¶æ tej witryny. + +
+ +
Czy zamiast spodziewanej witryny WWW widoczna jest ta?
+ ++Strona ta jest widoczna, poniewa¿ administrator serwera WWW zmieni³ jego konfiguracjê. +Proszê skontaktowaæ siê z osob± odpowiedzialn± za zarz±dzanie tym serwerem. Apache Software Foundation, producent oprogramowania serwerowego Apache, nie administruje t± witryn± i nie jest w stanie pomóc w sprawach zwi±zanych z jej konfiguracj±. + +
+ + +
+Do niniejszej dystrybucji serwera Apache do³±czono anglojêzyczn± dokumentacjê. + +
+Poni¿sze logo, "Powered by Apache", mo¿na stosowaæ bez ograniczeñ. Dziêkujemy za wybranie Apache'a! + +
+ + + + + Die Anfrage kann nicht beantwortet werden, da im Server + ein interner Fehler aufgetreten ist. + Der Server ist entweder überlastet oder ein Fehler in + einem CGI-Script ist aufgetreten. + + + + +----------de-- + +Content-language: en +Content-type: text/html +Body:----------en-- + + + + + + + + The server encountered an internal error and was + unable to complete your request. The server is either + overloaded or there was an error in a CGI script. + + + + +----------en-- + +Content-language: es +Content-type: text/html +Body:----------es-- + + + + + + + + El servidor encontro un error interno y fue + imposible completar su solicitud. + Existe tambien la posibilidad de que el servidor + este sobrecargado o de algún error en un + programa de CGI. + + + + +----------es-- + +Content-language: fr +Content-type: text/html +Body:----------fr-- + + + + + + + + Le serveur a èté victime d'une erreur interne et n'a pas été + capable de faire aboutir votre requête. Soit le server est surchargé + soit il s'agit d'une erreur dans le script CGI. + + + + +----------fr-- diff --git a/docs/error/HTTP_LENGTH_REQUIRED.html.var b/docs/error/HTTP_LENGTH_REQUIRED.html.var new file mode 100644 index 00000000000..24d6909c3c4 --- /dev/null +++ b/docs/error/HTTP_LENGTH_REQUIRED.html.var @@ -0,0 +1,37 @@ +Content-language: de +Content-type: text/html +Body:----------de-- + + + + Die Anfrage kann nicht beantwortet werden. + Bei Verwendung der -Methode + muß ein korrekter
Content-Length-Header
+ angegeben werden.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ A request with the
+ method requires a valid Content-Length header.
+
+
+----------en--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+ Une requête utilisant la méthode
+ nécessite un header valable Content-Length (indiquant la longueur).
+
+
+----------fr--
diff --git a/docs/error/HTTP_METHOD_NOT_ALLOWED.html.var b/docs/error/HTTP_METHOD_NOT_ALLOWED.html.var
new file mode 100644
index 00000000000..38d2bd8a05c
--- /dev/null
+++ b/docs/error/HTTP_METHOD_NOT_ALLOWED.html.var
@@ -0,0 +1,48 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Die -Methode
+ ist für den angeforderten URL nicht erlaubt.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The
+ method is not allowed for the requested URL.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ El
+ método utilizado por su solicitud no esta
+ permitido por el URL.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+ La méthode
+ n'est pas utilisable pour l'URL requise.
+
+
+----------fr--
diff --git a/docs/error/HTTP_NOT_ACCEPTABLE.html.var b/docs/error/HTTP_NOT_ACCEPTABLE.html.var
new file mode 100644
index 00000000000..fe4236fac7f
--- /dev/null
+++ b/docs/error/HTTP_NOT_ACCEPTABLE.html.var
@@ -0,0 +1,49 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Unter dem angeforderten URL konnte kein geeignetes Objekt
+ auf dem Server gefunden werden, das dem vom Browser
+ geforderten Format entsprechen würde.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ An appropriate representation of the requested resource
+ could not be found on this server.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ Una representación apropiada de los recursos
+ solicitados no ha podido ser localizada en
+ este servidor.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+ Une représentation appropriée de la ressource requise
+ n'a pu être trouvée sur ce serveur.
+
+
+----------fr--
diff --git a/docs/error/HTTP_NOT_FOUND.html.var b/docs/error/HTTP_NOT_FOUND.html.var
new file mode 100644
index 00000000000..8a7e8ee5fb8
--- /dev/null
+++ b/docs/error/HTTP_NOT_FOUND.html.var
@@ -0,0 +1,113 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Der angeforderte URL konnte auf dem Server nicht gefunden werden.
+
+
+
+ Der Link auf der
+ ">verweisenden
+Seite<
+/a>
+ scheint falsch oder nicht mehr aktuell zu sein.
+ Bitte informieren Sie den Autor
+ ">dieser Seite
+ über den Fehler.
+
+
+
+ Sofern Sie den URL manuell eingegeben haben,
+ überprüfen Sie bitte die Schreibweise und versuchen es erneut.
+
+
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The requested URL was not found on this server.
+
+
+
+ The link on the
+ ">referring
+page
+ seems to be wrong or outdated. Please inform the author of
+ ">that page
+ about the error.
+
+
+
+ If you entered the URL manually please check your
+ spelling and try again.
+
+
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ El URL requerido no ha sido localizado en
+ este servidor.
+
+
+
+ El URL en la
+ ">página
+referida
+ parece tener algun error o estar fuera de tiempo. Porfavor
+ comunique al autor de
+ ">la
+página
+ acerca del error.
+
+
+
+ Si usted provisiono el URL de manera manual le solicitamos
+ que porfavor revise los datos e intente de nuevo.
+
+
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+ L'URL requise n'a pu etre trouvée sur ce serveur.
+
+
+
+ La référence sur
+ ">la page
+citée
+ semble être erronée ou perimée. Nous vous prions
+d'informer l'auteur de
+ ">cette page
+ de cette erreur.
+
+
+
+ Si vous avez tapé l'URL à la main, veuillez vérifier
+ l'orthographe et réessayer.
+
+
+
+
+----------fr--
diff --git a/docs/error/HTTP_NOT_IMPLEMENTED.html.var b/docs/error/HTTP_NOT_IMPLEMENTED.html.var
new file mode 100644
index 00000000000..ed3468eaf3b
--- /dev/null
+++ b/docs/error/HTTP_NOT_IMPLEMENTED.html.var
@@ -0,0 +1,45 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Die vom Browser angeforderte Aktion wird vom Server
+ nicht unterstützt.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The server does not support the action requested by the browser.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ El buscador esta solicitando una acción
+ que no puede ser procesada.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+Le serveur n'est pas en mesure d'effectuer l'action requise par le navigateur.
+
+
+----------fr--
diff --git a/docs/error/HTTP_PRECONDITION_FAILED.html.var b/docs/error/HTTP_PRECONDITION_FAILED.html.var
new file mode 100644
index 00000000000..164bfcef6d8
--- /dev/null
+++ b/docs/error/HTTP_PRECONDITION_FAILED.html.var
@@ -0,0 +1,44 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Die Vorbedingung unter dem angeforderten URL wurde
+ negativ ausgewertet.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The precondition on the request for the URL failed positive evaluation.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ La precondicion para que exista una
+ conección al URL solicitado es falsa.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+La précondition pour l'URL requise a été évaluée négativement.
+
+----------fr--
diff --git a/docs/error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var b/docs/error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
new file mode 100644
index 00000000000..af7ef260e02
--- /dev/null
+++ b/docs/error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
@@ -0,0 +1,51 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Die bei der Anfrage übermittelnden Daten sind für
+ die -Methode nicht erlaubt
+ oder die Datenmenge hat das Maximum überschritten.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The method does not allow the data
+ transmitted, or the data volume exceeds the capacity limit.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ Los recursos establecidos no permiten peticiones con
+ el método
+ suministrado por su solicitud, o, la cantidad de datos
+ provistos exceden los límites de capacidad.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+La méthode
+n'autorise pas le transfert de ces données ou bien le volume
+des données excède la limite de capacité.
+
+
+----------fr--
diff --git a/docs/error/HTTP_REQUEST_TIME_OUT.html.var b/docs/error/HTTP_REQUEST_TIME_OUT.html.var
new file mode 100644
index 00000000000..6295279a037
--- /dev/null
+++ b/docs/error/HTTP_REQUEST_TIME_OUT.html.var
@@ -0,0 +1,48 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Der Server konnte nicht mehr länger auf die Beendigung
+ der Browseranfrage warten, die Netzwerkverbindung wurde
+ vom Server geschlossen.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The server closed the network connection because the browser
+ didn't finish the request within the specified time.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ El servidor ha cerrado la conección de red
+ debido a que el buscador no termino la solicitud
+ dentro del tiempo especificado.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+La précondition pour l'URL requise a été évaluée négativement.
+
+
+----------fr--
diff --git a/docs/error/HTTP_REQUEST_URI_TOO_LARGE.html.var b/docs/error/HTTP_REQUEST_URI_TOO_LARGE.html.var
new file mode 100644
index 00000000000..f34de5558c9
--- /dev/null
+++ b/docs/error/HTTP_REQUEST_URI_TOO_LARGE.html.var
@@ -0,0 +1,48 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Der bei der Anfrage übermittelnde URI überschreitet
+ die maximale Länge.
+ Die Anfrage kann nicht ausgeführt werden.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The length of the requested URL exceeds the capacity limit for this server.
+ The request cannot be processed.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ Su solicitud no puede procesarse debido a que la
+ longitud del URL excede la capacidad limite del
+ servidor.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+La longueur de l'URL demandée excède la limite de capacitè pour ce serveur. Nous ne pouvons donner suite à votre requête.
+
+
+----------fr--
diff --git a/docs/error/HTTP_SERVICE_UNAVAILABLE.html.var b/docs/error/HTTP_SERVICE_UNAVAILABLE.html.var
new file mode 100644
index 00000000000..d29f16fac8f
--- /dev/null
+++ b/docs/error/HTTP_SERVICE_UNAVAILABLE.html.var
@@ -0,0 +1,56 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Der Server ist derzeit nicht in der Lage die Anfrage
+ zu bearbeiten. Entweder ist der Server derzeit überlastet
+ oder wegen Wartungsarbeiten nicht verfügbar.
+ Bitte versuchen Sie es später wieder.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The server is temporarily unable to service your
+ request due to maintenance downtime or capacity
+ problems. Please try again later.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ El servidor no puede atender su solicitud por
+ el momento debido a problemas de mantenimiento
+ o de capacidad.
+
+ Le solicitamos que porfavor repita la operación
+ mas tarde.
+
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+ En raison de travaux de maintenance ou de problèmes de capacité
+ le serveur n'est pas en mesure de répondre à votre requête pour l'instant.
+ Veuillez réessayer plus tard.
+
+
+----------fr--
diff --git a/docs/error/HTTP_UNAUTHORIZED.html.var b/docs/error/HTTP_UNAUTHORIZED.html.var
new file mode 100644
index 00000000000..4152b66146b
--- /dev/null
+++ b/docs/error/HTTP_UNAUTHORIZED.html.var
@@ -0,0 +1,84 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Der Server konnte nicht verifizieren, ob Sie authorisiert sind,
+ auf den URL "" zuzugreifen.
+ Entweder wurden falsche Referenzen (z.B. ein falsches Passwort)
+ angeben oder ihr Browser versteht nicht, wie die geforderten
+ Referenzen zu übermitteln sind.
+
+
+
+ Sofern Sie für den Zugriff berechtigt sind, überprüfen Sie bitte
+ die eingegebene User-ID und das Passwort und versuchen es erneut.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ This server could not verify that you are authorized to access
+ the URL "".
+ You either supplied the wrong credentials (e.g., bad password), or your
+ browser doesn't understand how to supply the credentials required.
+
+
+
+ In case you are allowed to request the document, please
+ check your user-id and password and try again.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ El servidor no puede certificar que usted este autorizado
+ para accesar el URL "".
+ Usted pudo suministrar información incorrecta accidentalmente
+ (ejem. una contraseña inválida) o, el buscador no sabe
+ como suministrar la información requerida.
+
+
+
+ En caso de que a usted le este permitido el uso del
+ documento requerido, le solicitamos de la manera mas atenta
+ que porfavor vuelva a intentar la operación suministrando
+ nuevamente su numero de identificación y su contraseña.
+
+ Muchas Gracias.
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+ Ce server n'a pas été en mesure de vérifier que
+ vous êtes autorisé à accéder à cette
+ URL "".
+
+ Vous avez ou bien fourni des coordonnées erronées
+ (p.ex. mot de passe inexact) ou bien votre navigateur ne parvient
+ pas à fournir les données exactes.
+
+
+
+ Si vous êtez autorisé à requérir le document,
+ veuillez vérifier votre nom d'utilisateur et votre mot de passe
+ et réessayer.
+
+
+----------fr--
diff --git a/docs/error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var b/docs/error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
new file mode 100644
index 00000000000..78c48bd2c42
--- /dev/null
+++ b/docs/error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
@@ -0,0 +1,45 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Das bei der Anfrage übermittelte Format (media type)
+ wird vom Server nicht unterstützt.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ The server does not support the media type transmitted in the request.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ Los datos de su solicitud no se encuentran en
+ un formato aceptado por este recurso.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+Le serveur ne supporte pas le type de média utilisé dans votre requête.
+
+
+----------fr--
diff --git a/docs/error/HTTP_VARIANT_ALSO_VARIES.html.var b/docs/error/HTTP_VARIANT_ALSO_VARIES.html.var
new file mode 100644
index 00000000000..b558284f477
--- /dev/null
+++ b/docs/error/HTTP_VARIANT_ALSO_VARIES.html.var
@@ -0,0 +1,51 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+
+
+
+ Ein Zugriff auf das angeforderte Objekt bzw. einer
+ Variante dieses Objektes ist nicht möglich, da es ebenfalls
+ ein variables Objekt darstellt.
+
+
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+
+
+
+ A variant for the requested entity
+ is itself a negotiable resource.
+ Access not possible.
+
+
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+
+
+
+ No es posible tener acceso debido a que
+ una variante de la solicitud es por si
+ misma un recurso negociable.
+
+
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+
+
+
+ Une variante pour l'entité requise
+ est elle-même une ressource négociable.
+ L'accès est impossible.
+
+
+----------fr--
diff --git a/docs/error/contact.html.var b/docs/error/contact.html.var
new file mode 100644
index 00000000000..f39136b6373
--- /dev/null
+++ b/docs/error/contact.html.var
@@ -0,0 +1,30 @@
+Content-language: de
+Content-type: text/html
+Body:----------de--
+ Sofern Sie dies für eine Fehlfunktion des Servers halten,
+ informieren Sie bitte den
+ ">Webmaster
+ hierüber.
+----------de--
+
+Content-language: en
+Content-type: text/html
+Body:----------en--
+ In case you think this is a server error, please contact
+ the ">Webmaster
+----------en--
+
+Content-language: es
+Content-type: text/html
+Body:----------es--
+Favor de contactar al
+">Webmaster
+en caso de que usted crea que existe un error en el servidor.
+----------es--
+
+Content-language: fr
+Content-type: text/html
+Body:----------fr--
+Si vous pensez qu'il s'agit d'une erreur du serveur, veuillez contacter
+le ">gestionnaire du site
+----------fr--
diff --git a/docs/error/include/bottom.html b/docs/error/include/bottom.html
new file mode 100644
index 00000000000..a3b23698d37
--- /dev/null
+++ b/docs/error/include/bottom.html
@@ -0,0 +1,12 @@
+
+
+
+
+ rightleft> + + +
| +Error + |
-
diff --git a/docs/error/include/top.html b/docs/error/include/top.html
new file mode 100644
index 00000000000..3e24e486155
--- /dev/null
+++ b/docs/error/include/top.html
@@ -0,0 +1,12 @@
+
+
+
++
+ ++ + SRC="/error/images/logo.gif" ALT=""> + +
-
+
-
diff --git a/docs/icons/a.png b/docs/icons/a.png
new file mode 100644
index 00000000000..c1840256dcf
Binary files /dev/null and b/docs/icons/a.png differ
diff --git a/docs/icons/alert.black.png b/docs/icons/alert.black.png
new file mode 100644
index 00000000000..af6b1246ad7
Binary files /dev/null and b/docs/icons/alert.black.png differ
diff --git a/docs/icons/alert.red.png b/docs/icons/alert.red.png
new file mode 100644
index 00000000000..b9222fd5246
Binary files /dev/null and b/docs/icons/alert.red.png differ
diff --git a/docs/icons/apache_pb.png b/docs/icons/apache_pb.png
new file mode 100644
index 00000000000..eb99a8cd393
Binary files /dev/null and b/docs/icons/apache_pb.png differ
diff --git a/docs/icons/apache_pb2.png b/docs/icons/apache_pb2.png
new file mode 100644
index 00000000000..28baa70fb8c
Binary files /dev/null and b/docs/icons/apache_pb2.png differ
diff --git a/docs/icons/back.png b/docs/icons/back.png
new file mode 100644
index 00000000000..2d8d353bbc7
Binary files /dev/null and b/docs/icons/back.png differ
diff --git a/docs/icons/ball.gray.png b/docs/icons/ball.gray.png
new file mode 100644
index 00000000000..7b756f2d82d
Binary files /dev/null and b/docs/icons/ball.gray.png differ
diff --git a/docs/icons/ball.red.png b/docs/icons/ball.red.png
new file mode 100644
index 00000000000..05f3e50629c
Binary files /dev/null and b/docs/icons/ball.red.png differ
diff --git a/docs/icons/binary.png b/docs/icons/binary.png
new file mode 100644
index 00000000000..c5119d1e1ea
Binary files /dev/null and b/docs/icons/binary.png differ
diff --git a/docs/icons/binhex.png b/docs/icons/binhex.png
new file mode 100644
index 00000000000..eff532202d3
Binary files /dev/null and b/docs/icons/binhex.png differ
diff --git a/docs/icons/blank.png b/docs/icons/blank.png
new file mode 100644
index 00000000000..3802c03c9c8
Binary files /dev/null and b/docs/icons/blank.png differ
diff --git a/docs/icons/bomb.png b/docs/icons/bomb.png
new file mode 100644
index 00000000000..5261a0575e3
Binary files /dev/null and b/docs/icons/bomb.png differ
diff --git a/docs/icons/box1.png b/docs/icons/box1.png
new file mode 100644
index 00000000000..c55fccf8dc8
Binary files /dev/null and b/docs/icons/box1.png differ
diff --git a/docs/icons/box2.png b/docs/icons/box2.png
new file mode 100644
index 00000000000..26d14325d97
Binary files /dev/null and b/docs/icons/box2.png differ
diff --git a/docs/icons/broken.png b/docs/icons/broken.png
new file mode 100644
index 00000000000..e8fd150a339
Binary files /dev/null and b/docs/icons/broken.png differ
diff --git a/docs/icons/burst.png b/docs/icons/burst.png
new file mode 100644
index 00000000000..2329898f2a4
Binary files /dev/null and b/docs/icons/burst.png differ
diff --git a/docs/icons/c.png b/docs/icons/c.png
new file mode 100644
index 00000000000..41593b36b36
Binary files /dev/null and b/docs/icons/c.png differ
diff --git a/docs/icons/comp.blue.png b/docs/icons/comp.blue.png
new file mode 100644
index 00000000000..60ff156deb9
Binary files /dev/null and b/docs/icons/comp.blue.png differ
diff --git a/docs/icons/comp.gray.png b/docs/icons/comp.gray.png
new file mode 100644
index 00000000000..01538f8f316
Binary files /dev/null and b/docs/icons/comp.gray.png differ
diff --git a/docs/icons/compressed.png b/docs/icons/compressed.png
new file mode 100644
index 00000000000..de7276dbc08
Binary files /dev/null and b/docs/icons/compressed.png differ
diff --git a/docs/icons/continued.png b/docs/icons/continued.png
new file mode 100644
index 00000000000..8f656e27f24
Binary files /dev/null and b/docs/icons/continued.png differ
diff --git a/docs/icons/dir.png b/docs/icons/dir.png
new file mode 100644
index 00000000000..6b97905067e
Binary files /dev/null and b/docs/icons/dir.png differ
diff --git a/docs/icons/down.png b/docs/icons/down.png
new file mode 100644
index 00000000000..be3904b0451
Binary files /dev/null and b/docs/icons/down.png differ
diff --git a/docs/icons/dvi.png b/docs/icons/dvi.png
new file mode 100644
index 00000000000..19c417f227b
Binary files /dev/null and b/docs/icons/dvi.png differ
diff --git a/docs/icons/f.png b/docs/icons/f.png
new file mode 100644
index 00000000000..c946f5b3165
Binary files /dev/null and b/docs/icons/f.png differ
diff --git a/docs/icons/folder.open.png b/docs/icons/folder.open.png
new file mode 100644
index 00000000000..dd2d7e0cc2d
Binary files /dev/null and b/docs/icons/folder.open.png differ
diff --git a/docs/icons/folder.png b/docs/icons/folder.png
new file mode 100644
index 00000000000..6b97905067e
Binary files /dev/null and b/docs/icons/folder.png differ
diff --git a/docs/icons/folder.sec.png b/docs/icons/folder.sec.png
new file mode 100644
index 00000000000..833f59ac517
Binary files /dev/null and b/docs/icons/folder.sec.png differ
diff --git a/docs/icons/forward.png b/docs/icons/forward.png
new file mode 100644
index 00000000000..c5584a4c306
Binary files /dev/null and b/docs/icons/forward.png differ
diff --git a/docs/icons/generic.png b/docs/icons/generic.png
new file mode 100644
index 00000000000..0227cabb5ce
Binary files /dev/null and b/docs/icons/generic.png differ
diff --git a/docs/icons/generic.red.png b/docs/icons/generic.red.png
new file mode 100644
index 00000000000..be63249beb5
Binary files /dev/null and b/docs/icons/generic.red.png differ
diff --git a/docs/icons/generic.sec.png b/docs/icons/generic.sec.png
new file mode 100644
index 00000000000..0bd3d96bdcd
Binary files /dev/null and b/docs/icons/generic.sec.png differ
diff --git a/docs/icons/hand.right.png b/docs/icons/hand.right.png
new file mode 100644
index 00000000000..93035c658ab
Binary files /dev/null and b/docs/icons/hand.right.png differ
diff --git a/docs/icons/hand.up.png b/docs/icons/hand.up.png
new file mode 100644
index 00000000000..1405a6f1562
Binary files /dev/null and b/docs/icons/hand.up.png differ
diff --git a/docs/icons/icon.sheet.png b/docs/icons/icon.sheet.png
new file mode 100644
index 00000000000..b875cb6b1c1
Binary files /dev/null and b/docs/icons/icon.sheet.png differ
diff --git a/docs/icons/image1.png b/docs/icons/image1.png
new file mode 100644
index 00000000000..c1374fde333
Binary files /dev/null and b/docs/icons/image1.png differ
diff --git a/docs/icons/image2.png b/docs/icons/image2.png
new file mode 100644
index 00000000000..606d4fb87e5
Binary files /dev/null and b/docs/icons/image2.png differ
diff --git a/docs/icons/image3.png b/docs/icons/image3.png
new file mode 100644
index 00000000000..701fb1e1359
Binary files /dev/null and b/docs/icons/image3.png differ
diff --git a/docs/icons/index.png b/docs/icons/index.png
new file mode 100644
index 00000000000..9a0de350582
Binary files /dev/null and b/docs/icons/index.png differ
diff --git a/docs/icons/layout.png b/docs/icons/layout.png
new file mode 100644
index 00000000000..0a97c1c475f
Binary files /dev/null and b/docs/icons/layout.png differ
diff --git a/docs/icons/left.png b/docs/icons/left.png
new file mode 100644
index 00000000000..d6e2404a811
Binary files /dev/null and b/docs/icons/left.png differ
diff --git a/docs/icons/link.png b/docs/icons/link.png
new file mode 100644
index 00000000000..4714d0ef40a
Binary files /dev/null and b/docs/icons/link.png differ
diff --git a/docs/icons/movie.png b/docs/icons/movie.png
new file mode 100644
index 00000000000..5615180de88
Binary files /dev/null and b/docs/icons/movie.png differ
diff --git a/docs/icons/p.png b/docs/icons/p.png
new file mode 100644
index 00000000000..3fbe0e8801e
Binary files /dev/null and b/docs/icons/p.png differ
diff --git a/docs/icons/patch.png b/docs/icons/patch.png
new file mode 100644
index 00000000000..808ed7865fe
Binary files /dev/null and b/docs/icons/patch.png differ
diff --git a/docs/icons/pdf.png b/docs/icons/pdf.png
new file mode 100644
index 00000000000..516142bb47b
Binary files /dev/null and b/docs/icons/pdf.png differ
diff --git a/docs/icons/pie0.png b/docs/icons/pie0.png
new file mode 100644
index 00000000000..12e0200c97f
Binary files /dev/null and b/docs/icons/pie0.png differ
diff --git a/docs/icons/pie1.png b/docs/icons/pie1.png
new file mode 100644
index 00000000000..c44c793ed8b
Binary files /dev/null and b/docs/icons/pie1.png differ
diff --git a/docs/icons/pie2.png b/docs/icons/pie2.png
new file mode 100644
index 00000000000..e0b7167d913
Binary files /dev/null and b/docs/icons/pie2.png differ
diff --git a/docs/icons/pie3.png b/docs/icons/pie3.png
new file mode 100644
index 00000000000..820a3c35fa9
Binary files /dev/null and b/docs/icons/pie3.png differ
diff --git a/docs/icons/pie4.png b/docs/icons/pie4.png
new file mode 100644
index 00000000000..35490d857c7
Binary files /dev/null and b/docs/icons/pie4.png differ
diff --git a/docs/icons/pie5.png b/docs/icons/pie5.png
new file mode 100644
index 00000000000..359b7d377f4
Binary files /dev/null and b/docs/icons/pie5.png differ
diff --git a/docs/icons/pie6.png b/docs/icons/pie6.png
new file mode 100644
index 00000000000..4b293eae18c
Binary files /dev/null and b/docs/icons/pie6.png differ
diff --git a/docs/icons/pie7.png b/docs/icons/pie7.png
new file mode 100644
index 00000000000..6bfa2d06ae2
Binary files /dev/null and b/docs/icons/pie7.png differ
diff --git a/docs/icons/pie8.png b/docs/icons/pie8.png
new file mode 100644
index 00000000000..716cf2822bf
Binary files /dev/null and b/docs/icons/pie8.png differ
diff --git a/docs/icons/portal.png b/docs/icons/portal.png
new file mode 100644
index 00000000000..937c0f87cd6
Binary files /dev/null and b/docs/icons/portal.png differ
diff --git a/docs/icons/ps.png b/docs/icons/ps.png
new file mode 100644
index 00000000000..ccccf730b6c
Binary files /dev/null and b/docs/icons/ps.png differ
diff --git a/docs/icons/quill.png b/docs/icons/quill.png
new file mode 100644
index 00000000000..b697770a882
Binary files /dev/null and b/docs/icons/quill.png differ
diff --git a/docs/icons/right.png b/docs/icons/right.png
new file mode 100644
index 00000000000..41f8529a84e
Binary files /dev/null and b/docs/icons/right.png differ
diff --git a/docs/icons/screw1.png b/docs/icons/screw1.png
new file mode 100644
index 00000000000..11673ab97dc
Binary files /dev/null and b/docs/icons/screw1.png differ
diff --git a/docs/icons/screw2.png b/docs/icons/screw2.png
new file mode 100644
index 00000000000..5d7d2cf65e9
Binary files /dev/null and b/docs/icons/screw2.png differ
diff --git a/docs/icons/script.png b/docs/icons/script.png
new file mode 100644
index 00000000000..2520570a775
Binary files /dev/null and b/docs/icons/script.png differ
diff --git a/docs/icons/small/back.png b/docs/icons/small/back.png
new file mode 100644
index 00000000000..2257df2140d
Binary files /dev/null and b/docs/icons/small/back.png differ
diff --git a/docs/icons/small/binary.png b/docs/icons/small/binary.png
new file mode 100644
index 00000000000..2e2e1b073d6
Binary files /dev/null and b/docs/icons/small/binary.png differ
diff --git a/docs/icons/small/binhex.png b/docs/icons/small/binhex.png
new file mode 100644
index 00000000000..9deab419b61
Binary files /dev/null and b/docs/icons/small/binhex.png differ
diff --git a/docs/icons/small/blank.png b/docs/icons/small/blank.png
new file mode 100644
index 00000000000..86f57a504f7
Binary files /dev/null and b/docs/icons/small/blank.png differ
diff --git a/docs/icons/small/broken.png b/docs/icons/small/broken.png
new file mode 100644
index 00000000000..79c998c8c31
Binary files /dev/null and b/docs/icons/small/broken.png differ
diff --git a/docs/icons/small/burst.png b/docs/icons/small/burst.png
new file mode 100644
index 00000000000..2b21436c78e
Binary files /dev/null and b/docs/icons/small/burst.png differ
diff --git a/docs/icons/small/comp1.png b/docs/icons/small/comp1.png
new file mode 100644
index 00000000000..6d8c3459ed0
Binary files /dev/null and b/docs/icons/small/comp1.png differ
diff --git a/docs/icons/small/comp2.png b/docs/icons/small/comp2.png
new file mode 100644
index 00000000000..57f7ad197b8
Binary files /dev/null and b/docs/icons/small/comp2.png differ
diff --git a/docs/icons/small/compressed.png b/docs/icons/small/compressed.png
new file mode 100644
index 00000000000..43acd8b943d
Binary files /dev/null and b/docs/icons/small/compressed.png differ
diff --git a/docs/icons/small/continued.png b/docs/icons/small/continued.png
new file mode 100644
index 00000000000..db17c424650
Binary files /dev/null and b/docs/icons/small/continued.png differ
diff --git a/docs/icons/small/dir.png b/docs/icons/small/dir.png
new file mode 100644
index 00000000000..9bd6256bdbb
Binary files /dev/null and b/docs/icons/small/dir.png differ
diff --git a/docs/icons/small/dir2.png b/docs/icons/small/dir2.png
new file mode 100644
index 00000000000..836daf49ef2
Binary files /dev/null and b/docs/icons/small/dir2.png differ
diff --git a/docs/icons/small/doc.png b/docs/icons/small/doc.png
new file mode 100644
index 00000000000..c560df21d3c
Binary files /dev/null and b/docs/icons/small/doc.png differ
diff --git a/docs/icons/small/forward.png b/docs/icons/small/forward.png
new file mode 100644
index 00000000000..4ddbc61e142
Binary files /dev/null and b/docs/icons/small/forward.png differ
diff --git a/docs/icons/small/generic.png b/docs/icons/small/generic.png
new file mode 100644
index 00000000000..16374a12bbb
Binary files /dev/null and b/docs/icons/small/generic.png differ
diff --git a/docs/icons/small/generic2.png b/docs/icons/small/generic2.png
new file mode 100644
index 00000000000..40d60c1df23
Binary files /dev/null and b/docs/icons/small/generic2.png differ
diff --git a/docs/icons/small/generic3.png b/docs/icons/small/generic3.png
new file mode 100644
index 00000000000..aa38963afa2
Binary files /dev/null and b/docs/icons/small/generic3.png differ
diff --git a/docs/icons/small/image.png b/docs/icons/small/image.png
new file mode 100644
index 00000000000..d92f0a5fcc4
Binary files /dev/null and b/docs/icons/small/image.png differ
diff --git a/docs/icons/small/image2.png b/docs/icons/small/image2.png
new file mode 100644
index 00000000000..4049bda5619
Binary files /dev/null and b/docs/icons/small/image2.png differ
diff --git a/docs/icons/small/index.png b/docs/icons/small/index.png
new file mode 100644
index 00000000000..080453e2151
Binary files /dev/null and b/docs/icons/small/index.png differ
diff --git a/docs/icons/small/key.png b/docs/icons/small/key.png
new file mode 100644
index 00000000000..1a45f67df31
Binary files /dev/null and b/docs/icons/small/key.png differ
diff --git a/docs/icons/small/movie.png b/docs/icons/small/movie.png
new file mode 100644
index 00000000000..7c126042c9a
Binary files /dev/null and b/docs/icons/small/movie.png differ
diff --git a/docs/icons/small/patch.png b/docs/icons/small/patch.png
new file mode 100644
index 00000000000..c39f14435a0
Binary files /dev/null and b/docs/icons/small/patch.png differ
diff --git a/docs/icons/small/ps.png b/docs/icons/small/ps.png
new file mode 100644
index 00000000000..5c604230d07
Binary files /dev/null and b/docs/icons/small/ps.png differ
diff --git a/docs/icons/small/rainbow.png b/docs/icons/small/rainbow.png
new file mode 100644
index 00000000000..175053cb433
Binary files /dev/null and b/docs/icons/small/rainbow.png differ
diff --git a/docs/icons/small/sound.png b/docs/icons/small/sound.png
new file mode 100644
index 00000000000..6e3e95d3d01
Binary files /dev/null and b/docs/icons/small/sound.png differ
diff --git a/docs/icons/small/sound2.png b/docs/icons/small/sound2.png
new file mode 100644
index 00000000000..bc46eb48fe5
Binary files /dev/null and b/docs/icons/small/sound2.png differ
diff --git a/docs/icons/small/tar.png b/docs/icons/small/tar.png
new file mode 100644
index 00000000000..12f0347bf9c
Binary files /dev/null and b/docs/icons/small/tar.png differ
diff --git a/docs/icons/small/text.png b/docs/icons/small/text.png
new file mode 100644
index 00000000000..b4e30f466d3
Binary files /dev/null and b/docs/icons/small/text.png differ
diff --git a/docs/icons/small/transfer.png b/docs/icons/small/transfer.png
new file mode 100644
index 00000000000..324048170a8
Binary files /dev/null and b/docs/icons/small/transfer.png differ
diff --git a/docs/icons/small/unknown.png b/docs/icons/small/unknown.png
new file mode 100644
index 00000000000..cad7e7a7aa0
Binary files /dev/null and b/docs/icons/small/unknown.png differ
diff --git a/docs/icons/small/uu.png b/docs/icons/small/uu.png
new file mode 100644
index 00000000000..ef87c82ee6c
Binary files /dev/null and b/docs/icons/small/uu.png differ
diff --git a/docs/icons/sound1.png b/docs/icons/sound1.png
new file mode 100644
index 00000000000..7a766be6cc8
Binary files /dev/null and b/docs/icons/sound1.png differ
diff --git a/docs/icons/sound2.png b/docs/icons/sound2.png
new file mode 100644
index 00000000000..45112909398
Binary files /dev/null and b/docs/icons/sound2.png differ
diff --git a/docs/icons/sphere1.png b/docs/icons/sphere1.png
new file mode 100644
index 00000000000..2198ae89ec4
Binary files /dev/null and b/docs/icons/sphere1.png differ
diff --git a/docs/icons/sphere2.png b/docs/icons/sphere2.png
new file mode 100644
index 00000000000..257632ba46d
Binary files /dev/null and b/docs/icons/sphere2.png differ
diff --git a/docs/icons/tar.png b/docs/icons/tar.png
new file mode 100644
index 00000000000..6c40521ff80
Binary files /dev/null and b/docs/icons/tar.png differ
diff --git a/docs/icons/tex.png b/docs/icons/tex.png
new file mode 100644
index 00000000000..906622d3844
Binary files /dev/null and b/docs/icons/tex.png differ
diff --git a/docs/icons/text.png b/docs/icons/text.png
new file mode 100644
index 00000000000..34d0edf86e4
Binary files /dev/null and b/docs/icons/text.png differ
diff --git a/docs/icons/transfer.png b/docs/icons/transfer.png
new file mode 100644
index 00000000000..efaf17b682f
Binary files /dev/null and b/docs/icons/transfer.png differ
diff --git a/docs/icons/unknown.png b/docs/icons/unknown.png
new file mode 100644
index 00000000000..7c241c383c0
Binary files /dev/null and b/docs/icons/unknown.png differ
diff --git a/docs/icons/up.png b/docs/icons/up.png
new file mode 100644
index 00000000000..a69ea00c5b7
Binary files /dev/null and b/docs/icons/up.png differ
diff --git a/docs/icons/uu.png b/docs/icons/uu.png
new file mode 100644
index 00000000000..b1d1a8579d5
Binary files /dev/null and b/docs/icons/uu.png differ
diff --git a/docs/icons/uuencoded.png b/docs/icons/uuencoded.png
new file mode 100644
index 00000000000..b1d1a8579d5
Binary files /dev/null and b/docs/icons/uuencoded.png differ
diff --git a/docs/icons/world1.png b/docs/icons/world1.png
new file mode 100644
index 00000000000..3a65c00d846
Binary files /dev/null and b/docs/icons/world1.png differ
diff --git a/docs/icons/world2.png b/docs/icons/world2.png
new file mode 100644
index 00000000000..9f8a3ea4b35
Binary files /dev/null and b/docs/icons/world2.png differ
diff --git a/docs/manual/developer/documenting.html b/docs/manual/developer/documenting.html
new file mode 100644
index 00000000000..8f8163f426e
--- /dev/null
+++ b/docs/manual/developer/documenting.html
@@ -0,0 +1,64 @@
+
+
+
+
Documenting Apache 2.0 + + + + + + +Documentating Apache 2.0
+ +Apache 2.0 uses DoxyGen to document the API's and global variables in the + the code. This will explain the basics of how to document using DoxyGen. + +
To start a documentation block, use /**
+ +
+ To end a documentation block, use */In the middle of the block, there are multiple tags we can use:
++ Description of this functions purpose + @param parameter_name description + + +
The deffunc is not always necessary. DoxyGen does not have a full parser + in it, so any prototype that use a macro in the return type declaration + is too complex for scandoc. Those functions require a deffunc.
+ +An example (using &> rather than >):
++/** + * return the final element of the pathname + * @param pathname The path to get the final element of + * @return the final element of the path + * @tip Examples: + * <pre> + * "/foo/bar/gum" -&> "gum" + * "/foo/bar/gum/" -&> "" + * "gum" -&> "gum" + * "wi\\n32\\stuff" -&> "stuff" + * </pre> + * @deffunc const char * ap_filename_of_pathname(const char *pathname) + */ +
+ +At the top of the header file, always include:
++/** + * @package Name of library header + */ +
+ +ScanDoc uses a new html file for each package. The html files are named + {Name_of_library_header}.html, so try to be concise with your names.
+ + + + diff --git a/docs/manual/developer/request.html b/docs/manual/developer/request.html new file mode 100644 index 00000000000..6becc938a4e --- /dev/null +++ b/docs/manual/developer/request.html @@ -0,0 +1,217 @@ + + + +Request Processing in Apache 2.0 + + + + + + + +Request Processing in Apache 2.0
+ +Warning - this is a first (fast) draft that needs further revision!
+ +Several changes in Apache 2.0 affect the internal request processing + mechanics. Module authors need to be aware of these changes so they + may take advantage of the optimizations and security enhancements.
+ +The first major change is to the subrequest and redirect mechanisms. + There were a number of different code paths in Apache 1.3 to attempt + to optimize subrequest or redirect behavior. As patches were introduced + to 2.0, these optimizations (and the server behavior) were quickly broken + due to this duplication of code. All duplicate code has been folded + back into
+ +ap_process_internal_request()to prevent the + code from falling out of sync again.This means that much of the existing code was 'unoptimized'. It is + the Apache HTTP Project's first goal to create a robust and correct + implementation of the HTTP server RFC. Additional goals include + security, scalability and optimization. New methods were sought to + optimize the server (beyond the performance of Apache 1.3) without + introducing fragile or insecure code.
+ +The Request Processing Cycle
+ +All requests pass through
+ +ap_process_request_internal()+ in request.c, including subrequests and redirects. If a module doesn't + pass generated requests through this code, the author is cautioned that + the module may be broken by future changes to request processing.To streamline requests, the module author can take advantage of the + hooks offered to drop out of the request cycle early, or to bypass + core Apache hooks which are irrelevant (and costly in terms of CPU.)
+ +The Request Parsing Phase + +
Unescapes the URL
+ +The request's parsed_uri path is unescaped, once and only once, at the + beginning of internal request processing.
+ +This step is bypassed if the proxyreq flag is set, or the parsed_uri.path + element is unset. The module has no further control of this one-time + unescape operation, either failing to unescape or multiply unescaping + the URL leads to security reprecussions.
+ +Strips Parent and This Elements from the URI
+ +All
+ +/../and/./elements are removed by +ap_getparents(). This helps to ensure the path is (nearly) + absolute before the request processing continues.This step cannot be bypassed.
+ +Initial URI Location Walk
+ +Every request is subject to an
+ +ap_location_walk()call. + This ensures that <Location > sections are consistently enforced for + all requests. If the request is an internal redirect or a sub-request, + it may borrow some or all of the processing from the previous or parent + request's ap_location_walk, so this step is generally very efficient + after processing the main request.Hook: translate_name
+ +Modules can determine the file name, or alter the given URI in this step. + For example, mod_vhost_alias will translate the URI's path into the + configured virtual host, mod_alias will translate the path to an alias + path, and if the request falls back on the core, the DocumentRoot is + prepended to the request resource. + +
If all modules DECLINE this phase, an error 500 is returned to the browser, + and a "couldn't translate name" error is logged automatically.
+ +Hook: map_to_storage
+ +After the file or correct URI was determined, the appropriate per-dir + configurations are merged together. For example, mod_proxy compares + and merges the appropriate <Proxy > sections. If the URI is nothing + more than a local (non-proxy) TRACE request, the core handles the + request and returns DONE. If no module answers this hook with OK or + DONE, the core will run the request filename against the <Directory > + and <Files > sections. If the request 'filename' isn't an absolute, + legal filename, a note is set for later termination.
+ +Initial URI Location Walk
+ +Every request is hardened by a second
+ +ap_location_walk()+ call. This reassures that a translated request is still subjected to + the configured <Location > sections. The request again borrows + some or all of the processing from it's previous location_walk above, + so this step is almost always very efficient unless the translated URI + mapped to a substantially different path or Virtual Host.Hook: header_parser
+ +The main request then parses the client's headers. This prepares +the remaining request processing steps to better serve the client's +request.
+ +The Security Phase + +
Needs Documentation. Code is;
++ switch (ap_satisfies(r)) { + case SATISFY_ALL: + case SATISFY_NOSPEC: + if ((access_status = ap_run_access_checker(r)) != 0) { + return decl_die(access_status, "check access", r); + } + if (ap_some_auth_required(r)) { + if (((access_status = ap_run_check_user_id(r)) != 0) || !ap_auth_type(r)) { + return decl_die(access_status, ap_auth_type(r) + ? "check user. No user file?" + : "perform authentication. AuthType not set!", r); + } + if (((access_status = ap_run_auth_checker(r)) != 0) || !ap_auth_type(r)) { + return decl_die(access_status, ap_auth_type(r) + ? "check access. No groups file?" + : "perform authentication. AuthType not set!", r); + } + } + break; + case SATISFY_ANY: + if (((access_status = ap_run_access_checker(r)) != 0) || !ap_auth_type(r)) { + if (!ap_some_auth_required(r)) { + return decl_die(access_status, ap_auth_type(r) + ? "check access" + : "perform authentication. AuthType not set!", r); + } + if (((access_status = ap_run_check_user_id(r)) != 0) || !ap_auth_type(r)) { + return decl_die(access_status, ap_auth_type(r) + ? "check user. No user file?" + : "perform authentication. AuthType not set!", r); + } + if (((access_status = ap_run_auth_checker(r)) != 0) || !ap_auth_type(r)) { + return decl_die(access_status, ap_auth_type(r) + ? "check access. No groups file?" + : "perform authentication. AuthType not set!", r); + } + } + break; + } ++The Preparation Phase
+ +Hook: type_checker
+ +The modules have an opportunity to test the URI or filename against + the target resource, and set mime information for the request. Both + mod_mime and mod_mime_magic use this phase to compare the file name + or contents against the administrator's configuration and set the + content type, language, character set and request handler. Some + modules may set up their filters or other request handling parameters + at this time.
+ +If all modules DECLINE this phase, an error 500 is returned to the browser, + and a "couldn't find types" error is logged automatically.
+ +Hook: fixups
+ +Many modules are 'trounced' by some phase above. The fixups phase is + used by modules to 'reassert' their ownership or force the request's + fields to their appropriate values. It isn't always the cleanest + mechanism, but occasionally it's the only option.
+ +Hook: insert_filter
+ +Modules that transform the content in some way can insert their values + and override existing filters, such that if the user configured a more + advanced filter out-of-order, then the module can move it's order as + need be. + +
The Handler Phase
+ +This phase is not part of the processing in +
+ +ap_process_request_internal(). Many modules prepare one + or more subrequests prior to creating any content at all. After the + core, or a module callsap_process_request_internal()it + then callsap_invoke_handler()to generate the request.Hook: handler
+ +The module finally has a chance to serve the request in it's handler + hook. Note that not every prepared request is sent to the handler + hook. Many modules, such as mod_autoindex, will create subrequests + for a given URI, and then never serve the subrequest, but simply + lists it for the user. Remember not to put required teardown from + the hooks above into this module, but register pool cleanups against + the request pool to free resources as required.
+ + + + + + + + + + diff --git a/docs/manual/faq/index.html b/docs/manual/faq/index.html new file mode 100644 index 00000000000..90c19b7bb96 --- /dev/null +++ b/docs/manual/faq/index.html @@ -0,0 +1,67 @@ + + + + + + + + +Apache Server Frequently Asked Questions + + + +Frequently Asked Questions
+ ++ The latest version of this FAQ is always available from the main + Apache web site, at <http://httpd.apache.org/docs-2.0/faq/>. + In addition, you can view this FAQ all in one page for easy searching and + printing. +
+ +Since Apache 2.0 is very new, we don't yet know what the + Frequently Asked Questions will be. While this section + fills up, you should also consult the Apache 1.3 FAQ + to see if your question is answered there.
+ + + +Categories
+ + + +-
+
+
- Support +
- What do I do when I have problems? + +
-
+
+
- Support +
- What do I do when I have problems? + +
+ + + + + + + + diff --git a/docs/manual/faq/support.html b/docs/manual/faq/support.html new file mode 100644 index 00000000000..95aa420132c --- /dev/null +++ b/docs/manual/faq/support.html @@ -0,0 +1,143 @@ + + + + +Support - Apache Server Frequently Asked Questions + + + + +Apache Server Frequently Asked Questions
+ + +Support
+ +-
+
- "Why can't I ...? Why won't ... + work?" What to do in case of problems + +
- Whom do I contact for support? + + +
+ +"Why can't I ...? Why won't ... work?" + What to do in case of problems
++ If you are having trouble with your Apache server software, you should + take the following steps: +
+-
+
- Check the errorlog!
+
+ Apache tries to be helpful when it encounters a problem. In many + cases, it will provide some details by writing one or messages to + the server error log. Sometimes this is enough for you to diagnose + & fix the problem yourself (such as file permissions or the like). + The default location of the error log is + /usr/local/apache/logs/error_log, but see the + ErrorLog + directive in your config files for the location on your server. +
+
+ - Check the
+ FAQ!
+
+ The latest version of the Apache Frequently-Asked Questions list can + always be found at the main Apache web site. +
+
+ - Check the Apache bug database
+
+ Most problems that get reported to The Apache Group are recorded in + the + bug database. + Please check the existing reports, open + and closed, before adding one. If you find + that your issue has already been reported, please don't add + a "me, too" report. If the original report isn't closed + yet, we suggest that you check it periodically. You might also + consider contacting the original submitter, because there may be an + email exchange going on about the issue that isn't getting recorded + in the database. +
+
+ - Ask in the comp.infosystems.www.servers.unix
+ or comp.infosystems.www.servers.ms-windows USENET
+ newsgroup (as appropriate for the platform you use).
+
+ A lot of common problems never make it to the bug database because + there's already high Q&A traffic about them in the + comp.infosystems.www.servers.unix + newsgroup. Many Apache users, and some of the developers, can be + found roaming its virtual halls, so it is suggested that you seek + wisdom there. The chances are good that you'll get a faster answer + there than from the bug database, even if you don't see + your question already posted. +
+
+ - If all else fails, report the problem in the bug
+ database
+
+ If you've gone through those steps above that are appropriate and + have obtained no relief, then please do let The Apache + Group know about the problem by + logging a bug report. +
++ If your problem involves the server crashing and generating a core + dump, please include a backtrace (if possible). As an example, +
++
-
+
# cd ServerRoot+
+ # dbx httpd core
+ (dbx) where
+
+ (Substitute the appropriate locations for your + ServerRoot and your httpd and + core files. You may have to use
+gdb+ instead ofdbx.) +
+
+ +Whom do I contact for support?
++ There is no official support for Apache. None of the developers want to + be swamped by a flood of trivial questions that can be resolved elsewhere. + Bug reports and suggestions should be sent via + the bug report page. + Other questions should be directed to the + comp.infosystems.www.servers.unix or comp.infosystems.www.servers.ms-windows + newsgroup (as appropriate for the platform you use), where some of the + Apache team lurk, in the company of many other httpd gurus who + should be able to help. +
++ Commercial support for Apache is, however, available from a number + of third parties. +
+ + + + + + + diff --git a/docs/manual/howto/auth.html b/docs/manual/howto/auth.html new file mode 100644 index 00000000000..9311ffcf814 --- /dev/null +++ b/docs/manual/howto/auth.html @@ -0,0 +1,318 @@ + + + + + + +Authentication + + + + + + + +Authentication
+ + + +-
+
- Introduction + +
- The prerequisites + +
- Getting it + working. + +
- Letting more + than one person in + +
- Possible problems + +
- What other neat + stuff can I do? + +
- More information +
+ ++
+ + ++ +Related Modules +
+
+ mod_auth
+Related Directives +
+
+ Allow
+ AuthGroupFile
+ AuthName
+ AuthType
+ AuthUserFile
+ Deny
+ Options
+ Require
+ +Authentication
+ +Authentication is any process by which you verify that + someone is who they claim they are. Authorization is any + process by which someone is allowed to be where they want to + go, or to have information that they want to have.
+ +Introduction
+ +If you have information on your web site that is sensitive + or intended for only a small group of people, the techniques in + this article will help you make sure that the people that see + those pages are the people that you wanted to see them.
+ +This article covers the "standard" way of protecting parts of your + web site that most of you are going to use.
+ +The prerequisites
+ +The directives discussed in this article will need to go either + in your main server configuration file, or in per-directory + configuration files (
+ +.htaccessfiles).If you plan to use
+ +.htaccessfiles, you will need to + have a server configuration that permits putting authentication + directives in these files. This is done with the +AllowOverride+ directive, which specifies which directives, if any, may be put in + per-directory configuration files.Since we're talking here about authentication, you will need an +
+ +AllowOverridedirective like the following:+ AllowOverride AuthConfig +
+ +Or, if you are just going to put the directives directly in your + main server configuration file, you will of course need to have + write permission to that file.
+ +And you'll need to know a little bit about the directory + structure of your server, in order to know where some files are + kept. This should not be terribly difficult, and I'll try to + make this clear when we come to that point.
+ +Getting it working.
+ +Here's the basics of password protecting a directory on your + server.
+ +You'll need to create a password file. This file should be + placed somewhere outside of your document directory. This is so + that folks cannot download the password file. For example, if + your documents are served out of +
+ +/usr/local/apache/htdocsyou might want to put the + password file(s) in/usr/local/apache/passwd.To create the file, use the
+htpasswdutility + that came with Apache. This be located in thebin+ directory of wherever you installed Apache. To create the file, + type:+ htpasswd -c /usr/local/apache/passwd/password rbowen +
+ +
+htpasswdwill ask you for the password, and + then ask you to type it again to confirm it:+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen + New password: mypassword + Re-type new password: mypassword + Adding password for user rbowen +
+ +If
+ +htpasswdis not in your path, of course + you'll have to type the full path to the file to get it to run. + On my server, it's located at +/usr/local/apache/bin/htpasswdNext, you'll need to create a file in the directory you want + to protect. This file is usually called
+.htaccess, + although on Windows it's calledhtaccess(without + the leading period.).htaccessneeds to contain + the following lines:+ AuthType Basic + AuthName "By Invitation Only" + AuthUserFile /usr/local/apache/passwd/passwords + AuthGroupFile /dev/null + require user rbowen +
+ +The next time that you load a file from that directory, you + should see the familiar username/password dialog box pop up. If + you don't chances are pretty good that you are not permitted to + use
+ +.htaccessfiles in the directory in + question.Letting more than + one person in
+ +The directives above only let one person (specifically + someone with a username of
+ +rbowen) into the + directory. In most cases, you'll want to let more than one + person in. This is where theAuthGroupFilecomes + in. In the example above, we've pointed +AuthGroupFileto/dev/null, which is + Unix-speak for "nowhere", or "off into space." (The Windows + NT equivalent of this isnul.)If you want to let more than one person in, you'll need to + create a group file that associates group names with a list of + users in that group. The format of this file is pretty simple, + and you can create it with your favorite editor. The contents + of the file will look like this:
++ GroupName: rbowen dpitts sungo rshersey +
+ +That's just a list of the members of the group in a long + line separated by spaces.
+ +To add a user to your already existing password file, + type:
++ htpasswd /usr/local/apache/passwd/password dpitts +
+ +You'll get the same response as before, but it will be + appended to the existing file, rather than creating a new file. + (It's the
+ +-cthat makes it create a new password + file.Now, you need to modify your
+.htaccessfile to + look like the following:+ AuthType Basic + AuthName "By Invitation Only" + AuthUserFile /usr/local/apache/passwd/passwords + AuthGroupFile /usr/local/apache/passwd/groups + require group GroupName +
+ +Now, anyone that is listed in the group +
+ +GroupName, and has an entry in the +passwordfile, will be let in, if they type the + correct password.There's another way to let multiple users in that is less + specific. Rather than creating a group file, you can just use + the following directive:
++ require valid-user +
+ +Using that rather than the
+ +require user rbowen+ line will allow anyone in that is listed in the password file, + and who correctly enters their password. You can even emulate + the group behavior here, by just keeping a separate password + file for each group. The advantage of this approach is that + Apache only has to check one file, rather than two. The + disadvantage is that you have to maintain a bunch of password + files, and remember to reference th right one in the +AuthUserFiledirective.Possible problems
+ +Because of the way that Basic authentication is specified, + your username and password must be verified every time you + request a document from the server. This is even if you're + reloading the same page, and for every image on the page (if + they come from a protected directory). As you can imagine, this + slows things down a little. The amount that it slows things + down is proportional to the size of the password file, because + it has to open up that file, and go down the list of users + until it gets to your name. And it has to do this every time a + page is loaded.
+ +A consequence of this is that there's a practical limit to how many + users you can put in one password file. This limit will vary + depending on the performance of your particular server machine, but + you can expect to see slowdowns once you get above a few hundred + entries, and may wish to consider a different authentication method + at that time.
+ +What other neat + stuff can I do?
+ +Authentication by username and password is only part of the + story. Frequently you want to let people in based on something + other than who they are. Something such as where they are + coming from.
+ +The
+ +allowanddenydirectives let + you allow and deny access based on the host name, or host + address, of the machine requesting a document. The directive + goes hand-in-hand with these is theorder+ directive, which tells Apache in which order to apply the + filters.The usage of these directives is:
++ allow from address +
+ +where address is an IP address (or a partial IP + address) or a fully qualified domain name (or a partial domain + name).
+ +For example, if you have someone spamming your message + board, and you want to keep them out, you could do the + following:
++ deny from 205.252.46.165 +
+ +Visitors coming from that address will not be able to see + the content behind this directive. If, instead, you have a + machine name, rather than an IP address, you can use that.
++ deny from host.example.com +
+ +And, if you'd like to block access from an entire domain, + you can specify just part of an address or domain name:
++ deny from 192.101.205 + deny from cyberthugs.com + deny from ke +
+ +Using
+orderwill let you be sure that you are + actually restricting things to the group that you want to let + in, by combining adenyand anallow+ directive:+ order deny,allow + deny from all + allow from dev.example.com +
+ +Listing just the
+ +allowdirective would not do + what you want, because it will let folks from that host in, in + addition to letting everyone in. What you want is to let + only those folks in.More information
+ +You should also read the documentation for +
+ + + diff --git a/docs/manual/howto/auth.html.en b/docs/manual/howto/auth.html.en new file mode 100644 index 00000000000..9311ffcf814 --- /dev/null +++ b/docs/manual/howto/auth.html.en @@ -0,0 +1,318 @@ + + + + + + +mod_auth+ which contains + some more information about how this all works.Authentication + + + + + + + +Authentication
+ + + +-
+
- Introduction + +
- The prerequisites + +
- Getting it + working. + +
- Letting more + than one person in + +
- Possible problems + +
- What other neat + stuff can I do? + +
- More information +
+ ++
+ + ++ +Related Modules +
+
+ mod_auth
+Related Directives +
+
+ Allow
+ AuthGroupFile
+ AuthName
+ AuthType
+ AuthUserFile
+ Deny
+ Options
+ Require
+ +Authentication
+ +Authentication is any process by which you verify that + someone is who they claim they are. Authorization is any + process by which someone is allowed to be where they want to + go, or to have information that they want to have.
+ +Introduction
+ +If you have information on your web site that is sensitive + or intended for only a small group of people, the techniques in + this article will help you make sure that the people that see + those pages are the people that you wanted to see them.
+ +This article covers the "standard" way of protecting parts of your + web site that most of you are going to use.
+ +The prerequisites
+ +The directives discussed in this article will need to go either + in your main server configuration file, or in per-directory + configuration files (
+ +.htaccessfiles).If you plan to use
+ +.htaccessfiles, you will need to + have a server configuration that permits putting authentication + directives in these files. This is done with the +AllowOverride+ directive, which specifies which directives, if any, may be put in + per-directory configuration files.Since we're talking here about authentication, you will need an +
+ +AllowOverridedirective like the following:+ AllowOverride AuthConfig +
+ +Or, if you are just going to put the directives directly in your + main server configuration file, you will of course need to have + write permission to that file.
+ +And you'll need to know a little bit about the directory + structure of your server, in order to know where some files are + kept. This should not be terribly difficult, and I'll try to + make this clear when we come to that point.
+ +Getting it working.
+ +Here's the basics of password protecting a directory on your + server.
+ +You'll need to create a password file. This file should be + placed somewhere outside of your document directory. This is so + that folks cannot download the password file. For example, if + your documents are served out of +
+ +/usr/local/apache/htdocsyou might want to put the + password file(s) in/usr/local/apache/passwd.To create the file, use the
+htpasswdutility + that came with Apache. This be located in thebin+ directory of wherever you installed Apache. To create the file, + type:+ htpasswd -c /usr/local/apache/passwd/password rbowen +
+ +
+htpasswdwill ask you for the password, and + then ask you to type it again to confirm it:+ # htpasswd -c /usr/local/apache/passwd/passwords rbowen + New password: mypassword + Re-type new password: mypassword + Adding password for user rbowen +
+ +If
+ +htpasswdis not in your path, of course + you'll have to type the full path to the file to get it to run. + On my server, it's located at +/usr/local/apache/bin/htpasswdNext, you'll need to create a file in the directory you want + to protect. This file is usually called
+.htaccess, + although on Windows it's calledhtaccess(without + the leading period.).htaccessneeds to contain + the following lines:+ AuthType Basic + AuthName "By Invitation Only" + AuthUserFile /usr/local/apache/passwd/passwords + AuthGroupFile /dev/null + require user rbowen +
+ +The next time that you load a file from that directory, you + should see the familiar username/password dialog box pop up. If + you don't chances are pretty good that you are not permitted to + use
+ +.htaccessfiles in the directory in + question.Letting more than + one person in
+ +The directives above only let one person (specifically + someone with a username of
+ +rbowen) into the + directory. In most cases, you'll want to let more than one + person in. This is where theAuthGroupFilecomes + in. In the example above, we've pointed +AuthGroupFileto/dev/null, which is + Unix-speak for "nowhere", or "off into space." (The Windows + NT equivalent of this isnul.)If you want to let more than one person in, you'll need to + create a group file that associates group names with a list of + users in that group. The format of this file is pretty simple, + and you can create it with your favorite editor. The contents + of the file will look like this:
++ GroupName: rbowen dpitts sungo rshersey +
+ +That's just a list of the members of the group in a long + line separated by spaces.
+ +To add a user to your already existing password file, + type:
++ htpasswd /usr/local/apache/passwd/password dpitts +
+ +You'll get the same response as before, but it will be + appended to the existing file, rather than creating a new file. + (It's the
+ +-cthat makes it create a new password + file.Now, you need to modify your
+.htaccessfile to + look like the following:+ AuthType Basic + AuthName "By Invitation Only" + AuthUserFile /usr/local/apache/passwd/passwords + AuthGroupFile /usr/local/apache/passwd/groups + require group GroupName +
+ +Now, anyone that is listed in the group +
+ +GroupName, and has an entry in the +passwordfile, will be let in, if they type the + correct password.There's another way to let multiple users in that is less + specific. Rather than creating a group file, you can just use + the following directive:
++ require valid-user +
+ +Using that rather than the
+ +require user rbowen+ line will allow anyone in that is listed in the password file, + and who correctly enters their password. You can even emulate + the group behavior here, by just keeping a separate password + file for each group. The advantage of this approach is that + Apache only has to check one file, rather than two. The + disadvantage is that you have to maintain a bunch of password + files, and remember to reference th right one in the +AuthUserFiledirective.Possible problems
+ +Because of the way that Basic authentication is specified, + your username and password must be verified every time you + request a document from the server. This is even if you're + reloading the same page, and for every image on the page (if + they come from a protected directory). As you can imagine, this + slows things down a little. The amount that it slows things + down is proportional to the size of the password file, because + it has to open up that file, and go down the list of users + until it gets to your name. And it has to do this every time a + page is loaded.
+ +A consequence of this is that there's a practical limit to how many + users you can put in one password file. This limit will vary + depending on the performance of your particular server machine, but + you can expect to see slowdowns once you get above a few hundred + entries, and may wish to consider a different authentication method + at that time.
+ +What other neat + stuff can I do?
+ +Authentication by username and password is only part of the + story. Frequently you want to let people in based on something + other than who they are. Something such as where they are + coming from.
+ +The
+ +allowanddenydirectives let + you allow and deny access based on the host name, or host + address, of the machine requesting a document. The directive + goes hand-in-hand with these is theorder+ directive, which tells Apache in which order to apply the + filters.The usage of these directives is:
++ allow from address +
+ +where address is an IP address (or a partial IP + address) or a fully qualified domain name (or a partial domain + name).
+ +For example, if you have someone spamming your message + board, and you want to keep them out, you could do the + following:
++ deny from 205.252.46.165 +
+ +Visitors coming from that address will not be able to see + the content behind this directive. If, instead, you have a + machine name, rather than an IP address, you can use that.
++ deny from host.example.com +
+ +And, if you'd like to block access from an entire domain, + you can specify just part of an address or domain name:
++ deny from 192.101.205 + deny from cyberthugs.com + deny from ke +
+ +Using
+orderwill let you be sure that you are + actually restricting things to the group that you want to let + in, by combining adenyand anallow+ directive:+ order deny,allow + deny from all + allow from dev.example.com +
+ +Listing just the
+ +allowdirective would not do + what you want, because it will let folks from that host in, in + addition to letting everyone in. What you want is to let + only those folks in.More information
+ +You should also read the documentation for +
+ + + diff --git a/docs/manual/images/custom_errordocs.png b/docs/manual/images/custom_errordocs.png new file mode 100644 index 00000000000..11553cbdeec Binary files /dev/null and b/docs/manual/images/custom_errordocs.png differ diff --git a/docs/manual/images/mod_rewrite_fig1.png b/docs/manual/images/mod_rewrite_fig1.png new file mode 100644 index 00000000000..f3a68d9e4c5 Binary files /dev/null and b/docs/manual/images/mod_rewrite_fig1.png differ diff --git a/docs/manual/images/mod_rewrite_fig2.png b/docs/manual/images/mod_rewrite_fig2.png new file mode 100644 index 00000000000..bc141be7694 Binary files /dev/null and b/docs/manual/images/mod_rewrite_fig2.png differ diff --git a/docs/manual/logs.html b/docs/manual/logs.html new file mode 100644 index 00000000000..d3ebf480c58 --- /dev/null +++ b/docs/manual/logs.html @@ -0,0 +1,580 @@ + + + +mod_auth+ which contains + some more information about how this all works.Log Files - Apache HTTP Server + + + + + +Log Files
+ +In order to effectively manage a web server, it is necessary to get +feedback about the activity and performance of the server as well as +any problems that may be occuring. The Apache HTTP Server provides +very comprehensive and flexible logging capabilities. This document +describes how to configure the various log files, and how to +understand what the logs contain.
+ +-
+
- Security Warning +
- Error Log +
- Access Log + +
- Log Rotation +
- Piped Logs +
- VirtualHosts +
- Other Log Files
+
-
+
- PID File +
- Script Log +
- Rewrite Log +
+
+ +Security Warning
+ +Anyone who can write to the directory where Apache is writing a +log file can almost certainly gain access to the uid that the server is +started as, which is normally root. Do NOT give people write +access to the directory the logs are stored in without being aware of +the consequences; see the security tips +document for details.
+ +In addition, log files may contain information supplied directly +by the client, without escaping. Therefore, it is possible for +malicious clients to insert control-characters in the log files, so +care must be taken in dealing with raw logs.
+ +
+ +Error Log
+ ++
+ ++Related Directives
+ +ErrorLog
+LogLevel +The server error log, whose name and location is set by the ErrorLog directive, is the most +important log file. This is the place where Apache HTTPD will send +diagnostic information and record any errors that it encounters in +processing requests. It is the first place to look when a problem +occurs with starting the server or with the operation of the server, +since it will often contain details of what went wrong and how to fix +it.
+ +The error log is usually written to a file (typically +
+ +error_logon unix systems anderror.logon +Windows and OS/2). On unix systems it is also possible to have the +server send errors to thesyslogor pipe +them through a program.The format of the error log is relatively free-form and +descriptive. But there is certain information that is contained +in most error log entries. For example, here is a typical message.
+ +
+ ++[Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1] client denied by server configuration: /export/home/live/ap/htdocs/test +The first item in the log entry is the date and time of the +message. The second entry lists the severity of the error being +reported. The LogLevel directive +is used to control the types of errors that are sent to the error log +by restricting the severity level. The third entry gives the IP +address of the client that generated the error. Beyond that is the +message itself, which in this case indicates that the server has been +configured to deny the client access. The server reports the +file-system path (as opposed to the web path) of the requested +document.
+ +A very wide variety of different messages can appear in the error +log. Most look similar to the example above. The error log will also +contain debugging output from CGI scripts. Any information written to +
+ +stderrby a CGI script will be copied directly to the +error log.It is not possible to customize the error log by adding or removing +information. However, error log entries dealing with particular +requests have corresponding entries in the access +log. For example, the above example entry corresponds to an +access log entry with status code 403. Since it is possible to +customize the access log, you can obtain more information about error +conditions using that log file.
+ +During testing, it is often useful to continuously monitor the +error log for any problems. On unix systems, you can accomplish this +using:
+
+ ++tail -f error_log +
+ +Access Log
+ +
+ ++Related Modules
+ +mod_log_config
+ ++Related Directives
+ +CustomLog
+LogFormat
+SetEnvIf + +The server access log records all requests processed by the server. +The location of the access log as well as its contents are controlled +by the CustomLog +directive. The LogFormat directive can +be used to simplify the selection of the contents of the logs. +This section describes how to configure the server to record +information in the access log.
+ +Of course, storing the information in the access log is only the +start of log management. The next step is to analyze this information +to produce useful statistics. Log analysis in general is beyond the +scope of this document, and not really part of the job of the +web server itself. For more information about this topic, and for +applications which perform log analysis, check the Open Directory or Yahoo.
+ +Various versions of Apache HTTPD have used other modules and +directives to control access logging, including mod_log_referer, +mod_log_agent, and the
+ +TransferLogdirective. The +CustomLogdirective now subsumes the functionality of all +the older directives.The format of the access log is highly configurable. The format is +specified using a format +string that looks much like a C-style printf(1) format string. +Some examples are presented in the next sections. For a complete list +of the possible contents of the format string, see the mod_log_config documentation.
+ +Common Log Format
+ +A typical configuration for the access log might look +as follows.
+ +
+ ++LogFormat "%h %l %u %t \"%r\" %>s %b" common
+CustomLog logs/access_log common +This defines the nickname
+ +commonand +associates it with a particular log format string. The format string +consists of percent directives, each of which tell the server to log a +particular piece of information. Literal characters may also be +placed in the format string and will be copied directly into the log +output. The quote character (") must be escaped by +placing a back-slash before it to prevent it from being interpreted as +the end of the format string. The format string may also contain the +special control characters "\n" for new-line and +"\t" for tab.The
+ +CustomLogdirective sets up a new log file using +the defined nickname. The filename for the access log is +relative to the ServerRoot +unless it begins with a slash.The above configuration will write log entries in a format known as +the Common Log Format (CLF). This standard format can be produced by +many different web servers and read by many log analysis programs. +The log file entries produced in CLF will look something like +this:
+ +
+ ++127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 +Each part of this log entry is described below.
+ +-
+
127.0.0.1(%h)- This is the IP
+address of the client (remote host) which made the request to the
+server. If HostNameLookups is set to
+
On, then the server will try to determine the hostname +and log it in place of the IP address. However, this configuration is +not recommended since it can significantly slow the server. Instead, +it is best to use a log post-processor such as logresolve to determine the +hostnames. The IP address reported here is not necessarily the +address of the machine at which the user is sitting. If a proxy +server exists between the user and the server, this address will be +the address of the proxy, rather than the originating machine.
+
+ -(%l)- The "hyphen" in the
+output indicates that the requested piece of information is not
+available. In this case, the information that is not available is the
+RFC 1413 identity of the client determined by
identdon +the clients machine. This information is highly unreliable and should +almost never be used except on tightly controlled internal networks. +Apache HTTPD will not even attempt to determine this information +unless IdentityCheck is set +toOn.
+
+ frank(%u)- This is the userid
+of the person requesting the document as determined by HTTP
+authentication. The same value is typically provided to CGI scripts
+in the
REMOTE_USERenvironment variable. If the status +code for the request (see below) is 401, then this value should not be +trusted because the user is not yet authenticated. If the document is +not password protected, this entry will be "-" just like +the previous one.
+
+ [10/Oct/2000:13:55:36 -0700](%t)
+- The time that the server finished processing the request. The
+format is:
+
+It is possible to have the time displayed in another format +by specifying[day/month/year:hour:minute:second zone]
+day = 2*digit
+month = 3*letter
+year = 4*digit
+hour = 2*digit
+minute = 2*digit
+second = 2*digit
+zone = (`+' | `-') 4*digit%{format}tin the log format string, where +formatis as instrftime(3)from the C +standard library. +
+
+ "GET /apache_pb.gif HTTP/1.0"+(\"%r\")- The request line from the client is
+given in double quotes. The request line contains a great deal of
+useful information. First, the method used by the client is
+
GET. Second, the client requested the resource +/apache_pb.gif, and third, the client used the protocol +HTTP/1.0. It is also possible to log one or more
+parts of the request line independently. For example, the format
+string "
%m %U%q %H" will log the method, path, +query-string, and protocol, resulting in exactly the same output as +"%r".
+
+ 200 (- This is the status +code that the server sends back to the client. This information is +very valuable, because it reveals whether the request resulted in a +successful response (codes beginning in 2), a redirection (codes +beginning in 3), an error caused by the client (codes beginning in 4), +or an error in the server (codes beginning in 5). +The full list of possible status codes can be +found in the HTTP specification (RFC2616 section 10). + +
2326(%b) +- The last entry indicates the size of the object returned to
+the client, not including the response headers. If no content
+was returned to the client, this value will be "
-". +To log "0" for no content, use%B+instead.
+
+
%>s)Combined Log Format
+ +Another commonly used format string is called the +Combined Log Format. It can be used as follows.
+ +
+ ++LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined
+CustomLog log/acces_log combined +This format is exactly the same as the Common Log Format, +with the addition of two more fields. The access log under this +format will look like:
+ +
+ ++127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 "http://www.example.com/start.html" "Mozilla/4.08 [en] (Win98; I ;Nav)" +The additional fields are:
+ +-
+
+
"http://www.example.com/start.html"+(\"%{Referer}i\")- The "Referer" (sic) HTTP
+request header. This gives the site that the client reports having
+been referred from. (This should be the page that links to or includes
+
/apache_pb.gif). + + "Mozilla/4.08 [en] (Win98; I ;Nav)"+(\"%{User-agent}i\")- The User-Agent HTTP request +header. This is the identifying information that the client browser +reports about itself. + +
Multiple Access Logs
+ +Multiple access logs can be created simply by specifying multiple +
+ +CustomLogdirectives in the configuration file. For +example, the following directives will create three access logs. The +first contains the basic CLF information, while the second and third +contain referer and browser information. The last two +CustomLoglines show how to mimic the effects of the +ReferLogandAgentLogdirectives.
+ ++LogFormat "%h %l %u %t \"%r\" %>s %b" common
+CustomLog logs/access_log common
+CustomLog logs/referer_log "%{Referer}i -> %U"
+CustomLog logs/agent_log "%{User-agent}i" +This example also shows that it is not necessary to define a +nickname with the
+ +LogFormatdirective. Instead, the log +format can be specified directly in theCustomLog+directive.Conditional Logging
+ +There are times when it is convenient to exclude certain entries +from the access logs based on characteristics of the client request. +This is easily accomplished with the help of environment variables. First, an environment +variable must be set to indicate that the request meets certain +conditions. This is usually accomplished with SetEnvIf. Then the +
+ +env=clause of theCustomLogdirective is +used to include or exclude requests where the environment variable is +set. Some examples:
+ ++# Mark requests from the loop-back interface
+SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog
+# Mark requests for the robots.txt file
+SetEnvIf Request_URI "^/robots\.txt$" dontlog
+# Log what remains
+CustomLog logs/access_log common env=!dontlog +As another example, consider logging requests from english-speakers +to one log file, and non-english speakers to a different log file.
+ +
+ ++SetEnvIf Accept-Language "en" english
+CustomLog logs/english_log common env=english
+CustomLog logs/non_english_log common env=!english +Although we have just shown that conditional logging is very +powerful and flexibly, it is not the only way to control the contents +of the logs. Log files are more useful when they contain a complete +record of server activity. It is often easier to simply post-process +the log files to remove requests that you do not want to consider.
+ +
+ +Log Rotation
+ +On even a moderately busy server, the quantity of information +stored in the log files is very large. The access log file typically +grows 1 MB or more per 10,000 requests. It will consequently be +necessary to periodically rotate the log files by moving or deleting +the existing logs. This cannot be done while the server is running, +because Apache will continue writing to the old log file as long as it +holds the file open. Instead, the server must be restarted after the log files are moved or +deleted so that it will open new log files.
+ +By using a graceful restart, the server can be instructed +to open new log files without losing any existing or pending +connections from clients. However, in order to accomplish this, the +server must continue to write to the old log files while it finishes +serving old requests. It is therefore necessary to wait for some time +after the restart before doing any processing on the log files. A +typical scenario that simply rotates the logs and compresses the old +logs to save space is:
+ +
+ ++mv access_log access_log.old
+mv error_log error_log.old
+apachectl graceful
+sleep 600
+gzip access_log.old error_log.old +Another way to perform log rotation is using piped +logs as discussed in the next section.
+ +
+ +Piped Logs
+ +Apache HTTPD is capable of writing error and access log files +through a pipe to another process, rather than directly to a file. +This capability dramatically increases the flexibility of logging, +without adding code to the main server. In order to write logs to a +pipe, simply replace the filename with the pipe character +"
+ +|", followed by the name of the executable which should +accept log entries on its standard input. Apache will start the +piped-log process when the server starts, and will restart it if it +crashes while the server is running. (This last feature is why we can +refer to this technique as "reliable piped logging".)Piped log processes are spawned by the parent Apache HTTPD process, +and inherit the userid of that process. This means that piped log +programs usually run as root. It is therefore very important to keep +the programs simple and secure.
+ +Some simple examples using piped logs:
+ +
+ ++# compressed logs
+CustomLog "|/usr/bin/gzip -c >> /var/log/access_log.gz" common
+# almost-real-time name resolution
+CustomLog "|/usr/local/apache/bin/logresolve >> /var/log/access_log" common +Notice that quotes are used to enclose the entire command +that will be called for the pipe. Although these examples are +for the access log, the same technique can be used for the +error log.
+ +One important use of piped logs is to allow log rotation without +having to restart the server. Apache HTTPD includes a simple program +called rotatelogs for this +purpose. For example, to rotate the logs every 24 hours, you can +use:
+ +
+ ++CustomLog "|/usr/local/apache/bin/rotatelogs /var/log/access_log 86400" common +A similar, but much more flexible log rotation program +called cronolog +is available at an external site.
+ +As with conditional logging, piped logs are a very powerful tool, +but they should not be used where a simpler solution like +off-line post-processing is available.
+ +
+ +Virtual Hosts
+ +When running a server with many virtual +hosts, there are several options for dealing with log files. +First, it is possible to use logs exactly as in a single-host server. +Simply by placing the logging directives outside the +
+ +<VirtualHost>sections in the main server context, +it is possible to log all requests in the same access log and error +log. This technique does not allow for easy collection of statistics +on individual virtual hosts.If
+ +CustomLogorErrorLogdirectives are +placed inside a<VirtualHost>section, all requests +or errors for that virtual host will be logged only to the specified +file. Any virtual host which does not have logging directives will +still have its requests sent to the main server logs. This technique +is very useful for a small number of virtual hosts, but if the number +of hosts is very large, it can be complicated to manage. In addition, +it can often create problems with insufficient file descriptors.For the access log, there is a very good compromise. By adding +information on the virtual host to the log format string, +it is possible to log all hosts to the same log, and later +split the log into individual files. For example, consider the +following directives.
+ +
+ ++LogFormat "%v %l %u %t \"%r\" %>s %b" comonvhost
+CustomLog logs/access_log comonvhost +The
+ +%vis used to log the name of the virtual host +that is serving the request. Then a program like split-logfile can be used to +post-process the access log in order to split it into one file per +virtual host.Unfortunately, no similar technique is available for the error log, +so you must choose between mixing all virtual hosts in the same error +log and using one error log per virtual host.
+ +
+ +Other Log Files
+ +
+ ++Related Modules
+ +mod_cgi
+mod_rewrite + ++Related Directives
+ +PidFile
+RewriteLog +RewriteLogLevel +ScriptLog
+ScriptLogLength
+ScriptLogBuffer + +PID File
+ +On startup, Apache HTTPD saves the process id of the parent httpd +process to the file
logs/httpd.pid. This filename can be +changed with the PidFile +directive. The process-id is for use by the administrator in +restarting and terminating the daemon by sending signals +to the parent process; on Windows, use the -k command line +option instead. For more information see the Stopping and Restarting page. + +Script Log
+ +In order to aid in debugging, the +ScriptLog +directive allows you to record the input to and output from +CGI scripts. This should only be used in testing - not for +live servers. More information is available in the +mod_cgi documentation. + +
Rewrite Log
+ +When using the powerful and complex features of mod_rewrite, it is almost always +necessary to use the RewriteLog to help in +debugging. This log file produces a detailed analysis of how the +rewriting engine transforms requests. The level of detail is +controlled by the RewriteLogLevel +directive.
+ + + + diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en new file mode 100644 index 00000000000..d3ebf480c58 --- /dev/null +++ b/docs/manual/logs.html.en @@ -0,0 +1,580 @@ + + + +Log Files - Apache HTTP Server + + + + + +Log Files
+ +In order to effectively manage a web server, it is necessary to get +feedback about the activity and performance of the server as well as +any problems that may be occuring. The Apache HTTP Server provides +very comprehensive and flexible logging capabilities. This document +describes how to configure the various log files, and how to +understand what the logs contain.
+ +-
+
- Security Warning +
- Error Log +
- Access Log + +
- Log Rotation +
- Piped Logs +
- VirtualHosts +
- Other Log Files
+
-
+
- PID File +
- Script Log +
- Rewrite Log +
+
+ +Security Warning
+ +Anyone who can write to the directory where Apache is writing a +log file can almost certainly gain access to the uid that the server is +started as, which is normally root. Do NOT give people write +access to the directory the logs are stored in without being aware of +the consequences; see the security tips +document for details.
+ +In addition, log files may contain information supplied directly +by the client, without escaping. Therefore, it is possible for +malicious clients to insert control-characters in the log files, so +care must be taken in dealing with raw logs.
+ +
+ +Error Log
+ ++
+ ++Related Directives
+ +ErrorLog
+LogLevel +The server error log, whose name and location is set by the ErrorLog directive, is the most +important log file. This is the place where Apache HTTPD will send +diagnostic information and record any errors that it encounters in +processing requests. It is the first place to look when a problem +occurs with starting the server or with the operation of the server, +since it will often contain details of what went wrong and how to fix +it.
+ +The error log is usually written to a file (typically +
+ +error_logon unix systems anderror.logon +Windows and OS/2). On unix systems it is also possible to have the +server send errors to thesyslogor pipe +them through a program.The format of the error log is relatively free-form and +descriptive. But there is certain information that is contained +in most error log entries. For example, here is a typical message.
+ +
+ ++[Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1] client denied by server configuration: /export/home/live/ap/htdocs/test +The first item in the log entry is the date and time of the +message. The second entry lists the severity of the error being +reported. The LogLevel directive +is used to control the types of errors that are sent to the error log +by restricting the severity level. The third entry gives the IP +address of the client that generated the error. Beyond that is the +message itself, which in this case indicates that the server has been +configured to deny the client access. The server reports the +file-system path (as opposed to the web path) of the requested +document.
+ +A very wide variety of different messages can appear in the error +log. Most look similar to the example above. The error log will also +contain debugging output from CGI scripts. Any information written to +
+ +stderrby a CGI script will be copied directly to the +error log.It is not possible to customize the error log by adding or removing +information. However, error log entries dealing with particular +requests have corresponding entries in the access +log. For example, the above example entry corresponds to an +access log entry with status code 403. Since it is possible to +customize the access log, you can obtain more information about error +conditions using that log file.
+ +During testing, it is often useful to continuously monitor the +error log for any problems. On unix systems, you can accomplish this +using:
+
+ ++tail -f error_log +
+ +Access Log
+ +
+ ++Related Modules
+ +mod_log_config
+ ++Related Directives
+ +CustomLog
+LogFormat
+SetEnvIf + +The server access log records all requests processed by the server. +The location of the access log as well as its contents are controlled +by the CustomLog +directive. The LogFormat directive can +be used to simplify the selection of the contents of the logs. +This section describes how to configure the server to record +information in the access log.
+ +Of course, storing the information in the access log is only the +start of log management. The next step is to analyze this information +to produce useful statistics. Log analysis in general is beyond the +scope of this document, and not really part of the job of the +web server itself. For more information about this topic, and for +applications which perform log analysis, check the Open Directory or Yahoo.
+ +Various versions of Apache HTTPD have used other modules and +directives to control access logging, including mod_log_referer, +mod_log_agent, and the
+ +TransferLogdirective. The +CustomLogdirective now subsumes the functionality of all +the older directives.The format of the access log is highly configurable. The format is +specified using a format +string that looks much like a C-style printf(1) format string. +Some examples are presented in the next sections. For a complete list +of the possible contents of the format string, see the mod_log_config documentation.
+ +Common Log Format
+ +A typical configuration for the access log might look +as follows.
+ +
+ ++LogFormat "%h %l %u %t \"%r\" %>s %b" common
+CustomLog logs/access_log common +This defines the nickname
+ +commonand +associates it with a particular log format string. The format string +consists of percent directives, each of which tell the server to log a +particular piece of information. Literal characters may also be +placed in the format string and will be copied directly into the log +output. The quote character (") must be escaped by +placing a back-slash before it to prevent it from being interpreted as +the end of the format string. The format string may also contain the +special control characters "\n" for new-line and +"\t" for tab.The
+ +CustomLogdirective sets up a new log file using +the defined nickname. The filename for the access log is +relative to the ServerRoot +unless it begins with a slash.The above configuration will write log entries in a format known as +the Common Log Format (CLF). This standard format can be produced by +many different web servers and read by many log analysis programs. +The log file entries produced in CLF will look something like +this:
+ +
+ ++127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 +Each part of this log entry is described below.
+ +-
+
127.0.0.1(%h)- This is the IP
+address of the client (remote host) which made the request to the
+server. If HostNameLookups is set to
+
On, then the server will try to determine the hostname +and log it in place of the IP address. However, this configuration is +not recommended since it can significantly slow the server. Instead, +it is best to use a log post-processor such as logresolve to determine the +hostnames. The IP address reported here is not necessarily the +address of the machine at which the user is sitting. If a proxy +server exists between the user and the server, this address will be +the address of the proxy, rather than the originating machine.
+
+ -(%l)- The "hyphen" in the
+output indicates that the requested piece of information is not
+available. In this case, the information that is not available is the
+RFC 1413 identity of the client determined by
identdon +the clients machine. This information is highly unreliable and should +almost never be used except on tightly controlled internal networks. +Apache HTTPD will not even attempt to determine this information +unless IdentityCheck is set +toOn.
+
+ frank(%u)- This is the userid
+of the person requesting the document as determined by HTTP
+authentication. The same value is typically provided to CGI scripts
+in the
REMOTE_USERenvironment variable. If the status +code for the request (see below) is 401, then this value should not be +trusted because the user is not yet authenticated. If the document is +not password protected, this entry will be "-" just like +the previous one.
+
+ [10/Oct/2000:13:55:36 -0700](%t)
+- The time that the server finished processing the request. The
+format is:
+
+It is possible to have the time displayed in another format +by specifying[day/month/year:hour:minute:second zone]
+day = 2*digit
+month = 3*letter
+year = 4*digit
+hour = 2*digit
+minute = 2*digit
+second = 2*digit
+zone = (`+' | `-') 4*digit%{format}tin the log format string, where +formatis as instrftime(3)from the C +standard library. +
+
+ "GET /apache_pb.gif HTTP/1.0"+(\"%r\")- The request line from the client is
+given in double quotes. The request line contains a great deal of
+useful information. First, the method used by the client is
+
GET. Second, the client requested the resource +/apache_pb.gif, and third, the client used the protocol +HTTP/1.0. It is also possible to log one or more
+parts of the request line independently. For example, the format
+string "
%m %U%q %H" will log the method, path, +query-string, and protocol, resulting in exactly the same output as +"%r".
+
+ -
diff --git a/docs/icons/a.png b/docs/icons/a.png
new file mode 100644
index 00000000000..c1840256dcf
Binary files /dev/null and b/docs/icons/a.png differ
diff --git a/docs/icons/alert.black.png b/docs/icons/alert.black.png
new file mode 100644
index 00000000000..af6b1246ad7
Binary files /dev/null and b/docs/icons/alert.black.png differ
diff --git a/docs/icons/alert.red.png b/docs/icons/alert.red.png
new file mode 100644
index 00000000000..b9222fd5246
Binary files /dev/null and b/docs/icons/alert.red.png differ
diff --git a/docs/icons/apache_pb.png b/docs/icons/apache_pb.png
new file mode 100644
index 00000000000..eb99a8cd393
Binary files /dev/null and b/docs/icons/apache_pb.png differ
diff --git a/docs/icons/apache_pb2.png b/docs/icons/apache_pb2.png
new file mode 100644
index 00000000000..28baa70fb8c
Binary files /dev/null and b/docs/icons/apache_pb2.png differ
diff --git a/docs/icons/back.png b/docs/icons/back.png
new file mode 100644
index 00000000000..2d8d353bbc7
Binary files /dev/null and b/docs/icons/back.png differ
diff --git a/docs/icons/ball.gray.png b/docs/icons/ball.gray.png
new file mode 100644
index 00000000000..7b756f2d82d
Binary files /dev/null and b/docs/icons/ball.gray.png differ
diff --git a/docs/icons/ball.red.png b/docs/icons/ball.red.png
new file mode 100644
index 00000000000..05f3e50629c
Binary files /dev/null and b/docs/icons/ball.red.png differ
diff --git a/docs/icons/binary.png b/docs/icons/binary.png
new file mode 100644
index 00000000000..c5119d1e1ea
Binary files /dev/null and b/docs/icons/binary.png differ
diff --git a/docs/icons/binhex.png b/docs/icons/binhex.png
new file mode 100644
index 00000000000..eff532202d3
Binary files /dev/null and b/docs/icons/binhex.png differ
diff --git a/docs/icons/blank.png b/docs/icons/blank.png
new file mode 100644
index 00000000000..3802c03c9c8
Binary files /dev/null and b/docs/icons/blank.png differ
diff --git a/docs/icons/bomb.png b/docs/icons/bomb.png
new file mode 100644
index 00000000000..5261a0575e3
Binary files /dev/null and b/docs/icons/bomb.png differ
diff --git a/docs/icons/box1.png b/docs/icons/box1.png
new file mode 100644
index 00000000000..c55fccf8dc8
Binary files /dev/null and b/docs/icons/box1.png differ
diff --git a/docs/icons/box2.png b/docs/icons/box2.png
new file mode 100644
index 00000000000..26d14325d97
Binary files /dev/null and b/docs/icons/box2.png differ
diff --git a/docs/icons/broken.png b/docs/icons/broken.png
new file mode 100644
index 00000000000..e8fd150a339
Binary files /dev/null and b/docs/icons/broken.png differ
diff --git a/docs/icons/burst.png b/docs/icons/burst.png
new file mode 100644
index 00000000000..2329898f2a4
Binary files /dev/null and b/docs/icons/burst.png differ
diff --git a/docs/icons/c.png b/docs/icons/c.png
new file mode 100644
index 00000000000..41593b36b36
Binary files /dev/null and b/docs/icons/c.png differ
diff --git a/docs/icons/comp.blue.png b/docs/icons/comp.blue.png
new file mode 100644
index 00000000000..60ff156deb9
Binary files /dev/null and b/docs/icons/comp.blue.png differ
diff --git a/docs/icons/comp.gray.png b/docs/icons/comp.gray.png
new file mode 100644
index 00000000000..01538f8f316
Binary files /dev/null and b/docs/icons/comp.gray.png differ
diff --git a/docs/icons/compressed.png b/docs/icons/compressed.png
new file mode 100644
index 00000000000..de7276dbc08
Binary files /dev/null and b/docs/icons/compressed.png differ
diff --git a/docs/icons/continued.png b/docs/icons/continued.png
new file mode 100644
index 00000000000..8f656e27f24
Binary files /dev/null and b/docs/icons/continued.png differ
diff --git a/docs/icons/dir.png b/docs/icons/dir.png
new file mode 100644
index 00000000000..6b97905067e
Binary files /dev/null and b/docs/icons/dir.png differ
diff --git a/docs/icons/down.png b/docs/icons/down.png
new file mode 100644
index 00000000000..be3904b0451
Binary files /dev/null and b/docs/icons/down.png differ
diff --git a/docs/icons/dvi.png b/docs/icons/dvi.png
new file mode 100644
index 00000000000..19c417f227b
Binary files /dev/null and b/docs/icons/dvi.png differ
diff --git a/docs/icons/f.png b/docs/icons/f.png
new file mode 100644
index 00000000000..c946f5b3165
Binary files /dev/null and b/docs/icons/f.png differ
diff --git a/docs/icons/folder.open.png b/docs/icons/folder.open.png
new file mode 100644
index 00000000000..dd2d7e0cc2d
Binary files /dev/null and b/docs/icons/folder.open.png differ
diff --git a/docs/icons/folder.png b/docs/icons/folder.png
new file mode 100644
index 00000000000..6b97905067e
Binary files /dev/null and b/docs/icons/folder.png differ
diff --git a/docs/icons/folder.sec.png b/docs/icons/folder.sec.png
new file mode 100644
index 00000000000..833f59ac517
Binary files /dev/null and b/docs/icons/folder.sec.png differ
diff --git a/docs/icons/forward.png b/docs/icons/forward.png
new file mode 100644
index 00000000000..c5584a4c306
Binary files /dev/null and b/docs/icons/forward.png differ
diff --git a/docs/icons/generic.png b/docs/icons/generic.png
new file mode 100644
index 00000000000..0227cabb5ce
Binary files /dev/null and b/docs/icons/generic.png differ
diff --git a/docs/icons/generic.red.png b/docs/icons/generic.red.png
new file mode 100644
index 00000000000..be63249beb5
Binary files /dev/null and b/docs/icons/generic.red.png differ
diff --git a/docs/icons/generic.sec.png b/docs/icons/generic.sec.png
new file mode 100644
index 00000000000..0bd3d96bdcd
Binary files /dev/null and b/docs/icons/generic.sec.png differ
diff --git a/docs/icons/hand.right.png b/docs/icons/hand.right.png
new file mode 100644
index 00000000000..93035c658ab
Binary files /dev/null and b/docs/icons/hand.right.png differ
diff --git a/docs/icons/hand.up.png b/docs/icons/hand.up.png
new file mode 100644
index 00000000000..1405a6f1562
Binary files /dev/null and b/docs/icons/hand.up.png differ
diff --git a/docs/icons/icon.sheet.png b/docs/icons/icon.sheet.png
new file mode 100644
index 00000000000..b875cb6b1c1
Binary files /dev/null and b/docs/icons/icon.sheet.png differ
diff --git a/docs/icons/image1.png b/docs/icons/image1.png
new file mode 100644
index 00000000000..c1374fde333
Binary files /dev/null and b/docs/icons/image1.png differ
diff --git a/docs/icons/image2.png b/docs/icons/image2.png
new file mode 100644
index 00000000000..606d4fb87e5
Binary files /dev/null and b/docs/icons/image2.png differ
diff --git a/docs/icons/image3.png b/docs/icons/image3.png
new file mode 100644
index 00000000000..701fb1e1359
Binary files /dev/null and b/docs/icons/image3.png differ
diff --git a/docs/icons/index.png b/docs/icons/index.png
new file mode 100644
index 00000000000..9a0de350582
Binary files /dev/null and b/docs/icons/index.png differ
diff --git a/docs/icons/layout.png b/docs/icons/layout.png
new file mode 100644
index 00000000000..0a97c1c475f
Binary files /dev/null and b/docs/icons/layout.png differ
diff --git a/docs/icons/left.png b/docs/icons/left.png
new file mode 100644
index 00000000000..d6e2404a811
Binary files /dev/null and b/docs/icons/left.png differ
diff --git a/docs/icons/link.png b/docs/icons/link.png
new file mode 100644
index 00000000000..4714d0ef40a
Binary files /dev/null and b/docs/icons/link.png differ
diff --git a/docs/icons/movie.png b/docs/icons/movie.png
new file mode 100644
index 00000000000..5615180de88
Binary files /dev/null and b/docs/icons/movie.png differ
diff --git a/docs/icons/p.png b/docs/icons/p.png
new file mode 100644
index 00000000000..3fbe0e8801e
Binary files /dev/null and b/docs/icons/p.png differ
diff --git a/docs/icons/patch.png b/docs/icons/patch.png
new file mode 100644
index 00000000000..808ed7865fe
Binary files /dev/null and b/docs/icons/patch.png differ
diff --git a/docs/icons/pdf.png b/docs/icons/pdf.png
new file mode 100644
index 00000000000..516142bb47b
Binary files /dev/null and b/docs/icons/pdf.png differ
diff --git a/docs/icons/pie0.png b/docs/icons/pie0.png
new file mode 100644
index 00000000000..12e0200c97f
Binary files /dev/null and b/docs/icons/pie0.png differ
diff --git a/docs/icons/pie1.png b/docs/icons/pie1.png
new file mode 100644
index 00000000000..c44c793ed8b
Binary files /dev/null and b/docs/icons/pie1.png differ
diff --git a/docs/icons/pie2.png b/docs/icons/pie2.png
new file mode 100644
index 00000000000..e0b7167d913
Binary files /dev/null and b/docs/icons/pie2.png differ
diff --git a/docs/icons/pie3.png b/docs/icons/pie3.png
new file mode 100644
index 00000000000..820a3c35fa9
Binary files /dev/null and b/docs/icons/pie3.png differ
diff --git a/docs/icons/pie4.png b/docs/icons/pie4.png
new file mode 100644
index 00000000000..35490d857c7
Binary files /dev/null and b/docs/icons/pie4.png differ
diff --git a/docs/icons/pie5.png b/docs/icons/pie5.png
new file mode 100644
index 00000000000..359b7d377f4
Binary files /dev/null and b/docs/icons/pie5.png differ
diff --git a/docs/icons/pie6.png b/docs/icons/pie6.png
new file mode 100644
index 00000000000..4b293eae18c
Binary files /dev/null and b/docs/icons/pie6.png differ
diff --git a/docs/icons/pie7.png b/docs/icons/pie7.png
new file mode 100644
index 00000000000..6bfa2d06ae2
Binary files /dev/null and b/docs/icons/pie7.png differ
diff --git a/docs/icons/pie8.png b/docs/icons/pie8.png
new file mode 100644
index 00000000000..716cf2822bf
Binary files /dev/null and b/docs/icons/pie8.png differ
diff --git a/docs/icons/portal.png b/docs/icons/portal.png
new file mode 100644
index 00000000000..937c0f87cd6
Binary files /dev/null and b/docs/icons/portal.png differ
diff --git a/docs/icons/ps.png b/docs/icons/ps.png
new file mode 100644
index 00000000000..ccccf730b6c
Binary files /dev/null and b/docs/icons/ps.png differ
diff --git a/docs/icons/quill.png b/docs/icons/quill.png
new file mode 100644
index 00000000000..b697770a882
Binary files /dev/null and b/docs/icons/quill.png differ
diff --git a/docs/icons/right.png b/docs/icons/right.png
new file mode 100644
index 00000000000..41f8529a84e
Binary files /dev/null and b/docs/icons/right.png differ
diff --git a/docs/icons/screw1.png b/docs/icons/screw1.png
new file mode 100644
index 00000000000..11673ab97dc
Binary files /dev/null and b/docs/icons/screw1.png differ
diff --git a/docs/icons/screw2.png b/docs/icons/screw2.png
new file mode 100644
index 00000000000..5d7d2cf65e9
Binary files /dev/null and b/docs/icons/screw2.png differ
diff --git a/docs/icons/script.png b/docs/icons/script.png
new file mode 100644
index 00000000000..2520570a775
Binary files /dev/null and b/docs/icons/script.png differ
diff --git a/docs/icons/small/back.png b/docs/icons/small/back.png
new file mode 100644
index 00000000000..2257df2140d
Binary files /dev/null and b/docs/icons/small/back.png differ
diff --git a/docs/icons/small/binary.png b/docs/icons/small/binary.png
new file mode 100644
index 00000000000..2e2e1b073d6
Binary files /dev/null and b/docs/icons/small/binary.png differ
diff --git a/docs/icons/small/binhex.png b/docs/icons/small/binhex.png
new file mode 100644
index 00000000000..9deab419b61
Binary files /dev/null and b/docs/icons/small/binhex.png differ
diff --git a/docs/icons/small/blank.png b/docs/icons/small/blank.png
new file mode 100644
index 00000000000..86f57a504f7
Binary files /dev/null and b/docs/icons/small/blank.png differ
diff --git a/docs/icons/small/broken.png b/docs/icons/small/broken.png
new file mode 100644
index 00000000000..79c998c8c31
Binary files /dev/null and b/docs/icons/small/broken.png differ
diff --git a/docs/icons/small/burst.png b/docs/icons/small/burst.png
new file mode 100644
index 00000000000..2b21436c78e
Binary files /dev/null and b/docs/icons/small/burst.png differ
diff --git a/docs/icons/small/comp1.png b/docs/icons/small/comp1.png
new file mode 100644
index 00000000000..6d8c3459ed0
Binary files /dev/null and b/docs/icons/small/comp1.png differ
diff --git a/docs/icons/small/comp2.png b/docs/icons/small/comp2.png
new file mode 100644
index 00000000000..57f7ad197b8
Binary files /dev/null and b/docs/icons/small/comp2.png differ
diff --git a/docs/icons/small/compressed.png b/docs/icons/small/compressed.png
new file mode 100644
index 00000000000..43acd8b943d
Binary files /dev/null and b/docs/icons/small/compressed.png differ
diff --git a/docs/icons/small/continued.png b/docs/icons/small/continued.png
new file mode 100644
index 00000000000..db17c424650
Binary files /dev/null and b/docs/icons/small/continued.png differ
diff --git a/docs/icons/small/dir.png b/docs/icons/small/dir.png
new file mode 100644
index 00000000000..9bd6256bdbb
Binary files /dev/null and b/docs/icons/small/dir.png differ
diff --git a/docs/icons/small/dir2.png b/docs/icons/small/dir2.png
new file mode 100644
index 00000000000..836daf49ef2
Binary files /dev/null and b/docs/icons/small/dir2.png differ
diff --git a/docs/icons/small/doc.png b/docs/icons/small/doc.png
new file mode 100644
index 00000000000..c560df21d3c
Binary files /dev/null and b/docs/icons/small/doc.png differ
diff --git a/docs/icons/small/forward.png b/docs/icons/small/forward.png
new file mode 100644
index 00000000000..4ddbc61e142
Binary files /dev/null and b/docs/icons/small/forward.png differ
diff --git a/docs/icons/small/generic.png b/docs/icons/small/generic.png
new file mode 100644
index 00000000000..16374a12bbb
Binary files /dev/null and b/docs/icons/small/generic.png differ
diff --git a/docs/icons/small/generic2.png b/docs/icons/small/generic2.png
new file mode 100644
index 00000000000..40d60c1df23
Binary files /dev/null and b/docs/icons/small/generic2.png differ
diff --git a/docs/icons/small/generic3.png b/docs/icons/small/generic3.png
new file mode 100644
index 00000000000..aa38963afa2
Binary files /dev/null and b/docs/icons/small/generic3.png differ
diff --git a/docs/icons/small/image.png b/docs/icons/small/image.png
new file mode 100644
index 00000000000..d92f0a5fcc4
Binary files /dev/null and b/docs/icons/small/image.png differ
diff --git a/docs/icons/small/image2.png b/docs/icons/small/image2.png
new file mode 100644
index 00000000000..4049bda5619
Binary files /dev/null and b/docs/icons/small/image2.png differ
diff --git a/docs/icons/small/index.png b/docs/icons/small/index.png
new file mode 100644
index 00000000000..080453e2151
Binary files /dev/null and b/docs/icons/small/index.png differ
diff --git a/docs/icons/small/key.png b/docs/icons/small/key.png
new file mode 100644
index 00000000000..1a45f67df31
Binary files /dev/null and b/docs/icons/small/key.png differ
diff --git a/docs/icons/small/movie.png b/docs/icons/small/movie.png
new file mode 100644
index 00000000000..7c126042c9a
Binary files /dev/null and b/docs/icons/small/movie.png differ
diff --git a/docs/icons/small/patch.png b/docs/icons/small/patch.png
new file mode 100644
index 00000000000..c39f14435a0
Binary files /dev/null and b/docs/icons/small/patch.png differ
diff --git a/docs/icons/small/ps.png b/docs/icons/small/ps.png
new file mode 100644
index 00000000000..5c604230d07
Binary files /dev/null and b/docs/icons/small/ps.png differ
diff --git a/docs/icons/small/rainbow.png b/docs/icons/small/rainbow.png
new file mode 100644
index 00000000000..175053cb433
Binary files /dev/null and b/docs/icons/small/rainbow.png differ
diff --git a/docs/icons/small/sound.png b/docs/icons/small/sound.png
new file mode 100644
index 00000000000..6e3e95d3d01
Binary files /dev/null and b/docs/icons/small/sound.png differ
diff --git a/docs/icons/small/sound2.png b/docs/icons/small/sound2.png
new file mode 100644
index 00000000000..bc46eb48fe5
Binary files /dev/null and b/docs/icons/small/sound2.png differ
diff --git a/docs/icons/small/tar.png b/docs/icons/small/tar.png
new file mode 100644
index 00000000000..12f0347bf9c
Binary files /dev/null and b/docs/icons/small/tar.png differ
diff --git a/docs/icons/small/text.png b/docs/icons/small/text.png
new file mode 100644
index 00000000000..b4e30f466d3
Binary files /dev/null and b/docs/icons/small/text.png differ
diff --git a/docs/icons/small/transfer.png b/docs/icons/small/transfer.png
new file mode 100644
index 00000000000..324048170a8
Binary files /dev/null and b/docs/icons/small/transfer.png differ
diff --git a/docs/icons/small/unknown.png b/docs/icons/small/unknown.png
new file mode 100644
index 00000000000..cad7e7a7aa0
Binary files /dev/null and b/docs/icons/small/unknown.png differ
diff --git a/docs/icons/small/uu.png b/docs/icons/small/uu.png
new file mode 100644
index 00000000000..ef87c82ee6c
Binary files /dev/null and b/docs/icons/small/uu.png differ
diff --git a/docs/icons/sound1.png b/docs/icons/sound1.png
new file mode 100644
index 00000000000..7a766be6cc8
Binary files /dev/null and b/docs/icons/sound1.png differ
diff --git a/docs/icons/sound2.png b/docs/icons/sound2.png
new file mode 100644
index 00000000000..45112909398
Binary files /dev/null and b/docs/icons/sound2.png differ
diff --git a/docs/icons/sphere1.png b/docs/icons/sphere1.png
new file mode 100644
index 00000000000..2198ae89ec4
Binary files /dev/null and b/docs/icons/sphere1.png differ
diff --git a/docs/icons/sphere2.png b/docs/icons/sphere2.png
new file mode 100644
index 00000000000..257632ba46d
Binary files /dev/null and b/docs/icons/sphere2.png differ
diff --git a/docs/icons/tar.png b/docs/icons/tar.png
new file mode 100644
index 00000000000..6c40521ff80
Binary files /dev/null and b/docs/icons/tar.png differ
diff --git a/docs/icons/tex.png b/docs/icons/tex.png
new file mode 100644
index 00000000000..906622d3844
Binary files /dev/null and b/docs/icons/tex.png differ
diff --git a/docs/icons/text.png b/docs/icons/text.png
new file mode 100644
index 00000000000..34d0edf86e4
Binary files /dev/null and b/docs/icons/text.png differ
diff --git a/docs/icons/transfer.png b/docs/icons/transfer.png
new file mode 100644
index 00000000000..efaf17b682f
Binary files /dev/null and b/docs/icons/transfer.png differ
diff --git a/docs/icons/unknown.png b/docs/icons/unknown.png
new file mode 100644
index 00000000000..7c241c383c0
Binary files /dev/null and b/docs/icons/unknown.png differ
diff --git a/docs/icons/up.png b/docs/icons/up.png
new file mode 100644
index 00000000000..a69ea00c5b7
Binary files /dev/null and b/docs/icons/up.png differ
diff --git a/docs/icons/uu.png b/docs/icons/uu.png
new file mode 100644
index 00000000000..b1d1a8579d5
Binary files /dev/null and b/docs/icons/uu.png differ
diff --git a/docs/icons/uuencoded.png b/docs/icons/uuencoded.png
new file mode 100644
index 00000000000..b1d1a8579d5
Binary files /dev/null and b/docs/icons/uuencoded.png differ
diff --git a/docs/icons/world1.png b/docs/icons/world1.png
new file mode 100644
index 00000000000..3a65c00d846
Binary files /dev/null and b/docs/icons/world1.png differ
diff --git a/docs/icons/world2.png b/docs/icons/world2.png
new file mode 100644
index 00000000000..9f8a3ea4b35
Binary files /dev/null and b/docs/icons/world2.png differ
diff --git a/docs/manual/developer/documenting.html b/docs/manual/developer/documenting.html
new file mode 100644
index 00000000000..8f8163f426e
--- /dev/null
+++ b/docs/manual/developer/documenting.html
@@ -0,0 +1,64 @@
+
+
+
+
200 (- This is the status +code that the server sends back to the client. This information is +very valuable, because it reveals whether the request resulted in a +successful response (codes beginning in 2), a redirection (codes +beginning in 3), an error caused by the client (codes beginning in 4), +or an error in the server (codes beginning in 5). +The full list of possible status codes can be +found in the HTTP specification (RFC2616 section 10). + +
2326(%b) +- The last entry indicates the size of the object returned to
+the client, not including the response headers. If no content
+was returned to the client, this value will be "
-". +To log "0" for no content, use%B+instead.
+
+
%>s) Combined Log Format
+ +Another commonly used format string is called the +Combined Log Format. It can be used as follows.
+ +
+LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined
+CustomLog log/acces_log combined
+This format is exactly the same as the Common Log Format, +with the addition of two more fields. The access log under this +format will look like:
+ +
+127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 "http://www.example.com/start.html" "Mozilla/4.08 [en] (Win98; I ;Nav)"
+The additional fields are:
+ +-
+
+
"http://www.example.com/start.html"+(\"%{Referer}i\")- The "Referer" (sic) HTTP
+request header. This gives the site that the client reports having
+been referred from. (This should be the page that links to or includes
+
/apache_pb.gif). + + "Mozilla/4.08 [en] (Win98; I ;Nav)"+(\"%{User-agent}i\")- The User-Agent HTTP request +header. This is the identifying information that the client browser +reports about itself. + +
Multiple Access Logs
+ +Multiple access logs can be created simply by specifying multiple
+CustomLog directives in the configuration file. For
+example, the following directives will create three access logs. The
+first contains the basic CLF information, while the second and third
+contain referer and browser information. The last two
+CustomLog lines show how to mimic the effects of the
+ReferLog and AgentLog directives.
+LogFormat "%h %l %u %t \"%r\" %>s %b" common
+CustomLog logs/access_log common
+CustomLog logs/referer_log "%{Referer}i -> %U"
+CustomLog logs/agent_log "%{User-agent}i"
+This example also shows that it is not necessary to define a
+nickname with the LogFormat directive. Instead, the log
+format can be specified directly in the CustomLog
+directive.
Conditional Logging
+ +There are times when it is convenient to exclude certain entries
+from the access logs based on characteristics of the client request.
+This is easily accomplished with the help of environment variables. First, an environment
+variable must be set to indicate that the request meets certain
+conditions. This is usually accomplished with SetEnvIf. Then the
+env= clause of the CustomLog directive is
+used to include or exclude requests where the environment variable is
+set. Some examples:
+# Mark requests from the loop-back interface
+SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog
+# Mark requests for the robots.txt file
+SetEnvIf Request_URI "^/robots\.txt$" dontlog
+# Log what remains
+CustomLog logs/access_log common env=!dontlog
+As another example, consider logging requests from english-speakers +to one log file, and non-english speakers to a different log file.
+ +
+SetEnvIf Accept-Language "en" english
+CustomLog logs/english_log common env=english
+CustomLog logs/non_english_log common env=!english
+Although we have just shown that conditional logging is very +powerful and flexibly, it is not the only way to control the contents +of the logs. Log files are more useful when they contain a complete +record of server activity. It is often easier to simply post-process +the log files to remove requests that you do not want to consider.
+ ++ +
Log Rotation
+ +On even a moderately busy server, the quantity of information +stored in the log files is very large. The access log file typically +grows 1 MB or more per 10,000 requests. It will consequently be +necessary to periodically rotate the log files by moving or deleting +the existing logs. This cannot be done while the server is running, +because Apache will continue writing to the old log file as long as it +holds the file open. Instead, the server must be restarted after the log files are moved or +deleted so that it will open new log files.
+ +By using a graceful restart, the server can be instructed +to open new log files without losing any existing or pending +connections from clients. However, in order to accomplish this, the +server must continue to write to the old log files while it finishes +serving old requests. It is therefore necessary to wait for some time +after the restart before doing any processing on the log files. A +typical scenario that simply rotates the logs and compresses the old +logs to save space is:
+ +
+mv access_log access_log.old
+mv error_log error_log.old
+apachectl graceful
+sleep 600
+gzip access_log.old error_log.old
+Another way to perform log rotation is using piped +logs as discussed in the next section.
+ ++ +
Piped Logs
+ +Apache HTTPD is capable of writing error and access log files
+through a pipe to another process, rather than directly to a file.
+This capability dramatically increases the flexibility of logging,
+without adding code to the main server. In order to write logs to a
+pipe, simply replace the filename with the pipe character
+"|", followed by the name of the executable which should
+accept log entries on its standard input. Apache will start the
+piped-log process when the server starts, and will restart it if it
+crashes while the server is running. (This last feature is why we can
+refer to this technique as "reliable piped logging".)
Piped log processes are spawned by the parent Apache HTTPD process, +and inherit the userid of that process. This means that piped log +programs usually run as root. It is therefore very important to keep +the programs simple and secure.
+ +Some simple examples using piped logs:
+ +
+# compressed logs
+CustomLog "|/usr/bin/gzip -c >> /var/log/access_log.gz" common
+# almost-real-time name resolution
+CustomLog "|/usr/local/apache/bin/logresolve >> /var/log/access_log" common
+Notice that quotes are used to enclose the entire command +that will be called for the pipe. Although these examples are +for the access log, the same technique can be used for the +error log.
+ +One important use of piped logs is to allow log rotation without +having to restart the server. Apache HTTPD includes a simple program +called rotatelogs for this +purpose. For example, to rotate the logs every 24 hours, you can +use:
+ +
+CustomLog "|/usr/local/apache/bin/rotatelogs /var/log/access_log 86400" common
+A similar, but much more flexible log rotation program +called cronolog +is available at an external site.
+ +As with conditional logging, piped logs are a very powerful tool, +but they should not be used where a simpler solution like +off-line post-processing is available.
+ ++ +
Virtual Hosts
+ +When running a server with many virtual
+hosts, there are several options for dealing with log files.
+First, it is possible to use logs exactly as in a single-host server.
+Simply by placing the logging directives outside the
+<VirtualHost> sections in the main server context,
+it is possible to log all requests in the same access log and error
+log. This technique does not allow for easy collection of statistics
+on individual virtual hosts.
If CustomLog or ErrorLog directives are
+placed inside a <VirtualHost> section, all requests
+or errors for that virtual host will be logged only to the specified
+file. Any virtual host which does not have logging directives will
+still have its requests sent to the main server logs. This technique
+is very useful for a small number of virtual hosts, but if the number
+of hosts is very large, it can be complicated to manage. In addition,
+it can often create problems with insufficient file descriptors.
For the access log, there is a very good compromise. By adding +information on the virtual host to the log format string, +it is possible to log all hosts to the same log, and later +split the log into individual files. For example, consider the +following directives.
+ +
+LogFormat "%v %l %u %t \"%r\" %>s %b" comonvhost
+CustomLog logs/access_log comonvhost
+The %v is used to log the name of the virtual host
+that is serving the request. Then a program like split-logfile can be used to
+post-process the access log in order to split it into one file per
+virtual host.
Unfortunately, no similar technique is available for the error log, +so you must choose between mixing all virtual hosts in the same error +log and using one error log per virtual host.
+ ++ +
Other Log Files
+ +|
+Related Modules + +mod_cgi +mod_rewrite + + |
+Related Directives + +PidFile +RewriteLog +RewriteLogLevel +ScriptLog +ScriptLogLength +ScriptLogBuffer + + |
PID File
+ +On startup, Apache HTTPD saves the process id of the parent httpd
+process to the file logs/httpd.pid. This filename can be
+changed with the PidFile
+directive. The process-id is for use by the administrator in
+restarting and terminating the daemon by sending signals
+to the parent process; on Windows, use the -k command line
+option instead. For more information see the Stopping and Restarting page.
+
+
Script Log
+ +In order to aid in debugging, the +ScriptLog +directive allows you to record the input to and output from +CGI scripts. This should only be used in testing - not for +live servers. More information is available in the +mod_cgi documentation. + +
Rewrite Log
+ +When using the powerful and complex features of mod_rewrite, it is almost always +necessary to use the RewriteLog to help in +debugging. This log file produces a detailed analysis of how the +rewriting engine transforms requests. The level of detail is +controlled by the RewriteLogLevel +directive.
+ + + + diff --git a/docs/manual/mod/mod_cgid.html b/docs/manual/mod/mod_cgid.html new file mode 100644 index 00000000000..396d608d5cc --- /dev/null +++ b/docs/manual/mod/mod_cgid.html @@ -0,0 +1,101 @@ + + + +Module mod_cgid
+ +This module provides for execution of CGI scripts using an external +CGI daemon.
+ +Status: Base (unix threaded MPMs only)
+
+Source File: mod_cgid.c
+
+Module Identifier: cgid_module
+
Summary
+ +On certain unix operating systems, forking a process from a +multi-threaded server is a very expensive operation because the new +process will replicate all the threads of the parent process. In +order to avoid incurring this expense on each CGI invocation, mod_cgid +creates an external daemon that is responsible for forking child +processes to run CGI scripts. The main server communicates with this +daemon using a unix domain socket.
+ +This module is used by default whenever a multi-threaded MPM is
+selected during the compilation process. At the user level, this
+module is identical in configuration and operation to mod_cgi. The only exception is the additional
+directive ScriptSock which gives the name of the socket
+to use for communication with the cgi daemon.
Directives
+ + + ++ +
ScriptSock directive
+ +Syntax: Scriptsock filename
+Default: logs/cgisock
+Context: server config
+Status: Base
+Module: mod_cgid
This directive sets the name of the socket to use for communication +with the CGI daemon. The socket will be opened using the permissions +of the user who starts Apache (usually root). To maintain the security +of communications with CGI scripts, it is important that no other +user has permission to write in the directory where the socket is +located.
+ + + + + + diff --git a/docs/manual/mod/mod_suexec.html b/docs/manual/mod/mod_suexec.html new file mode 100644 index 00000000000..0910999f1ae --- /dev/null +++ b/docs/manual/mod/mod_suexec.html @@ -0,0 +1,95 @@ + + + +Module mod_suexec
+ ++This module provides support for +running CGI scripts as a specified User and Group. +
+ +Status: Extension
+
+Source File: mod_suexec.c
+
+Module Identifier: suexec_module
+
+Compatibility: Available in Apache 2.0 and later.
+
Summary
+ +This module allows CGI scripts to run as a specified user and Group.
+ +Directives
+-
+
- SuexecUserGroup +
SuexecUserGroup directive
+
+Syntax: SuexecUserGroup User Group
+Default: None
+Context: server config, virtual host
+Status: Extension
+Module: mod_suexec
+Compatibility: SuexecUserGroup is only available in 2.0 and later.
+The SuexecUserGroup directive allows you to specify a user and
+group for CGI programs to run as. Non-CGI requests are still processes
+with the user specified in the User directive. This directive replaces
+using the User and Group directives inside of VirtualHosts.
+
+ +
+ Apache HTTP Server Version 2.0 +
+ +
+
+
+
+
diff --git a/include/util_ldap.h b/include/util_ldap.h
new file mode 100644
index 00000000000..10dc2eabe55
--- /dev/null
+++ b/include/util_ldap.h
@@ -0,0 +1,275 @@
+/* ====================================================================
+ * The Apache Software License, Version 1.1
+ *
+ * Copyright (c) 2000-2001 The Apache Software Foundation. All rights
+ * reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer.
+ *
+ * 2. Redistributions in binary form must reproduce the above copyright
+ * notice, this list of conditions and the following disclaimer in
+ * the documentation and/or other materials provided with the
+ * distribution.
+ *
+ * 3. The end-user documentation included with the redistribution,
+ * if any, must include the following acknowledgment:
+ * "This product includes software developed by the
+ * Apache Software Foundation (http://www.apache.org/)."
+ * Alternately, this acknowledgment may appear in the software itself,
+ * if and wherever such third-party acknowledgments normally appear.
+ *
+ * 4. The names "Apache" and "Apache Software Foundation" must
+ * not be used to endorse or promote products derived from this
+ * software without prior written permission. For written
+ * permission, please contact apache@apache.org.
+ *
+ * 5. Products derived from this software may not be called "Apache",
+ * nor may "Apache" appear in their name, without prior written
+ * permission of the Apache Software Foundation.
+ *
+ * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+ * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
+ * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+ * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+ * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ * ====================================================================
+ *
+ * This software consists of voluntary contributions made by many
+ * individuals on behalf of the Apache Software Foundation. For more
+ * information on the Apache Software Foundation, please see
+ * - \n"
+ "
- Host is the name of the LDAP server. Use a space separated list of hosts \n" + "to specify redundant servers.\n" + "
- Port is optional, and specifies the port to connect to.\n" + "
- basedn specifies the base DN to start searches from\n" + "
- Attrib specifies what attribute to search for in the directory. If not " + "provided, it defaults to uid.\n" + "
- Scope is the scope of the search, and can be either sub or " + "one. If not provided, the default is sub.\n" + "
- Filter is a filter to use in the search. If not provided, " + "defaults to (objectClass=*).\n" + "
LDAP Cache Information
\n", r); + + ap_rputs("\n" + "
| Cache Name | " + "Entries | " + "Avg. Chain Len. | " + "Hits | " + "Ins/Rem | " + "Purges | " + "Avg Purge Time | " + "||