Mercurial > hg > nginx-site
changeset 121:49443032011c
Unified <section> syntax for "article" and "module" documents.
line wrap: on
line diff
--- a/dtd/content.dtd +++ b/dtd/content.dtd @@ -1,8 +1,8 @@ <!ELEMENT section (para | list | book | download | security | note | programlisting)* > <!ATTLIST section - name ID #IMPLIED - title CDATA #IMPLIED + id ID #IMPLIED + name CDATA #IMPLIED > <!ELEMENT para (#PCDATA | a | link | br | list | orderedlist | note |
--- a/xml/en/docs/freebsd_tuning.xml +++ b/xml/en/docs/freebsd_tuning.xml @@ -5,7 +5,7 @@ lang="en"> -<section title="Syncache and syncookies"> +<section name="Syncache and syncookies"> <para> We look at how various kernel settings affect ability of the kernel @@ -19,8 +19,8 @@ to process requests. Let’s start w </section> -<section name="listen_queues" - title="Listen queues"> +<section id="listen_queues" + name="Listen queues"> <para> After the connection has been established it is placed in the listen queue @@ -83,8 +83,8 @@ By default nginx uses the maximum value </section> -<section name="sockets_and_files" - title="Sockets and files"> +<section id="sockets_and_files" + name="Sockets and files"> <para> [ sockets, files ] @@ -93,8 +93,8 @@ By default nginx uses the maximum value </section> -<section name="socket_buffers" - title="Socket buffers"> +<section id="socket_buffers" + name="Socket buffers"> <para> When a client sends a data, the data first is received by the kernel @@ -144,8 +144,8 @@ therefore it does not require the large </section> -<section name="mbufs" - title="mbufs, mbuf clusters, etc."> +<section id="mbufs" + name="mbufs, mbuf clusters, etc."> <para> Inside the kernel the buffers are stored in the form of chains of @@ -317,8 +317,8 @@ sysctl net.inet.ip.intr_queue_maxlen=204 </section> -<section name="proxying" - title="Proxying"> +<section id="proxying" + name="Proxying"> <programlisting> @@ -330,8 +330,8 @@ net.inet.ip.portrange.last=65535 </section> -<section name="finalizing_connection" - title="Finalizing connection"> +<section id="finalizing_connection" + name="Finalizing connection"> <programlisting> net.inet.tcp.fast_finwait2_recycle=1 @@ -340,8 +340,8 @@ net.inet.tcp.fast_finwait2_recycle=1 </section> -<section name="i386_specific_tuning" - title="i386 specific tuning"> +<section id="i386_specific_tuning" + name="i386 specific tuning"> <para> [ KVA, KVM, nsfbufs ] @@ -350,8 +350,8 @@ net.inet.tcp.fast_finwait2_recycle=1 </section> -<section name="minor_optmizations" - title="Minor optimizations"> +<section id="minor_optmizations" + name="Minor optimizations"> <para>
--- a/xml/en/docs/howto_build_on_win32.xml +++ b/xml/en/docs/howto_build_on_win32.xml @@ -6,7 +6,7 @@ link="/en/docs/howto_build_on_win32.html" lang="en"> -<section title="Prerequisites"> +<section name="Prerequisites"> <para> To build nginx on the Microsoft Win32® platform you need: @@ -42,8 +42,8 @@ and <link url="http://www.openssl.org">O </section> -<section name="build_steps" - title="Build steps"> +<section id="build_steps" + name="Build steps"> <para> Ensure that paths to Perl, Subversion and MSYS bin directories are added to @@ -107,8 +107,8 @@ nmake -f objs/Makefile </section> -<section name="see_also" - title="See also"> +<section id="see_also" + name="See also"> <para> <list>
--- a/xml/en/docs/http/configuring_https_servers.xml +++ b/xml/en/docs/http/configuring_https_servers.xml @@ -66,7 +66,7 @@ Configuration of ciphers can be adjusted </section> -<section name="optimization" title="HTTPS server optimization"> +<section id="optimization" name="HTTPS server optimization"> <para> SSL operations consume extra CPU resources. @@ -109,7 +109,7 @@ http { </section> -<section name="chains" title="SSL certificate chains"> +<section id="chains" name="SSL certificate chains"> <para> Some browsers may complain about a certificate signed by a well-known @@ -206,7 +206,7 @@ certificate #0. </section> -<section name="single_http_https_server" title="A single HTTP/HTTPS server"> +<section id="single_http_https_server" name="A single HTTP/HTTPS server"> <para> It is good practice to configure separate servers for HTTP and HTTPS @@ -242,7 +242,7 @@ listen 443 default ssl; </section> -<section name="name_based_https_servers" title="Name-based HTTPS servers"> +<section id="name_based_https_servers" name="Name-based HTTPS servers"> <para> A common issue arises when configuring two or more HTTPS servers @@ -300,8 +300,8 @@ server { </section> -<section name="certificate_with_several_names" - title="A SSL certificate with several names"> +<section id="certificate_with_several_names" + name="A SSL certificate with several names"> <para> There are other ways to share a single IP address between several @@ -349,7 +349,7 @@ server { </section> -<section name="sni" title="Server Name Indication"> +<section id="sni" name="Server Name Indication"> <para> A more generic solution for running several HTTPS servers on a single @@ -417,7 +417,7 @@ therefore SNI is not available </section> -<section name="compatibility" title="Compatibility"> +<section id="compatibility" name="Compatibility"> <para> <list>
--- a/xml/en/docs/http/converting_rewrite_rules.xml +++ b/xml/en/docs/http/converting_rewrite_rules.xml @@ -5,7 +5,7 @@ lang="en"> -<section title="A redirect to a main site"> +<section name="A redirect to a main site"> <para> People who during their shared hosting life used to configure @@ -103,8 +103,8 @@ On versions prior to 0.9.1, redirects ca </section> -<section name="converting_mongrel_rules" - title="Converting Mongrel rules"> +<section id="converting_mongrel_rules" + name="Converting Mongrel rules"> <para> Typical Mongrel rules:
--- a/xml/en/docs/http/request_processing.xml +++ b/xml/en/docs/http/request_processing.xml @@ -7,7 +7,7 @@ editor="Brian Mercer"> -<section title="Name-based virtual servers"> +<section name="Name-based virtual servers"> <para> nginx first decides which <i>server</i> should process the request. @@ -69,8 +69,8 @@ and not of the server name. More about t </section> -<section name="how_to_prevent_undefined_server_names" - title="How to prevent processing requests with undefined server names"> +<section id="how_to_prevent_undefined_server_names" + name="How to prevent processing requests with undefined server names"> <para> If you do not want to process requests without the <header>Host</header> @@ -97,8 +97,8 @@ a default server name. </section> -<section name="mixed_name_ip_based_servers" - title="Mixed name-based and IP-based virtual servers"> +<section id="mixed_name_ip_based_servers" + name="Mixed name-based and IP-based virtual servers"> <para> Let’s look at a more complex configuration @@ -167,8 +167,8 @@ server { </section> -<section name="simple_php_site_configuration" - title="A simple PHP site configuration"> +<section id="simple_php_site_configuration" + name="A simple PHP site configuration"> <para> Now let’s look at how nginx chooses a <i>location</i> to process a request
--- a/xml/en/docs/http/server_names.xml +++ b/xml/en/docs/http/server_names.xml @@ -68,8 +68,8 @@ The first match stops the search. </section> -<section name="wildcard_names" - title="Wildcard names"> +<section id="wildcard_names" + name="Wildcard names"> <para> A wildcard name may contain an asterisk only on the name's start or end, @@ -92,8 +92,8 @@ and the wildcard name <dirname>*.nginx.o </section> -<section name="regex_names" - title="Regular expressions names"> +<section id="regex_names" + name="Regular expressions names"> <para> The regular expressions used by nginx are compatible with those used @@ -184,8 +184,8 @@ since the digital references can easily </section> -<section name="miscellaneous_names" - title="Miscellaneous names"> +<section id="miscellaneous_names" + name="Miscellaneous names"> <para> If you want to process requests without a “Host” header line @@ -281,8 +281,8 @@ server { </section> -<section name="optimization" - title="Optimization"> +<section id="optimization" + name="Optimization"> <para> Exact names and wildcard names are stored in hashes. @@ -382,8 +382,8 @@ then nginx has to execute the expression </section> -<section name="compatibility" - title="Compatibility"> +<section id="compatibility" + name="Compatibility"> <para> <list>
--- a/xml/en/docs/index.xml +++ b/xml/en/docs/index.xml @@ -37,7 +37,7 @@ </section> -<section title="Modules reference"> +<section name="Modules reference"> <para> <list>
--- a/xml/en/docs/windows.xml +++ b/xml/en/docs/windows.xml @@ -103,8 +103,8 @@ quitting an old worker gracefully </section> -<section name="known_issues" - title="Known issues"> +<section id="known_issues" + name="Known issues"> <list> @@ -126,8 +126,8 @@ address space layout randomization being </section> -<section name="possible_future_enhancements" - title="Possible future enhancements"> +<section id="possible_future_enhancements" + name="Possible future enhancements"> <list>
--- a/xml/en/download.xml +++ b/xml/en/download.xml @@ -5,7 +5,7 @@ lang="en"> -<section title="Development versions"> +<section name="Development versions"> <download last="5" changes="CHANGES"> @@ -22,7 +22,7 @@ </section> -<section title="Stable versions"> +<section name="Stable versions"> <download last="5" changes="CHANGES-1.0"> @@ -49,7 +49,7 @@ </section> -<section title="Legacy versions"> +<section name="Legacy versions"> <download last="1" changes="CHANGES-0.8">
--- a/xml/en/index.xml +++ b/xml/en/index.xml @@ -33,8 +33,8 @@ The sources are distributed under the </section> -<section name="basic_http_features" - title="Basic HTTP server features"> +<section id="basic_http_features" + name="Basic HTTP server features"> <para> <list> @@ -73,8 +73,8 @@ SSL and TLS SNI support. </section> -<section name="other_http_features" - title="Other HTTP server features"> +<section id="other_http_features" + name="Other HTTP server features"> <para> <list> @@ -150,8 +150,8 @@ Embedded Perl. </section> -<section name="mail_proxy_server_features" - title="Mail proxy server features"> +<section id="mail_proxy_server_features" + name="Mail proxy server features"> <para> <list> @@ -200,8 +200,8 @@ STARTTLS and STLS support. </section> -<section name="architecture_and_scalability" - title="Architecture and scalability"> +<section id="architecture_and_scalability" + name="Architecture and scalability"> <para> <list> @@ -258,8 +258,8 @@ Data copy operations are kept to a minim </section> -<section name="tested_os_and_platforms" - title="Tested OS and platforms"> +<section id="tested_os_and_platforms" + name="Tested OS and platforms"> <para> <list>
--- a/xml/en/links.xml +++ b/xml/en/links.xml @@ -4,7 +4,7 @@ link="/en/links.html" lang="en"> -<section title="nginx internals"> +<section name="nginx internals"> <para> <list> @@ -25,7 +25,7 @@ Advanced Topics In Nginx Module Developm </section> -<section title="miscellanea"> +<section name="miscellanea"> <para> <list>
--- a/xml/en/support.xml +++ b/xml/en/support.xml @@ -5,7 +5,7 @@ lang="en"> -<section title="Wiki"> +<section name="Wiki"> <para> <list> @@ -20,7 +20,7 @@ </section> -<section title="Mailing Lists"> +<section name="Mailing Lists"> <para> You can @@ -62,7 +62,7 @@ Gmane archive</a> </section> -<section title="Forums"> +<section name="Forums"> <para> <list> @@ -86,7 +86,7 @@ mailing list integration) </section> -<section title="Development"> +<section name="Development"> <para> <list>
--- a/xml/he/docs/http/converting_rewrite_rules.xml +++ b/xml/he/docs/http/converting_rewrite_rules.xml @@ -6,7 +6,7 @@ author="Igor Sysoev" translator="מבזקים.נט"> -<section title="הפנייה לאתר ראשי"> +<section name="הפנייה לאתר ראשי"> <para> משתמשים שבמהלך חיי האירוח המשותף נהגו להגדיר <i>הכל</i> באמצעות @@ -87,8 +87,8 @@ server { </section> -<section name="converting_mongrel_rules" - title="המרת כללי Mongrel"> +<section id="converting_mongrel_rules" + name="המרת כללי Mongrel"> <para> כללי Mongrel טיפוסיים:
--- a/xml/he/docs/http/server_names.xml +++ b/xml/he/docs/http/server_names.xml @@ -67,8 +67,8 @@ server { </section> -<section name="wildcard_names" - title="שמות Wildcard"> +<section id="wildcard_names" + name="שמות Wildcard"> <para> שם wildcard יכול להכיל כוכבית רק בתחילת או בסוף השם, וחייב להיות בגבול של נקודה. @@ -91,8 +91,8 @@ server { </section> -<section name="regex_names" - title="שמות ביטויים רגולריים"> +<section id="regex_names" + name="שמות ביטויים רגולריים"> <para> הביטויים הרגולריים ש nginx משתמש בהם, תואמים לאלה אשר נמצאים בשימוש @@ -184,8 +184,8 @@ server { </section> -<section name="miscellaneous_names" - title="שמות כלליים"> +<section id="miscellaneous_names" + name="שמות כלליים"> <para> אם אף <dirname>server_name</dirname> לא מוגדר בבלוג שרת, @@ -277,8 +277,8 @@ server { </section> -<section name="optimization" - title="ייעול"> +<section id="optimization" + name="ייעול"> <para> @@ -372,8 +372,8 @@ nginx חייב לבצע את הביטוי כדי לקבל את מה שנלכד בהן. </section> -<section name="compatibility" - title="תאימות"> +<section id="compatibility" + name="תאימות"> <para> <list>
--- a/xml/he/docs/windows.xml +++ b/xml/he/docs/windows.xml @@ -95,8 +95,8 @@ nginx/Windows רץ כיישום קונסול סטנדרטי, ולא כשירות (service) במערכת, </section> -<section name="known_issues" - title="בעיות ידועות"> +<section id="known_issues" + name="בעיות ידועות"> <list> @@ -118,8 +118,8 @@ nginx/Windows רץ כיישום קונסול סטנדרטי, ולא כשירות (service) במערכת, </section> -<section name="possible_future_enhancements" - title="שיפורים עתידיים אפשריים"> +<section id="possible_future_enhancements" + name="שיפורים עתידיים אפשריים"> <list>
--- a/xml/he/index.xml +++ b/xml/he/index.xml @@ -29,8 +29,8 @@ nginx [נהגה: engine x] הוא שרת HTTP ופרוקסי הפוך, כמו גם שרת פרוקסי לדואר, </section> -<section name="basic_http_features" - title="תכונות HTTP בסיסיות"> +<section id="basic_http_features" + name="תכונות HTTP בסיסיות"> <para> <list> @@ -67,8 +67,8 @@ nginx [נהגה: engine x] הוא שרת HTTP ופרוקסי הפוך, כמו גם שרת פרוקסי לדואר, </section> -<section name="other_http_features" - title="תכונות HTTP אחרות"> +<section id="other_http_features" + name="תכונות HTTP אחרות"> <para> <list> @@ -132,8 +132,8 @@ perl משובץ. </section> -<section name="mail_proxy_server_features" - title="תכונות פרוקסי דואר"> +<section id="mail_proxy_server_features" + name="תכונות פרוקסי דואר"> <para> <list> @@ -180,8 +180,8 @@ SMTP: AUTH LOGIN/PLAIN/CRAM-MD5; </section> -<section name="architecture_and_scalability" - title="ארכיטקטורה ויכולת גידול"> +<section id="architecture_and_scalability" + name="ארכיטקטורה ויכולת גידול"> <para> <list> @@ -231,8 +231,8 @@ 12.5M; </section> -<section name="tested_os_and_platforms" - title="מערכות הפעלה ופלטפורמות בדוקות"> +<section id="tested_os_and_platforms" + name="מערכות הפעלה ופלטפורמות בדוקות"> <para> <list>
--- a/xml/ja/docs/http/configuring_https_servers.xml +++ b/xml/ja/docs/http/configuring_https_servers.xml @@ -41,7 +41,7 @@ SSL プロトコルの強力なバージョンと暗号に接続を制限するには、ディレクティブ <dirname>ssl_protocols</dirname> と <dirname>ssl_ciphers</dirname> を使用します。バージョン 0.8.20 以降、nginx は <dirname>ssl_protocols SSLv3 TLSv1</dirname> と <dirname>ssl_ciphers HIGH:!ADH:!MD5</dirname> をデフォルトとして使用しているので、これより古い nginx のバージョンでのみ設定してください。 </section> -<section name="optimization" title="HTTPS サーバの最適化"> +<section id="optimization" name="HTTPS サーバの最適化"> <para> SSL の工程は CPU リソースを余計に消費します。マルチプロセッサシステムでは（利用できる CPU コアの数よりも大きい数の）複数のワーカープロセスを走らせるといいでしょう。最も CPU に負荷がかかる工程は SSL ハンドシェイクです。クライアント毎のこの工程数を最小化するには２つの方法があります。最初の方法はキープアライブ接続を有効にして、ひとつの接続経由で複数のリクエストを送るようにする方法です。二つ目の方法は SSL セッションパラメータを再利用して、並行かつ順次接続のための SSL ハンドシェイクを避ける方法です。セッションはワーカー間で共有される SSL セッションキャッシュに保持され、<dirname>ssl_session_cache</dirname> ディレクティブで設定されています。１メガバイトのキャッシュには約４０００のセッションが含まれます。キャッシュのデフォルトタイムアウトは５分です。この値は <dirname>ssl_session_timeout</dirname> ディレクティブを使用して増やすことができます。次の例は１０Mの共有セッションキャッシュをもったクアッドコアシステムに最適化された設定例です: @@ -71,7 +71,7 @@ http { </section> -<section name="chains" title="SSL 連鎖証明書"> +<section id="chains" name="SSL 連鎖証明書"> <para> ブラウザによっては有名な認証局によって署名された証明書にエラーをだすことがあります。その一方でその証明書を他のブラウザでは問題なく受け入れることもあります。これは発行している認証局が、有名で信用されている認証局の認証基盤には含まれない特定のブラウザで配布されている中間証明書を使ったサーバ証明書に署名しているからです。このケースでは、認証局は署名されたサーバ証明書に連結されているはずの連鎖証明書のバンドルを提供しています。サーバ証明書は、かならず結合されたファイル内の連鎖証明書に存在している必要があります: @@ -143,7 +143,7 @@ Certificate chain </section> -<section name="single_http_https_server" title="単一の HTTP/HTTPS サーバ"> +<section id="single_http_https_server" name="単一の HTTP/HTTPS サーバ"> <para> 最初の段階から HTTP と HTTPS プロトコル用にサーバを分けて設定するのは優れた実践です。現時点では両者の機能性としては等しいかもしれませんが、将来的に大きな変更があるかもしれず、統合されたサーバの使用が問題になるかもしれません。とはいえ、HTTP と HTTPS のサーバが等しく、将来のことを考えたくないのなら、ディレクティブ <dirname>ssl on</dirname> を削除して *:443 ポートに <dirname>ssl</dirname> パラメータを追加することによって HTTP と HTTPS リクエストの両者を扱う単一のサーバを設定することができます: @@ -170,7 +170,7 @@ listen 443 default ssl; </section> -<section name="name_based_https_servers" title="名前ベースの HTTPS サーバ"> +<section id="name_based_https_servers" name="名前ベースの HTTPS サーバ"> <para> 単一の IP アドレスを２つ以上の HTTPS サーバで待ち受けるように設定するとよく発生する問題があります: @@ -221,8 +221,8 @@ server { </section> -<section name="certificate_with_several_names" - title="複数サーバ名をもつ SSL 証明書"> +<section id="certificate_with_several_names" + name="複数サーバ名をもつ SSL 証明書"> <para> 単一の IP アドレスを複数の HTTPS サーバ間で共有する方法は他にもありますが、どれも欠点があります。ひとつは、SubjectAltName フィールドに複数サーバ名（例えば、<url>www.nginx.com</url> と <url>www.nginx.org</url>）をもつ単一の証明書を使用する方法です。しかし、SubjectAltName の長さには制限があります。 @@ -258,7 +258,7 @@ server { </section> -<section name="sni" title="サーバ名指示（Server Name Indication – SNI）"> +<section id="sni" name="サーバ名指示（Server Name Indication – SNI）"> <para> 単一の IP アドレス上で複数の HTTPS サーバを動かすときのさらに包括的な解決方法として <a href="http://en.wikipedia.org/wiki/Server_Name_Indication">TLSv1.1 Server Name Indication extension（サーバ名指示拡張）</a> (SNI, RFC3546) があります。これは、ブラウザが SSL ハンドシェイクの間にリクエストされたサーバ名を渡せるようにするもので、それによりサーバはその接続でどの証明書を使用するべきかが分かります。しかし、SNI は限られたブラウザしかサポートしていません。現時点では次のブラウザのバージョン以降のものがサポートされています: @@ -310,7 +310,7 @@ therefore SNI is not available </section> -<section name="compatibility" title="Compatibility"> +<section id="compatibility" name="Compatibility"> <para> <list>
--- a/xml/ja/docs/http/converting_rewrite_rules.xml +++ b/xml/ja/docs/http/converting_rewrite_rules.xml @@ -4,7 +4,7 @@ link="/ja/docs/http/converting_rewrite_rules.html" lang="ja"> -<section title="メインサイトへのリダイレクト"> +<section name="メインサイトへのリダイレクト"> <para> 共有のホスティングで Apache の .htaccess ファイル<i>のみ</i>で<i>すべて</i>を設定してきたのなら、次のようにルールをコンバートします: @@ -81,8 +81,8 @@ server { </section> -<section name="converting_mongrel_rules" - title="Mongrel ルールのコンバート"> +<section id="converting_mongrel_rules" + name="Mongrel ルールのコンバート"> <para> 典型的な Mongrel のルール:
--- a/xml/ja/docs/http/request_processing.xml +++ b/xml/ja/docs/http/request_processing.xml @@ -6,7 +6,7 @@ author="Igor Sysoev" translator="DigitalCube Co. Ltd., wokamoto"> -<section title="名前ベースの仮想サーバ"> +<section name="名前ベースの仮想サーバ"> <para> nginx はまず最初にどの<i>サーバ</i>がそのリクエストを処理すべきなのかを決定します。手はじめに、３つすべての仮想サーバが port *:80 で待ち受けている単純な設定から見てみましょう: @@ -53,8 +53,8 @@ server { </section> -<section name="how_to_prevent_undefined_server_names" - title="サーバ名未定義のリクエストの処理を防ぐ"> +<section id="how_to_prevent_undefined_server_names" + name="サーバ名未定義のリクエストの処理を防ぐ"> <para> “Host” ヘッダが未定義のリクエストを処理させたくない場合は、リクエストを単にドロップさせるデフォルトサーバを設定できます: @@ -73,8 +73,8 @@ server { </section> -<section name="mixed_name_ip_based_servers" - title="名前ベースとIPベースをミックスした仮想サーバ"> +<section id="mixed_name_ip_based_servers" + name="名前ベースとIPベースをミックスした仮想サーバ"> <para> 異なるアドレスで待ち受けている仮想サーバのより複雑な設定をみてみましょう: @@ -131,8 +131,8 @@ server { </section> -<section name="simple_php_site_configuration" - title="単純な PHP サイトの設定"> +<section id="simple_php_site_configuration" + name="単純な PHP サイトの設定"> <para> では、典型的で単純な PHP サイトで nginx がどのように<i>ロケーション（location）</i>を選択してリクエストを処理するのかを見てみましょう:
--- a/xml/ja/docs/http/server_names.xml +++ b/xml/ja/docs/http/server_names.xml @@ -64,8 +64,8 @@ server { </section> -<section name="wildcard_names" - title="ワイルドカード名"> +<section id="wildcard_names" + name="ワイルドカード名"> <para> ワイルドカード名にはそのサーバ名の最初か最後のみ、そしてドットに隣接したところのみにアスタリスクが含まれます。サーバ名 <dirname>www.*.nginx.org</dirname> や <dirname>w*.nginx.org</dirname> は無効です。しかし、これらのサーバ名は正規表現を使用して、例えば <dirname>~^www\..+\.nginx\.org$</dirname> や <dirname>~^w.*\.nginx\.org$</dirname> として指定することができます。アスタリスクは複数部分にマッチさせることができます。<dirname>*.nginx.org</dirname> は <url>www.nginx.org</url> だけでなく <url>www.sub.nginx.org</url> にもマッチします。 @@ -78,8 +78,8 @@ server { </section> -<section name="regex_names" - title="正規表現名"> +<section id="regex_names" + name="正規表現名"> <para> nginx で使用される正規表現は Perl プログラミング言語（PCRE）で使用されているものと互換性があります。正規表現を使用するには、サーバ名を必ずチルダで始めます: @@ -158,8 +158,8 @@ server { </section> -<section name="miscellaneous_names" - title="その他のサーバ名"> +<section id="miscellaneous_names" + name="その他のサーバ名"> <para> デフォルトではないサーバブロックで “Host” ヘッダ無しのリクエストを処理させたい場合は、空のサーバ名を指定します: @@ -237,8 +237,8 @@ server { </section> -<section name="optimization" - title="最適化"> +<section id="optimization" + name="最適化"> <para> 完全一致名とワイルドカード名はハッシュで保存されます。このハッシュは待ち受けポートに結び付けられ、各待ち受けポートは、完全一致名のハッシュ、アスタリスクで始まるワイルドカード名のハッシュ、アスタリスクで終わるワイルドカード名のハッシュの３つまでのハッシュを持つことができます。ハッシュのサイズは構成フェーズで最適化されるので、CPU キャッシュのミスは最低でもサーバ名を見つけることができます。最初に完全一致名のハッシュが検索されます。完全一致名のハッシュを使って見つからなければ、次にアスタリスクで始まるワイルドカード名のハッシュが検索されます。さらにまだ見つからなければ、アスタリスクで終わるワイルドカード名のハッシュが検索されます。ワイルドカード名のハッシュの検索は完全一致名のハッシュの検索よりも遅くなります。これはサーバ名の検索がドメイン部分によって検索されるからです。特別なワイルドカード形式の <dirname>.nginx.org</dirname> は完全一致名のハッシュではなくワイルドカード名のハッシュで保存されます。正規表現は順番に考査されるので、これがもっとも遅い方式ですし、非スケーラブルでもあります。 @@ -300,8 +300,8 @@ or server_names_hash_bucket_size: 32 </section> -<section name="compatibility" - title="互換性"> +<section id="compatibility" + name="互換性"> <para> <list>
--- a/xml/ja/index.xml +++ b/xml/ja/index.xml @@ -20,8 +20,8 @@ nginx [えんじんえっくす] は <a href="http://sysoev.ru/en/">Igor Sysoev</a> によって作られた HTTP とリバースプロキシのサーバで、メールプロキシサーバでもあります。<a href="http://www.rambler.ru">Rambler</a> </section> -<section name="basic_http_features" - title="基本的な HTTP 機能"> +<section id="basic_http_features" + name="基本的な HTTP 機能"> <para> <list> @@ -52,8 +52,8 @@ SSL と TLS SNI サポート。 </section> -<section name="other_http_features" - title="他の HTTP 機能"> +<section id="other_http_features" + name="他の HTTP 機能"> <para> <list> @@ -116,8 +116,8 @@ FLV ストリーミング </section> -<section name="mail_proxy_server_features" - title="メールプロキシサーバ機能"> +<section id="mail_proxy_server_features" + name="メールプロキシサーバ機能"> <para> <list> @@ -164,8 +164,8 @@ STARTTLS と STLS のサポート </section> -<section name="architecture_and_scalability" - title="アーキテクチャとスケーラビリティ"> +<section id="architecture_and_scalability" + name="アーキテクチャとスケーラビリティ"> <para> <list> @@ -208,8 +208,8 @@ 1 万の非アクティブな HTTP キープアライブ接続は約 2.5M のメモリーを使用 </section> -<section name="tested_os_and_platforms" - title="テスト済み OS とプラットフォーム"> +<section id="tested_os_and_platforms" + name="テスト済み OS とプラットフォーム"> <para> <list>
--- a/xml/ru/docs/control.xml +++ b/xml/ru/docs/control.xml @@ -47,7 +47,7 @@ </section> -<section title="Изменение конфигурации" name="reconfiguration"> +<section id="reconfiguration" name="Изменение конфигурации"> <para> Для того, чтобы nginx перечитал файл конфигурации, нужно послать @@ -104,7 +104,7 @@ 33136 33126 nobody 0.0 1368 kqread ng </section> -<section title="Ротация лог-файлов" name="logs"> +<section id="logs" name="Ротация лог-файлов"> <para> Лог-файлы нужно переименовать, а затем послать сигнал USR1 главному процессу. @@ -121,7 +121,7 @@ 33136 33126 nobody 0.0 1368 kqread ng </section> -<section title="Обновление сервера на лету" name="upgrade"> +<section id="upgrade" name="Обновление сервера на лету"> <para> Для обновления сервера нужно записать на место старого исполняемого файла новый.
--- a/xml/ru/docs/index.xml +++ b/xml/ru/docs/index.xml @@ -73,7 +73,7 @@ </section> -<section title="Справочник по модулям"> +<section name="Справочник по модулям"> <para> <list>
--- a/xml/ru/download.xml +++ b/xml/ru/download.xml @@ -4,7 +4,7 @@ link="/ru/download.html" lang="ru"> -<section title="Текущие версии"> +<section name="Текущие версии"> <download last="5" changes="CHANGES.ru"> @@ -21,7 +21,7 @@ </section> -<section title="Стабильные версии"> +<section name="Стабильные версии"> <download last="5" changes="CHANGES.ru-1.0"> @@ -48,7 +48,7 @@ </section> -<section title="Устаревшие версии"> +<section name="Устаревшие версии"> <download last="1" changes="CHANGES.ru-0.8">
--- a/xml/ru/index.xml +++ b/xml/ru/index.xml @@ -33,8 +33,8 @@ nginx [engine x]—это HTTP-сервер и обратный прокси-сервер, </section> -<section name="basic_http_features" - title="Основная функциональность HTTP-сервера"> +<section id="basic_http_features" + name="Основная функциональность HTTP-сервера"> <para> <list> @@ -90,8 +90,8 @@ chunked ответы, </section> -<section name="other_http_features" - title="Другие возможности HTTP-сервера"> +<section id="other_http_features" + name="Другие возможности HTTP-сервера"> <para> <list> @@ -181,8 +181,8 @@ PUT, DELETE, MKCOL, COPY и MOVE</link>; </section> -<section name="mail_proxy_server_features" - title="Функциональность почтового прокси-сервера"> +<section id="mail_proxy_server_features" + name="Функциональность почтового прокси-сервера"> <para> <list> @@ -231,8 +231,8 @@ SMTP: AUTH LOGIN/PLAIN/CRAM-MD5; </section> -<section name="architecture_and_scalability" - title="Архитектура и масштабируемость"> +<section id="architecture_and_scalability" + name="Архитектура и масштабируемость"> <para> <list> @@ -294,8 +294,8 @@ accept-фильтров (FreeBSD 4.1+) и TCP_DEFER_ACCEPT (Linux 2.4+); </section> -<section name="tested_os_and_platforms" - title="Протестированные ОС и платформы"> +<section id="tested_os_and_platforms" + name="Протестированные ОС и платформы"> <para> <list>
--- a/xml/ru/support.xml +++ b/xml/ru/support.xml @@ -5,7 +5,7 @@ lang="ru"> -<section title="Wiki"> +<section name="Wiki"> <para> <list> @@ -20,7 +20,7 @@ </section> -<section title="Списки рассылок"> +<section name="Списки рассылок"> <para> Вы можете @@ -64,7 +64,7 @@ </section> -<section title="Форумы"> +<section name="Форумы"> <para> <list> @@ -91,7 +91,7 @@ </section> -<section title="Разработка"> +<section name="Разработка"> <para> <list>
--- a/xml/tr/docs/http/configuring_https_servers.xml +++ b/xml/tr/docs/http/configuring_https_servers.xml @@ -41,7 +41,7 @@ Bu durumda dosya erişimi kısıtlanmalıdır. Aynı dosyada yer alsalar da istemciye sadece sertifika gönderilir. </section> -<section name="optimization" title="HTTPS sunucu optimizasyonu"> +<section id="optimization" name="HTTPS sunucu optimizasyonu"> <para> SSL işlemleri ekstra işlemci (CPU) kaynakları tüketir. Çok-işlemcili sistemlerde birçok işçi işlemler yürütmelisiniz: Mevcut işlemci çekirdek sayısından az olmamalı. En yoğun işlemci-yoğun işlem SSL el sıkışmalarıdır (ÇN: SSL Handshake, kısaca sunucuda bulunan sertifikanın istemci bilgisayar tarafından onaylanması ve tekrar sunucuya bildirilmesi sürecidir). Her bir istemci için mevcut bu işlemlerin sayısını azaltmanın iki yolu vardır: İlki, keep-alive bağlantıları olanaklı kılarak bir çok talebi sadece bir bağlantı ile göndermek ve ikincisi ise SSL oturum parametrelerini tekrar kullanarak paralel ve izleyen (subsequent) bağlantılar için SSL el sıkışmalarından kaçınmaktır. @@ -72,7 +72,7 @@ http { </section> -<section name="chains" title="SSL sertifika zincirleri"> +<section id="chains" name="SSL sertifika zincirleri"> <para> Bazı tarayıcılar popüler bir sertifika otoritesi tarafından imzalanmış sertifikaları sorunsuz kabul ederken, diğerleri sorun çıkarabilir. Bunun nedeni sertifika otoritesinin, sunucu sertifikasını, güvenilir sertifika veri tabanında yer almayan aracı bir sertifikayı kullanarak imzalamış olmasıdır. Bu durumda otorite, imzalanmış sertifikaya art arda bağlanması gereken bir dizi sertifika zinciri sunar. Bir araya geldikleri dosyada ilk önce sunucu sertifikası daha sonra zincirlenmiş sertifikalar yer almalıdır: @@ -144,7 +144,7 @@ Eğer sertifika dizisi eklemediyseniz, yalnızca bir sunucu sertifikası görürsünüz (server certificate #0). </section> -<section name="single_http_https_server" title="Tekil HTTP/HTTPS sunucusu"> +<section id="single_http_https_server" name="Tekil HTTP/HTTPS sunucusu"> <para> En baştan HTTP ve HTTPS protokollerini ayrı yapılandırmak en iyisidir. Mevcut durumda fonksiyonellikleri aynı gözükmekle birlikte, bu gelecekte önemli bir şekilde değişebilir ve birleştirilmiş bir sunucu problemli olabilir. Ancak, eğer HTTP ve HTTPS sunucuları eşit ise ve geleceği düşünmek istemiyorsanız, <dirname>ssl on</dirname> yönergesini silerek ve *:443 portu için <dirname>ssl</dirname> parametresi ekleyerek, HTTP ve HTTPS taleplerini tutan yalnızca bir sunucu yapılandırabilirsiniz: @@ -171,7 +171,7 @@ listen 443 default ssl; </section> -<section name="name_based_https_servers" title="Ad tabanlı HTTPS sunucuları"> +<section id="name_based_https_servers" name="Ad tabanlı HTTPS sunucuları"> <para> Bir IP adresini dinleyen iki veya daha fazla HTTPS sunucusunu yapılandırdığınız zaman genel bir problem ortaya çıkar: @@ -222,8 +222,8 @@ server { </section> -<section name="certificate_with_several_names" - title="Birçok ad içeren SSL sertifikası"> +<section id="certificate_with_several_names" + name="Birçok ad içeren SSL sertifikası"> <para> Bir tekil IP’yi birçok HTTPS sunucu arasında paylaştırmanın başka yolları da vardır, ancak bunların hepsi dezavantajlara sahiptir. Bunlardan biri, birçok ad içeren bir sertifikanın, SubjectAltName sertifika alanında kullanılmasıdır. Örneğin: <url>www.nginx.com</url> ve <url>www.nginx.org</url>. Ancak SubjectAltName alan uzunluğu sınırlandırılmıştır. @@ -259,7 +259,7 @@ server { </section> -<section name="sni" title="Server Name Indication"> +<section id="sni" name="Server Name Indication"> <para> Bir IP adresi üzerinde birçok HTTPS sunucusu yürütebilmenin en genel yollarından biri, bir SSL el sıkışması (handshake) sırasında, tarayıcının talep edilmiş bir sunucu adını iletmesine izin veren ve böylece sunucunun varsayılan bağlantı için hangi sertifikayı kullanacağını bilmesini sağlayan <a href="http://en.wikipedia.org/wiki/Server_Name_Indication">TLSv1.1 Server Name Indication eklentisidir</a> (SNI, RFC3546). Ancak SNI, kısıtlı bir tarayıcı desteğine sahiptir. Mevcut destekleyen tarayıcılar ve versiyonları: @@ -311,7 +311,7 @@ therefore SNI is not available </section> -<section name="compatibility" title="Uygunluk"> +<section id="compatibility" name="Uygunluk"> <para> <list>
--- a/xml/tr/docs/http/converting_rewrite_rules.xml +++ b/xml/tr/docs/http/converting_rewrite_rules.xml @@ -4,7 +4,7 @@ link="/tr/docs/http/converting_rewrite_rules.html" lang="tr"> -<section title="Ana siteye yönlendirme"> +<section name="Ana siteye yönlendirme"> <para> Paylaşımlı hosting kullananlar genelde her şeyi, sadece Apache’nin .htaccess dosyalarını yapılandırarak kullanırlar. Bu dosyada bulunan kuralların çevirisine örnek olarak: @@ -80,8 +80,8 @@ server { </section> -<section name="converting_mongrel_rules" - title="Mongrel kurallarının çevirisi"> +<section id="converting_mongrel_rules" + name="Mongrel kurallarının çevirisi"> <para> Tipik Mongrel kuralları:
--- a/xml/tr/docs/http/request_processing.xml +++ b/xml/tr/docs/http/request_processing.xml @@ -6,7 +6,7 @@ author="Igor Sysoev" translator="Altan Tanrıverdi"> -<section title="Ad-tabanlı sanal sunucular"> +<section name="Ad-tabanlı sanal sunucular"> <para> nginx, ilk olarak hangi sunucunun talebi işleyeceğine karar verir. @@ -58,8 +58,8 @@ Not: Varsayılan sunucu, sunucu adının değil listen portunun bir özelliğidir. Daha sonra bu konuya değinilecek. </section> -<section name="how_to_prevent_undefined_server_names" - title="Tanımlanmamış sunucu adlarına gelen taleplerin işlenmesini engellemek"> +<section id="how_to_prevent_undefined_server_names" + name="Tanımlanmamış sunucu adlarına gelen taleplerin işlenmesini engellemek"> <para> Eğer tanımlanmamış “Host” bilgisine sahip talepleri işlemek istemiyorsanız, bu talepleri düşüren bir varsayılan sunucu tanımlayabilirsiniz: @@ -79,8 +79,8 @@ Not: Bu sunucu için bir ad belirlemelisiniz. Aksi takdirde nginx <i>hostname</i> ifadesini kullanacaktır. </section> -<section name="mixed_name_ip_based_servers" - title="Ad ve IP bazlı karışık sanal sunucular"> +<section id="mixed_name_ip_based_servers" + name="Ad ve IP bazlı karışık sanal sunucular"> <para> Farklı adreslerde bulunan sanal sunucuların yer aldığı biraz daha karışık bir yapılandırmayı inceleyelim: @@ -136,8 +136,8 @@ server { </section> -<section name="simple_php_site_configuration" - title="Basit bir PHP sitesi yapılandırması"> +<section id="simple_php_site_configuration" + name="Basit bir PHP sitesi yapılandırması"> <para> nginx’in basit bir PHP sitesi için gelen talebi işlemek için nasıl bir <i>lokasyon</i> seçtiğini inceleyelim:
--- a/xml/tr/docs/http/server_names.xml +++ b/xml/tr/docs/http/server_names.xml @@ -64,8 +64,8 @@ ve düzenli ifadeler (regular expressions). </section> -<section name="wildcard_names" - title="Wildcard adlar"> +<section id="wildcard_names" + name="Wildcard adlar"> <para> Bir wildcard ad ancak başlangıçta veya bitişte * ifadesini içerir ve nokta ile sınırlandırılır. <dirname>www.*.nginx.org</dirname> ve <dirname>w*.nginx.org</dirname> adları geçersizdir. Ancak bu adlar düzenli ifadeler ile geçerli hale getirilebilir, örneğin, <dirname>~^www\..+\.nginx\.org$</dirname> ve <dirname>~^w.*\.nginx\.org$</dirname>. Buradaki * bir çok eşleşmeyi tanımlayabilir. <dirname>*.nginx.org</dirname> ifadesi <url>www.nginx.org</url> ve <url>www.sub.nginx.org</url> adlarına karşılık gelebilir. @@ -78,8 +78,8 @@ Bir wildcard ad ancak başlangıçta veya bitişte * ifadesini içerir ve nokta ile sınırlandırılır. <dirname>www.*.nginx.org</dirname> ve <dirname>w*.nginx.org</dirname> adları geçersizdir. Ancak bu adlar düzenli ifadeler ile geçerli hale getirilebilir, örneğin, <dirname>~^www\..+\.nginx\.org$</dirname> ve <dirname>~^w.*\.nginx\.org$</dirname>. Buradaki * bir çok eşleşmeyi tanımlayabilir. <dirname>*.nginx.org</dirname> ifadesi <url>www.nginx.org</url> ve <url>www.sub.nginx.org</url> adlarına karşılık gelebilir. </section> -<section name="regex_names" - title="Düzenli ifade adları"> +<section id="regex_names" + name="Düzenli ifade adları"> <para> nginx tarafından kullanılan düzenli ifadeler, Perl programlama dili (PCRE) tarafından kullanılanlar ile tam uyumludur. @@ -164,8 +164,8 @@ Ancak, dijital referanslar kolaylıkla üstüne yazılabilir olduğundan, bu şekilde kullanım basit durumlar için sınırlandırılmalıdır (yukarıdaki gibi). </section> -<section name="miscellaneous_names" - title="Diğer muhtelif adlar"> +<section id="miscellaneous_names" + name="Diğer muhtelif adlar"> <para> Eğer server bloğu içerisinde bir <dirname>server_name</dirname> tanımlanmamışsa nginx, sunucu adı olarak <i>hostname</i> ifadesini kullanır. @@ -244,8 +244,8 @@ server { </section> -<section name="optimization" - title="Optimizasyon"> +<section id="optimization" + name="Optimizasyon"> <para> Gerçek ve wildcard adlar çırpılarda (hash) depolanır. Çırpılar listen portlarına bağlıdırlar ve her bir listen port 3 farklı çırpıya sahip olabilir: gerçek ad çırpısı, * ile başlayan bir wildcard adı çırpısı ve * ile biten bir wildcard adı çırpısı. Çırpıların boyutu yapılandırma aşamasında optimize edilir ve böylece bir ad en az önbellek kayıpları ile bulundurulur. İlk olarak gerçek ad çırpısı aranır. Gerçek ad çırpısı kullanan bir ad bulunmaz ise, * ile başlayan wildcard ad çırpısı aranır. Bu da bulunmaz ise, * ile biten wildcard ad çırpısı aranır. Adların alanadı parçaları ile aranması nedeniyle wildcard ad çırpıları araması, gerçek ad çırpı aramasına oranla daha yavaştır. Not: Özel <dirname>.nginx.org</dirname> wildcard formu, gerçek ad çırpısında değil, wildcard ad çırpısında saklanır. Düzenli İfadeler sırayla test edildiğinden bu en yavaş ve ölçeklenebilir olmayan yöntemdir. @@ -308,8 +308,8 @@ Eğer bir sunucu sadece bir listen port için ise, nginx sunucu adlarını test etmeyecek ve listen port için çırpılar yaratmayacaktır. Fakat bu durumun bir istisnası var; eğer <dirname>server_name</dirname> tutuklar (capture) içeren bir düzenli ifade ise nginx, bu tutukları almak için ifadeyi yürütmek zorundadır. </section> -<section name="compatibility" - title="Uygunluk"> +<section id="compatibility" + name="Uygunluk"> <para> <list>
--- a/xml/tr/docs/windows.xml +++ b/xml/tr/docs/windows.xml @@ -87,8 +87,8 @@ eski işçi işlemden yavaşça çıkmak </section> -<section name="known_issues" - title="Bilinen sorunlar"> +<section id="known_issues" + name="Bilinen sorunlar"> <list> @@ -110,8 +110,8 @@ Windows Vista ve sonraki versiyonlarda çalışmamaktadır. </section> -<section name="possible_future_enhancements" - title="Muhtemel geliştirmeler"> +<section id="possible_future_enhancements" + name="Muhtemel geliştirmeler"> <list>
--- a/xml/tr/index.xml +++ b/xml/tr/index.xml @@ -24,8 +24,8 @@ Kaynak kodu, <a href="/LICENSE">2-clause BSD-like license</a> lisansı altındadır. </section> -<section name="basic_http_features" - title="Temel HTTP özellikleri"> +<section id="basic_http_features" + name="Temel HTTP özellikleri"> <para> <list> @@ -61,8 +61,8 @@ SSL ve TLS SNI desteği. </section> -<section name="other_http_features" - title="Diğer HTTP özellikleri"> +<section id="other_http_features" + name="Diğer HTTP özellikleri"> <para> <list> @@ -125,8 +125,8 @@ Gömülü perl. </section> -<section name="mail_proxy_server_features" - title="Mail proxy sunucu özellikleri"> +<section id="mail_proxy_server_features" + name="Mail proxy sunucu özellikleri"> <para> <list> @@ -173,8 +173,8 @@ STARTTLS ve STLS desteği. </section> -<section name="architecture_and_scalability" - title="Yapı ve ölçeklenebilirlik"> +<section id="architecture_and_scalability" + name="Yapı ve ölçeklenebilirlik"> <para> <list> @@ -224,8 +224,8 @@ Data kopyalama operasyonları minimum düzeydedir. </section> -<section name="tested_os_and_platforms" - title="Test edilen işletim sistemleri ve platformlar"> +<section id="tested_os_and_platforms" + name="Test edilen işletim sistemleri ve platformlar"> <para> <list>
--- a/xsls/body.xsls +++ b/xsls/body.xsls @@ -35,20 +35,14 @@ X:template body (lang) { <tr><td valign="top"> <table width="100%"><tr><td align="{$INDEX_ALIGN}"> - X:if "section[@id]" { - X:for-each "section[@id and @name]" { - <a href="#{@id}"> !{@name} </a><br/> - X:if "@id = 'directives'" { - X:for-each "directive[@name]" { - X:text{     } - <a href="#{@name}"> !{@name} </a><br/> - } + X:for-each "section[@id and @name]" { + <a href="#{@id}"> !{@name} </a><br/> + X:if "@id = 'directives'" { + X:for-each "directive[@name]" { + X:text{     } + <a href="#{@name}"> !{@name} </a><br/> } } - } else { - X:for-each "section[@name]" { - <a href="#{@name}"> !{@title} </a><br/> - } } </td></tr></table>
--- a/xsls/content.xsls +++ b/xsls/content.xsls @@ -10,22 +10,11 @@ X:stylesheet { !!; } - <!-- legacy section templates --> - - X:template = "section[not(@id) and @name and @title]" { - <a name="{@name}" /> <center><h4> !{@title} </h4></center> + X:template = "section[not(@id) and @name]" { + <center><h4> !{@name} </h4></center> !!; } - X:template = "section[not(@id) and not(@name) and @title]" { - <center><h4> !{@title} </h4></center> - !!; - } - - X:template = "section[not(@id) and not(@name) and not(@title)]" { !!; } - - <!-- --> - X:template = "para" { <p> !!; </p> } X:template = "para[@align]" { <p align="{@align}"> !!; </p> }