Russkij Apach HTTP server ot Dmitriya Kryukova

Russkij Apach HTTP server ot Dmitriya Kryukova

Original  etogo  dokumenta  a  tak zhe vse svyazannye s nim fajly
lezhat na servere Aleksa Tutubalina http://apache.lexa.ru/

1. Kratkij obzor servera

Za osnovu servera byl vzyat populyarnyj server Apache/1.1.3. Tekushaya versiya dannogo servera Apache/1.1.3 rus/PL14. Poslednyaya vepsiya, schitayushchayasya stabil'noj - Apache/1.1.3 rus/PL12. Zdes' mozhno uznat' obo vseh izmeneniyah v dannom servere po sravneniyu s predydushchimi platformami. Rekomenduyu prosmotret' eti izmeneniya tak kak oni znachitel'ny. Takzhe rekomenduyu tshchatel'no izuchit' razdely Kak nastroit' i Nekotorye rekomendacii. Osobennostyami servera yavlyayutsya:

Podderzhka soglasovaniya kodirovok klienta i servera.
Vydacha pravil'nyh Content-type:...;charset=... v sootvetstvii s etim soglasovaniem.
Vydacha pri neobhodimosti zagolovka Expires: dlya proxy serverov.
Podderzhka Ranges.
Podderzhka vozmozhnosti ne zapisyvat' v logfile nenuzhnye adresa.

V servere realizovano sovmeshchenie neskol'kih metodov soglasovaniya kodirovok klienta i servera, a imenno:
Shema soglasovaniya

CHerez zagolovki klienta Accept-Charset: i/ili Accept: text/x-cyrillic ... Esli server znaet o tom charset, kotoryj zaprosil klient, to eti zagolovki imeyut vysshij prioritet dlya servera, vne zavisimosti ot ego nastrojki na native charset.
CHerez poisk v imeni servera nazvaniya odnoj iz skonfigurirovnnyh kodovyh stranic (naprimer: www-koi8-r.stack.serpukhov.su ili www-windows-1251.stack.serpukhov.su)
CHerez poisk v preffikse zaproshennogo URI nazvaniya odnoj iz skonfigurirovnnyh kodovyh stranic (naprimer: http://www.stack.net/windows-1251/file.html)
CHerez konfiguraciyu kodovyh stranic po umolchaniyu dlya razlichnyh tipov klientskih programm v sluchae, kogda server mozhet opoznat' klientskuyu programmu (inogda sredu, v kotoroj rabotaet klientskaya programma).
CHerez tekushchee derevo. T.e. administrator mozhet zapustit' neskol'ko serverov na raznyh portah, ili opisat' v konfiguracii servera neskol'ko virtual'nyh serverov. V oboih sluchayah dlya raznyh real'nyh ili virtual'nyh serverov ustanavlivaetsya svoj charset po umolchaniyu. Posle etogo, administrator mozhet planirovat' derevo v raznyh kodirovkah. Estestvenno, samo derevo dokumentov v takom sluchae hranitsya v edinstvennom ekzemplyare.
V sluchae prinyatiya soobshchestvom edinoj transportnoj kodirovki, neobhodimo budet ostavit' tol'ko ee v servere, nezavisimo ot fizicheskogo sposoba predstavleniya dannyh dokumentov.

Nekotorye osobennosti:

Administrator servera sam opredelyaet - v kakih sluchayah dolzhny ispol'zovat'sya raznye kodovye stranicy. Administrator servera, takzhe, mozhet samostoyatel'no sozdavat' tablicy perekodirovki i pristegivat' ih k serveru dlya soglasovaniya j kodovoj stranicy servera s trebuemoj kodirovkoj klienta.
Server korrektno preobrazuet tekstovye potoki ot/k klientu, vklyuchaya posledovatel'nosti tipa %xx%yy%zz.
Administrator servera mozhet ukazyvat' harakternye priznaki klientskoj programmy (User-agent: zagolovok) i sootvetstvuyushchij dannoj klientskoj programme charset po-umolchaniyu.
Administrator servera mozhet ukazat' klientskie programmy, kotorye neadekvatno vosprinimayut MIME, dlya nih takie zagolovki serverom ne budut vydavat'sya.
Administrator servera mozhet ukazat' prioritet v vybore serverom charset mezhdu URL i User-agent.
Administrator servera mozhet opredelit' reakciyu servera na nekorrektno zaproshennyj charset (t.e. vydavat' li zaproshennyj dokument v takom sluchae v charset po-umolchaniyu)
Ispol'zovanie v URL fragmenta fajla. Dannaya vozmozhnost' pozvolyaet serveru pereslat' klientu ne ves' trebuemyj dokument a tol'ko neobhodimuyu ego chast' (naprimer, ssylki na rezul'tat poiska WAIS v bol'shih strukturirovannyh fajlah). Server vosprinimaet v zaprose konstrukciyu:
- file_name;bytes=l-m ili
- file_name;lines=l-m
Server takzhe vosprinimaet ot klienta zagolovok:
- Range: bytes=a-b
- Range: lines=a-b
Pri etom, dokumentu stavitsya Content-type: text/plain esli dokument byl tekstom ili Content-type: application/octet - esli dokument yavlyaetsya ne tekstovym.
Vozmozhnost' isklyuchat' v konfiguracionnyh fajlah nezhelatel'nye adresa dlya zapisi v logfile dlya kazhdogo real'nogo i virtual'nogo servera s pomoshch'yu direktivy NoLog domain ili NoLog aaa.bbb.ccc

2. Gde vzyat'?

Sejchas dostupny dve versii pravok - dlya Apache-1.1.1 (eto original'nye pravki Dmitriya Kryukova) i dlya Apache-1.1.3 (te zhe pravki, ikorporirovannye v Apache-1.1.3). Starye pravki poka sohraneny t.k. oni pokazali svoyu rabotosposobnost', a pravki dlya 1.1.3 poka eshche prakticheski ne testirovalis'. Sam server Apache mozhno vzyat' na www.apache.org ili na ego zerkalah. Neobhodimye komponenty, realizuyushchie ukazannye vyshe vozmozhnosti mozhno vzyat' po ftp: na servere apache.lexa.ru. Na etot server budut pomeshchat'sya vse posleduyushchie versii pravok (ispravlenie oshibok, pravki dlya novyh versij Apache, novye vozmozhnosti). V nastoyashchee vremya dostupny:

Apache-1.1.3-RUS-pl14a (alpha-quality, budte gotovy k oshibkam :) :

Apache-1.1.3 + RUS-pl14 patches

Tol'ko patchi, nakladyvaemye poverh Apache-1.1.3 clean source tree

Razlichiya mezhdu PL12 i PL14a

Apache-1.1.3 + RUS-pl12 patches

Tol'ko patchi, nakladyvaemye poverh Apache-1.1.3 clean source tree

Apache-1.1.1 + RUS-pl12 patches

Tol'ko patchi, nakladyvaemye poverh Apache-1.1.1 clean source tree

3. Kak ustanovit'?

Ustanovka iz "polnogo arhiva"

Raskrojte poluchennyj arhiv
Vnesite nuzhnye vam izmeneniya v ./src/Configuration i/ili ./src/httpd.h
./Configure && make

Ustanovka patchej poverh distributivnogo Apache

Raskrojte "rodnoj" arhiv servera Apache.
Nalozhite poluchennye s etogo servera patchi s pomoshch'yu programmy patch
Vnesite nuzhnye vam izmeneniya v ./src/Configuration i/ili ./src/httpd.h
./Configure && make

4. Kak nastroit'?

CharsetTable

Sluzhit dlya opisaniya osnovnyh charsets, ispol'zuemyh v servere. Sintaksis sleduyushchij:

CharsetTable Oficial_Name Table1 [Table2] Language

Oficial_Name

Oficial'noe nazvanie charset (naprimer windows-1251, koi8-r, ibm866, iso_8859-5:1988 i.t.d.)

Table1

Imya fajla tavlicy, ustanavlivayushchej sootvetstvie mezhdu vnutrennim predstavleniem dokumentov i dokumentov v dannom charset pri peredache k klientu.

Table2

Imya fajla tavlicy, ustanavlivayushchej sootvetstvie mezhdu vnutrennim predstavleniem dokumentov i dokumentov v dannom charset pri prieme ot klienta. Mozhet otsutstvovat', v etom sluchae ispol'zuetsya tablica, obratnaya Table1.

Language

Nazvanie yazyka, k kotoromu prinadlezhit dannyj charset. |to nazvanie dolzhno byt' opredeleno v conf/srm.conf v direktivah AddLanguage i LanguagePriority.

Primery

CharsetTable iso_8859-5:1988 conf/koi-iso.tab ru
CharsetTable ibm866 conf/koi-alt.tab ru
CharsetTable windows-1251 conf/koi-win.tab ru
CharsetTable koi8-r conf/koi-koi.tab ru

CharsetAlias

Sluzhit dlya opisaniya imen psevdonimov ukazannyh charset. Sintaksis sleduyushchij:

CharsetAlias Oficial_Name Alias1 Alias2 Alias3 ...

Oficial_Name

Oficial'noe imya opisyvaemogo charset. Dolzhno byt' opredeleno do dannoj direktivy direktivoj CharsetTable.

Alias1 Alias2 ...

Imena psevdonimov dlya dannogo charset.

Primery:

CharsetAlias iso_8859-5:1988 iso-ir-144 iso_8859-5 cyrillic iso-8859-5
CharsetAlias iso_8859-5:1988 iso8859-5 iso-8859.5 iso8859.5 iso
CharsetAlias ibm866 csibm866 866 cp866 x-cp866 x-ibm866 cp-866 alt
CharsetAlias windows-1251 win x-cp1251 cp1251 cp-1251

Vse psevdonimy dolzhny byt' opredeleny individual'no dlya kazhdogo virtual'nogo servera.

CharsetPriority

Sluzhit dlya opredeleniya prioritetov skonfigurirovannyh charsets. Mozhet imet' znachenie esli v zaprose klienta ukazany ravnye vesovye koefficienty dlya razlichnyh charsets ili esli ne ukazan NativeCharset to budet ispol'zovan starshij. Sintaksis:

CharsetPriority Charset1 Charset2 Charset3 ...

Charset1 Charset2 ..: Imena charset v poryadke ubyvaniya prioriteta (samyj levyj imeet vysshij prioritet). Vse imena Charset dolzhny byt' opredeleny do etoj direktivy s pomoshch'yu CharsetTable.
Primer:: CharsetPriority windows-1251 koi8-r ibm866

V imenah charset dolzhny ispol'zovat'sya tol'ko oficial'nye imena, a ne psevdonimy.

NativeCharset

Opredelyaet imya chatset po-umolchaniyu dlya dannogo servera. Sintaksis:

NativeCharset Charset_Name

Charset_Name

Oficial'noe imya charset po-umolchaniyu dlya dannogo servera.

Primer:

NativeCharset koi8-r
NativeCharset windows-1251

Opredelyaetsya dlya kazhdogo virtual'nogo servera nezavisimo. Charset_Name dolzhno byt' opredeleno do etoj direktivy s pomoshch'yu direktivy CharsetTable.

AgentCharset

Opredelyaet charset, kotoryj mozhet byt' ispol'zovan pri nahozhdenii v zaprose klienta podstroki, identificiruyushchej dannogo klienta. |ta podstroka ishchetsya v zaprose klienta v pole User-Agent. Sintaksis:

AgentCharset Charset_Name Pattern1 Pattern2 Pattern3 ...

Charset_Name

Oficial'noe imya charset

Pattern1 Pattern2 ...

SHablony dlya poiska v zaprose klienta v pole User-Agent.

Primery:

AgentCharset windows-1251 AIR_Mosaic IWENG/1 MSIE WinMosaic (Windows (WinNT;
AgentCharset windows-1251 (Win16; (Win95; (16-bit)
AgentCharset koi8-r Arena Ariadna Macintosh OmniWeb Sextant PRD (X11
AgentCharset ibm866 DosLynx

Vse Pattern yavlyayutsya podstrokami, a ne regexp vyrazheniyami.

BadAgent

Nekotorye klientskie programmy ne mogut adekvatno reagirovat' na MIME, naprimer pri poluchenii zagolovka

Content-type: text/html; charset=koi8-r; level=3

CHtoby server ne vydaval takim klientskim programmam charset=... sluzhit eta direktiva. Sintaksis:

BadAgent Pattern1 Pattern2 Pattern3 ...

Pattern1 Pattern2 ...: Podstroka v pole User-agent zaprosa klienta, pri nahozhdenii kotoroj server budet vozderzhivat'sya ot vydachi charset=...
Primer:: BadAgent lynx arena

Vse Pattern yavlyayutsya podstrokami, a ne regexp vyrazheniyami.

RejectErrorCharset

Direktiva sluzhit dlya opredeleniya serverom dejstvij pri poluchinii v zaprose klienta neizvestnogo charset. Sintaksis:

RejectErrorCharset On/Off

Pri ustanovke etogo parametra v On server ne budet vydavat' dokument v native charset, a budet soobshchat' klientu ob oshibke v zaprose. Pri ustanovke v Off - v lyubom sluchae vydast dokument kak smozhet. Znachenie po-umolchaniyu Off.

NoHostnameCharset

Po umolchaniyu, esli klientom ne zaproshena konkretnaya code page server pytaetsya ee opredelit' po svoemu imeni, naprimer: win.www.company.com. Dannaya direktiva pozvolyaet zapretit' serveru iskat' trebuemyj klientu charset v svoem imeni. Sintaksis:

NoHostnameCharset On/Off

Znachenie po-umolchaniyu Off.

NoUriCharset

Direktiva pozvolyaet zapretit' serveru opredelyat' trebuemyj klientu charset iz URI. Konkretnyj primer, po umolchaniyu server schitaet chto dokumenty tipa:

http://www.company.com/win/name.html

sleduet vydavat' v kodirovke windows-1251. Ispol'zovanie direktivy:

NoUriCharset On

zastavit server vydat' etot dokument v native code page.

CharsetAgentPriority

Opredelyaet prioritetnost' pri poiske neobhodimogo charset serverom mezhdu URL i User-Agent. Sintaksis:

CharsetAgentPriority On/Off

Pri ustanovke etogo parametra v On server v pervuyu ochered' budet smotret' na pole User-Agent. I esli v etom pole on najdet izvestnyj emu shablon, to primet reshenie o skonfigurirovannom charset soglasno direktivam AgentCharset. Esli zhe shablon ne budet najden - server popytaetsya najti imya charset v preffikse imeni virtual'nogo servera, k kotoromu obrashchen zapros i/ili v preffikse zatrebovannogo URI.
Pri ustanovke v Off (eto znachenie po-umolchaniyu) - naoborot.

5. Nekotorye rekomendacii

Tak kak server naryadu s soglasovaniem charset ispol'zuet i soglasovaniya po language, ya rekomenduyu chtoby dokumenty, soderzhashchie ne tol'ko anglijskie simvoly (ISO8859-1) nazyvalis' v sootvetstvii so svoej yazykovoj prinadlezhnost'yu. Standartnym dlya Apache yavlyaetsya dobavlenie dvuhbukvennogo koda v konec imeni fajla, naprimer:
Esli u vas est' dokumenty, perevedennye na raznye yazyki, eto takzhe budet polezno klientskim programmam dlya soglasovaniya language. Nekotorye programmy umeyut v zaprose posylat' zagolovki tipa:
Krome togo, pri ispol'zovanii pravil'nyh yazykovyh rasshirenij fajlov vash server na russkoyazychnye dokumenty budet vydavat' charset=... i v sluchae teoreticheskoj vozmozhnosti vydachi dannogo dokumenta v drugom charset, server budet dobavlyat' zagolovok Expires: current_date_time, chto predupredit proxy servera o nezhelatel'nosti osedaniya dannogo dokumenta v kesh proxy servera. Ne sleduet boyat'sya togo, chto v takom sluchae pridetsya perepisyvat' perekrestnye ssylki vo vseh dokumentah. |to ne tak. Esli na servere lezhit dokument s imenem file.html.ru, to na zapros klienta
```
GET /file.html
```
Server smozhet najti sootvetstvuyushchij file.html.ru. Pravda dlya etogo neobhodimo pri opisanii domashnej direktorii servera v fajle conf/access.conf dopolnit' Options ... MultiViews. Naprimer:
```
<Directory /usr/local/etc/httpd/home>

# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".

# Note that "MultiViews" must be named *explicitly* - "Options All"
# doesn't give it to you (or at least, not yet).

Options Indexes FollowSymLinks Includes MultiViews

</Directory>
```
Esli na Vashem servere bol'shaya chast' dokumentov russkoyazychnaya, ya rekomenduyu dobavit' v conf/srm.conf stroku
```
AddLanguage ru .html .ru
```
Pri etom budet vydavat'sya charset=... dlya vseh dokumentov *.html, krome dokumentov, prinadlezhashchih k drugim yazykam.
Esli u Vas imeetsya vozmozhnost' ispol'zovat' razlichnye IP adresa dlya raznyh virtual'nyh serverov, ya takzhe rekomenduyu eto delat', t.k. po sravneniyu s razdeleniem kodirovok po portam eto potrebuet men'she resursov ot komp'yutera. Optimal'naya na moj vzglyad konfiguraciya sleduyushchaya:
- Bazovyj server www.company.name.ru skonfigurirovan tak, chto on znaet obo vseh vozmozhnyh charset i ih psevdonimah. Krome togo on znaet o vseh User-agent i sootvetstvuyushchih im charsets po-umolchaniyu. |tot server v kachestve NativeCharset dolzhen imet' rodnuyu kodirovku dokumentov. Takoj server smozhet vypolnit' samyj zamyslovatyj zapros. No budet protivodejstvovat' proxy serveram sohranyat' dokumenty v kesh.
- Virtual'nye servera, naprimer windows-1251.company.name.ru ili koi8-r.company.name.ru budut znat' tol'ko ob odnoj kodovoj stranice i vsegda vydavat' dokumenty v nej vne zavisimosti ot User-agent. |to ne budet meshat' proxy serveram sohranyat' takie dokumenty.
- V sochetanii 2 predydushchih punktov i pravil'no postroiv derevo dokumentov mozhno budet udovletvorit' lyubye potrednosti klientov.
Esli net vozmozhnosti ispol'zovat' virtual'nye servera, ya rekomenduyu vystroit' derevo russkoyazychnyh dokumentov v otdel'noj direktorii, naprimer /koi8-r/, v kotoroj dokumenty hranyatsya v native charset. Posle etogo mozhno sdelat' simvolicheskie ssylki tipa:
```
ln -s home_of_server/koi8-r home_of_server/windows-1251
ln -s home_of_server/koi8-r home_of_server/ibm866
```
ili chto-to podobnoe. Dokumenty v etih direktoriyah budut postupat' k klientu v kodirovke, ukazannoj v preffikse. Nado pomnit', chto v etom sluchae perekrestnye ssylki v takom dereve ne dolzhny soderzhat' absolyutnogo puti, a ukazyvat' vse vremya ot tekushchego polozheniya dokumenta. Odnako, esli dokument soderzhit v sebe SSI, naprimer:
```
<!-#include virtual="/~dvk/cgi-bin/a.cgi"->
```
rezul'tat raboty a.cgi vklyuchennyj serverom v dokument budet takzhe priveden k vybrannomu serverom charset, nesmotrya na to, chto sam a.cgi ne nahoditsya v dereve.
|tot sposob teper' takzhe goditsya i dlya direktorij pol'zovatelej, t.e. /~user/win/file.html budet vydavat'sya v windows-1251.

Blagodarnosti

Alexander Ermolaev <ae@mark-itt.ru>
Alex Tutubalin <lexa@lexa.ru>
Andrew Maltsev <am@f1.ru>
Andrey Gerasimov <andy@netclub.ru>
Dima Antipov <dima@elvis.msk.su>
Dmitry A.Deineka <axl@infocom.kharkov.ua>
Igor V. Semenyuk <iga@sovam.com>
Nickolay Saukh <nms@nns.ru>
Paul S. Hrobostov <hps@rp3.jetinf.ru>
Plechov P.Yu <lym@sunny.ccas.ru>
Prof. S.D.F. <sdf@lx.ispm.ac.ru>
Stanislav Sinyagin <stas@isf.ru>
Vladislav A. Chekalov <CHV@nhb.ru>

Apache HTTP server LICENSE

/* ====================================================================
 * Copyright (c) 1995 The Apache Group.  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. All advertising materials mentioning features or use of this
 *    software must display the following acknowledgment:
 *    "This product includes software developed by the Apache Group
 *    for use in the Apache HTTP server project (http://www.apache.org/)."
 *
 * 4. The names "Apache Server" and "Apache Group" must not be used to
 *    endorse or promote products derived from this software without
 *    prior written permission.
 *
 * 5. Redistributions of any form whatsoever must retain the following
 *    acknowledgment:
 *    "This product includes software developed by the Apache Group
 *    for use in the Apache HTTP server project (http://www.apache.org/)."
 *
 * THIS SOFTWARE IS PROVIDED BY THE APACHE GROUP ``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 GROUP 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 Group and was originally based
 * on public domain software written at the National Center for
 * Supercomputing Applications, University of Illinois, Urbana-Champaign.
 * For more information on the Apache Group and the Apache HTTP server
 * project, please see .
 *
 */


Last-modified: Fri, 28 Feb 1997 23:31:58 GMT
Ocenite etot tekst: