diff --git a/doc/locale/ja/LC_MESSAGES/admin/cluster-howto.en.po b/doc/locale/ja/LC_MESSAGES/admin/cluster-howto.en.po new file mode 100644 index 00000000000..c0af0b813f3 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/cluster-howto.en.po @@ -0,0 +1,293 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/cluster-howto.en.rst:4 +msgid "Traffic Server Cluster" +msgstr "Traffic Server クラスター" + +#: ../../admin/cluster-howto.en.rst:25 +msgid "" +"Traffic Server scales from a single node to multiple nodes that form a " +"cluster allowing you to improve system performance and reliability." +msgstr "" +"Traffic Server は単一ノードからシステムのパフォーマンスと信頼性を向上するク" +"ラスターを構成する複数ノードまでスケールします。" + +#: ../../admin/cluster-howto.en.rst:32 +msgid "Understanding Traffic Server Clusters" +msgstr "Traffic Server クラスターの理解" + +#: ../../admin/cluster-howto.en.rst:34 +msgid "" +"A Traffic Server cluster consists of multiple Traffic Server nodes. The " +"nodes in a cluster share configuration information and can form a single " +"logical cache. Traffic Server detects the addition and deletion of nodes in " +"the cluster automatically and can detect when a node is unavailable. " +"Traffic Server uses its own protocol for clustering, which is multicast for " +"node location and heartbeat, but unicast for all data exchange within the " +"cluster. Traffic Server has two clustering modes:" +msgstr "" +"Traffic Server クラスターは複数の Traffic Server ノードから構成されます。ク" +"ラスター内のノードは設定情報を共有し一つの論理的なキャッシュを形成します。" +"Traffic Server はクラスター内のノードの追加と削除を自動的に検知し、ノードが" +"利用不能になったことも検知します。Traffic Server はクラスタリングのために、" +"ノードの位置確認と生存確認にマルチキャストを、クラスター内のすべてのデータ交" +"換をユニキャストで行う独自のプロトコルを使用します。Traffic Server は二つの" +"クラスタリングモードを持ちます。" + +#: ../../admin/cluster-howto.en.rst:42 +msgid "Management-only mode; refer to `Management-Only Clustering`_ below." +msgstr "管理専用モード。`管理専用クラスタリング`_\\ を参照してください。" + +#: ../../admin/cluster-howto.en.rst:43 +msgid "Full-clustering mode; refer to `Full Clustering`_" +msgstr "" +"完全クラスタリングモード。`完全クラスタリング`_\\ を参照してください。" + +#: ../../admin/cluster-howto.en.rst:46 +msgid "Management-Only Clustering" +msgstr "管理専用クラスタリング" + +#: ../../admin/cluster-howto.en.rst:48 +msgid "" +"In management-only clustering mode, Traffic Server cluster nodes share " +"configuration information. You can administer all the nodes at the same " +"time. Traffic Server uses a multicast management protocol to provide a " +"single system image of your Traffic Server cluster. Information about " +"cluster membership, configuration, and exceptions is shared across all " +"nodes, and the :program:`traffic_manager` process automatically propagates " +"configuration changes to all the nodes." +msgstr "" +"管理専用クラスタリングモードでは、Traffic Server クラスターノードは設定情報" +"を共有します。すべてのノードを同時に管理できます。Traffic Server は Traffic " +"Server クラスターの単一のシステムイメージを提供するためにマルチキャスト管理" +"プロトコルを使用します。クラスターメンバー、設定、例外に関する情報がすべての" +"ノード間で共有され、:program:`traffic_manager` プロセスは自動的に設定の変更" +"をすべてのノードに伝搬します。" + +#: ../../admin/cluster-howto.en.rst:57 +msgid "Full Clustering" +msgstr "完全クラスタリング" + +#: ../../admin/cluster-howto.en.rst:59 +msgid "" +"In full-clustering mode, as well as sharing configuration information, a " +"Traffic Server cluster distributes its cache across its nodes into a " +"single, virtual object store, rather than replicating the cache node by " +"node. Traffic Server can provide an enormous aggregate cache size and can " +"maximize cache hit rate by storing objects only once across the entire " +"cluster." +msgstr "" +"完全クラスタリングモードでは、設定情報と同様に、Traffic Server クラスターは" +"キャッシュをノードごとに複製するのではなく、ノードをまたいだ単一の仮想オブ" +"ジェクトストアに配信します。Traffic Server はをクラスター全体にたった一度だ" +"けオブジェクトを保存する事で巨大な総キャッシュサイズの提供ととキャッシュヒッ" +"ト率の最大化を可能とします。" + +#: ../../admin/cluster-howto.en.rst:66 +msgid "" +"A fully clustered Traffic Server maps objects to specific nodes in the " +"cluster. When a node receives a request, it checks to see if the request is " +"a hit somewhere in the cluster. If the request is a hit on a different " +"node, the node handling the request obtains the object from the hit node " +"and serves it to the client. Traffic Server uses its own communication " +"protocol to obtain an object from sibling cluster nodes." +msgstr "" +"完全にクラスター化された Traffic Server はオブジェクトをクラスター内の特定の" +"ノードに割り当てます。ノードがリクエストを受け取ると、リクエストがクラスター" +"内のどこかでヒットするか確認します。リクエストが他のノードでヒットした場合、" +"ヒットしたノードからオブジェクトを読み取ってクライアントに返すようリクエスト" +"を扱います。Traffic Server は隣のクラスターノードからオブジェクトを読み取る" +"ために独自のコミュニケーションプロトコルを使用します。" + +#: ../../admin/cluster-howto.en.rst:73 +msgid "" +"If a node fails or is shut down and removed, Traffic Server removes " +"references to the missing node on all nodes in the cluster." +msgstr "" +"ノードが動作不能になったりシャットダウンされたり削除されたりすると、Traffic " +"Server はクラスター内のすべてのノード上にある失われたノードへの参照を削除し" +"ます。" + +#: ../../admin/cluster-howto.en.rst:76 +msgid "" +"Full clustering recommends a dedicated network interface for cluster " +"communication to get better performance." +msgstr "" +"完全クラスタリングはより良いパフォーマンスを得るためにクラスターのコミュニ" +"ケーションのための専用のネットワークインターフェースを推奨します。" + +#: ../../admin/cluster-howto.en.rst:80 +msgid "Enabling Clustering Mode" +msgstr "クラスタリングモードの有効化" + +#: ../../admin/cluster-howto.en.rst:82 +msgid "" +"Before you put a node into a cluster, please make sure the following things " +"are in order:" +msgstr "" +"ノードをクラスターに投入する前に、次のことが適切であることを確認してくださ" +"い。" + +#: ../../admin/cluster-howto.en.rst:85 +msgid "You are using the same operation system on all nodes:" +msgstr "すべてのノードで同じオペレーティングシステムを使用していること:" + +#: ../../admin/cluster-howto.en.rst:87 +msgid "Using the same distribution, e.g.: RHEL 5.5" +msgstr "同じディストリビューションを使用していること。例: RHEL 5.5" + +#: ../../admin/cluster-howto.en.rst:88 +msgid "Have same kernel, e.g.: 2.6.18-194.17.1.el5" +msgstr "同じカーネルを使っていること。例: 2.6.18-194.17.1.el5" + +#: ../../admin/cluster-howto.en.rst:89 +msgid "The same architecture, e.g.: ``x86_64``" +msgstr "同じアーキテクチャであること。例: ``x86_64``" + +#: ../../admin/cluster-howto.en.rst:91 +msgid "You have the same version of Traffic Server installed" +msgstr "同じバージョンの Traffic Server がインストールされていること" + +#: ../../admin/cluster-howto.en.rst:92 +msgid "The same hardware" +msgstr "同じハードウェアであること" + +#: ../../admin/cluster-howto.en.rst:93 +msgid "On the same switch or same VLAN." +msgstr "同じスイッチもしくは同じ VLAN 上にあること" + +#: ../../admin/cluster-howto.en.rst:95 +msgid "" +"Traffic Server does not apply the clustering mode change to all the nodes " +"in the cluster. You must change the clustering mode on each node " +"individually. You may following these instructions:" +msgstr "" +"Traffic Server はクラスタリングモードの変更をクラスター内のすべてのノードに" +"適用しません。クラスタリングモードは各ノードで個別に変更しなければなりませ" +"ん。次の指示に従ってください。" + +#: ../../admin/cluster-howto.en.rst:99 +msgid "" +"setup the same cluster name, with :ts:cv:`proxy.config.proxy_name`, e.g. " +"MyCluster." +msgstr "" +":ts:cv:`proxy.config.proxy_name` に同じクラスター名をセットアップする。例 " +"MyCluster" + +#: ../../admin/cluster-howto.en.rst:101 +msgid "" +"Set :ts:cv:`proxy.local.cluster.type` to ``1``, to enable cluster mode." +msgstr "" +"クラスターモードを有効化するために :ts:cv:`proxy.local.cluster.type`を " +"``1`` に設定する。" + +#: ../../admin/cluster-howto.en.rst:103 +msgid "" +"Setup a :ts:cv:`proxy.config.cluster.ethernet_interface`, e.g.: ``eth0``. " +"This should be replaced by your real interface; we recommends a dedicated " +"interface here. Refer to :ts:cv:`proxy.local.cluster.type` for a full " +"description." +msgstr "" +":ts:cv:`proxy.config.cluster.ethernet_interface` を設定する。例: ``eth0`` 。" +"これは実際のインターフェース名に置き換えてください。これは専用のインター" +"フェースにすることをお勧めします。完全な説明については :ts:cv:`proxy.local." +"cluster.type` を参照してください。" + +#: ../../admin/cluster-howto.en.rst:107 +msgid "enable: ::" +msgstr "有効化 ::" + +#: ../../admin/cluster-howto.en.rst:111 +msgid "restart: ::" +msgstr "リスタート ::" + +#: ../../admin/cluster-howto.en.rst:115 +msgid "" +"The :program:`traffic_server` and :program:`traffic_manager` processes will " +"need to restart after the change of :ts:cv:`proxy.local.cluster.type` and :" +"ts:cv:`proxy.config.cluster.ethernet_interface` have taken place." +msgstr "" +":program:`traffic_server` と :program:`traffic_manager` のプロセスは :ts:cv:" +"`proxy.local.cluster.type` と :ts:cv:`proxy.config.cluster." +"ethernet_interface` の変更が行われた後にリスタートする必要があります。" + +#: ../../admin/cluster-howto.en.rst:119 +msgid "" +"Traffic Server will join the cluster in about 10 seconds, and you can run :" +"option:`traffic_line -r` `proxy.process.cluster.nodes` to check the hosts " +"in the cluster, or check out the :file:`cluster.config` in the " +"configuration directory." +msgstr "" +"Traffic Server は約 10 秒でクラスターに加わり、クラスター内のホストを確認し" +"たり、設定ディレクトリ内の :file:`cluster.config` を確認するために :option:" +"`traffic_line -r` `proxy.process.cluster.nodes` を実行することができます。" + +#: ../../admin/cluster-howto.en.rst:125 +msgid "" +"After a successful join of the cluster, all changes of global " +"configurations on any node, will take effect on **all** nodes." +msgstr "" +"クラスターへの参加が成功した後、どのノード上であってもグローバル設定のあらゆ" +"る変更は\\ *すべて*\\ のノードに影響します。" + +#: ../../admin/cluster-howto.en.rst:129 +msgid "Deleting Nodes from a Cluster" +msgstr "クラスターからのノードの削除" + +#: ../../admin/cluster-howto.en.rst:131 +msgid "" +"To delete a node from the Traffic Server cluster, just roll back :ts:cv:" +"`proxy.config.cluster.type` to the default value 3 and reload." +msgstr "" +"Traffic Server クラスターからノードを削除するためには、単に :ts:cv:`proxy." +"config.cluster.type` をデフォルト値の 3 に戻して再読み込みを行ってください。" + +#: ../../admin/cluster-howto.en.rst:135 +msgid "Performance tweak for busy Cluster" +msgstr "多忙なクラスターのパフォーマンス調整" + +#: ../../admin/cluster-howto.en.rst:137 +msgid "" +"Starting from v3.2.0, Apache Traffic Server can handle multiple internal " +"cluster connections, and we can tweak for the Cluster threads and each of " +"the thread will keep one connection to all of the cluster machines:" +msgstr "" +"v3.2.0 から、Apache Traffic Server は複数の内部クラスター接続を扱えるように" +"なり、クラスタースレッドと各スレッドが全クラスターマシンに対して一つの接続を" +"維持するよう調整できるようになりました。" + +#: ../../admin/cluster-howto.en.rst:141 +msgid "Increasing Cluster threads:" +msgstr "クラスタースレッドの増加:" + +#: ../../admin/cluster-howto.en.rst:143 +msgid "" +"In the cluster env, the current performance of the Cluster threads will " +"consume the same cpu usage as net threads, so you may adapt the ET_NET & " +"ET_CLUSTER at about 1:1. For example, on a 24 cores system, set ET_NET " +"threads & ET_CLUSTER threads to 10, by setting :ts:cv:`proxy.config.cluster." +"threads` to ``10``." +msgstr "" +"クラスター環境では、現在のクラスタースレッドのパフォーマンスはネットスレッド" +"と同じだけ CPU を使用するので、ET_NET と ET_CLUSTER を約 1:1 に調整してもよ" +"いでしょう。例えば、24 コアのシステム上では、:ts:cv:`proxy.config.cluster." +"threads` を ``10`` に設定することで ET_NET スレッドと ET_CLUSTER スレッドを " +"10 に設定します。" + +#: ../../admin/cluster-howto.en.rst:153 +msgid "" +"with these tweaks, we can archive about 10gbps traffic for the internal " +"cluster transfer speed." +msgstr "" +"これらの調整により、内部クラスター転送速度 10gbps を達成することができます。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/configuring-cache.en.po b/doc/locale/ja/LC_MESSAGES/admin/configuring-cache.en.po new file mode 100644 index 00000000000..bb2093e6379 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/configuring-cache.en.po @@ -0,0 +1,578 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/configuring-cache.en.rst:4 +msgid "Configuring the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:23 +msgid "" +"The Traffic Server cache consists of a high-speed object database called " +"the **object store** that indexes objects according to URLs and their " +"associated headers." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:31 +msgid "The Traffic Server Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:33 +msgid "" +"The Traffic Server cache consists of a high-speed object database called " +"the **object store**. The object store indexes objects according to URLs " +"and associated headers. This enables Traffic Server to store, retrieve, and " +"serve not only web pages, but also parts of web pages - which provides " +"optimum bandwidth savings. Using sophisticated object management, the " +"object store can cache alternate versions of the same object (versions may " +"differ because of dissimilar language or encoding types). It can also " +"efficiently store very small and very large documents, thereby minimizing " +"wasted space. When the cache is full, Traffic Server removes stale data to " +"ensure the most requested objects are kept readily available and fresh." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:45 +msgid "" +"Traffic Server is designed to tolerate total disk failures on any of the " +"cache disks. If the disk fails completely, then Traffic Server marks the " +"entire disk as corrupt and continues using the remaining disks. An alarm is " +"then created to indicate which disk failed. If all of the cache disks fail, " +"then Traffic Server goes into proxy-only mode." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:51 +msgid "You can perform the following cache configuration tasks:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:53 +msgid "" +"Change the total amount of disk space allocated to the cache: refer to " +"`Changing Cache Capacity`_." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:55 +msgid "" +"Partition the cache by reserving cache disk space for specific protocols " +"and origin servers/domains: refer to `Partitioning the Cache`_." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:57 +msgid "Delete all data in the cache: refer to `Clearing the Cache`_." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:64 +msgid "The RAM Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:66 +msgid "" +"Traffic Server maintains a small RAM cache of extremely popular objects. " +"This RAM cache serves the most popular objects as quickly as possible and " +"reduces load on disks, especially during temporary traffic peaks. You can " +"configure the RAM cache size to suit your needs, as described in :ref:" +"`changing-the-size-of-the-ram-cache` below." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:79 +msgid "" +"Both the **LRU** and **CLFUS** RAM caches support a configuration to " +"increase scan resistance. In a typical **LRU**, if you request all possible " +"objects in sequence, you will effectively churn the cache on every request. " +"The option :ts:cv:`proxy.config.cache.ram_cache.use_seen_filter` can be set " +"to add some resistance against this problem." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:85 +msgid "" +"In addition, **CLFUS** also supports compressing in the RAM cache itself. " +"This can be useful for content which is not compressed by itself (e.g. " +"images). This should not be confused with *Content-Encoding: gzip*, this " +"feature is only thereto save space internally in the RAM cache itself. As " +"such, it is completely transparent to the User-Agent. The RAM cache " +"compression is enabled with the option :ts:cv:`proxy.config.cache.ram_cache." +"compress`. The default is 0, which means no compression. Other possible " +"values are 1 for **fastlz**, 2 for **libz** and 3 for **liblzma**." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:99 +msgid "Changing the Size of the RAM Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:101 +msgid "" +"Traffic Server provides a dedicated RAM cache for fast retrieval of popular " +"small objects. The default RAM cache size is automatically calculated based " +"on the number and size of the cache partitions you have configured. If " +"you've partitioned your cache according to protocol and/or hosts, then the " +"size of the RAM cache for each partition is proportional to the size of " +"that partition." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:108 +msgid "" +"You can increase the RAM cache size for better cache hit performance. " +"However, if you increase the size of the RAM cache and observe a decrease " +"in performance (such as increased latencies), then it's possible that the " +"operating system requires more memory for network resources. In such " +"instances, you should return the RAM cache size to its previous value." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:115 +msgid "To change the RAM cache size:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:117 +#: ../../admin/configuring-cache.en.rst:142 +#: ../../admin/configuring-cache.en.rst:155 +msgid "Stop Traffic Server." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:118 +msgid "" +"Set the variable :ts:cv:`proxy.config.cache.ram_cache.size` to specify the " +"size of the RAM cache. The default value of -1 means that the RAM cache is " +"automatically sized at approximately 1MB per gigabyte of disk." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:122 +msgid "" +"Restart Traffic Server. If you increase the RAM cache to a size of 1GB or " +"more, then restart with the :program:`trafficserver` command (refer to :ref:" +"`start-traffic-server`)." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:129 +msgid "Changing Cache Capacity" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:131 +msgid "" +"You can increase or reduce the total amount of disk space allocated to the " +"cache without clearing the content. To check the size of the cache (in " +"bytes), enter the command :option:`traffic_line -r` ``proxy.process.cache." +"bytes_total``." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:136 +msgid "Increasing Cache Capacity" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:138 +msgid "" +"To increase the total amount of disk space allocated to the cache on " +"existing disks or to add new disks to a Traffic Server node, follow the " +"steps below:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:143 +msgid "Add hardware, if necessary." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:144 +msgid "" +"Edit :file:`storage.config` to increase the amount of disk space allocated " +"to the cache on existing disks or describe the new hardware you are adding." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:146 +#: ../../admin/configuring-cache.en.rst:159 +#: ../../admin/configuring-cache.en.rst:188 +msgid "Restart Traffic Server." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:149 +msgid "Reducing Cache Capacity" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:151 +msgid "" +"To reduce the total amount of disk space allocated to the cache on an " +"existing disk or to remove disks from a Traffic Server node, follow the " +"steps below:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:156 +msgid "Remove hardware, if necessary." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:157 +msgid "" +"Edit :file:`storage.config` to reduce the amount of disk space allocated to " +"the cache on existing disks or delete the reference to the hardware you're " +"removing." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:161 +msgid "" +"In :file:`storage.config`, a formatted or raw disk must be at least 128 MB." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:166 +msgid "Partitioning the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:168 +msgid "" +"You can manage your cache space more efficiently and restrict disk usage by " +"creating cache volumes with different sizes for specific protocols. You can " +"further configure these volumes to store data from specific origin servers " +"and/or domains. The volume configuration must be the same on all nodes in " +"a :ref:`cluster `." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:175 +msgid "Creating Cache Partitions for Specific Protocols" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:177 +msgid "" +"You can create separate volumes for your cache that vary in size to store " +"content according to protocol. This ensures that a certain amount of disk " +"space is always available for a particular protocol. Traffic Server " +"currently supports the **http** partition type for HTTP objects." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:184 +msgid "To partition the cache according to protocol:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:186 +msgid "" +"Enter a line in the :file:`volume.config` file for each volume you want to " +"create" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:191 +msgid "Making Changes to Partition Sizes and Protocols" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:193 +msgid "" +"After you've configured your cache volumes based on protocol, you can make " +"changes to the configuration at any time. Before making changes, note the " +"following:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:197 +msgid "" +"You must stop Traffic Server before you change the cache volume size and " +"protocol assignment." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:199 +msgid "" +"When you increase the size of a volume, the contents of the volume are " +"*not* deleted. However, when you reduce the size of a volume, the contents " +"of the volume *are* deleted." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:202 +msgid "" +"When you change the volume number, the volume is deleted and then " +"recreated, even if the size and protocol type remain the same." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:204 +msgid "" +"When you add new disks to your Traffic Server node, volume sizes specified " +"in percentages will increase proportionately." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:206 +msgid "" +"A lot of changes to volume sizes might result in disk fragmentation, which " +"affects performance and hit rate. You should clear the cache before making " +"many changes to cache volume sizes (refer to `Clearing the Cache`_)." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:211 +msgid "Partitioning the Cache According to Origin Server or Domain" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:213 +msgid "" +"After you have partitioned the cache according to size and protocol, you " +"can assign the volumes you created to specific origin servers and/or " +"domains. You can assign a volumes to a single origin server or to multiple " +"origin servers. However, if a volumes is assigned to multiple origin " +"servers, then there is no guarantee on the space available in the volumes " +"for each origin server. Content is stored in the volumes according to " +"popularity. In addition to assigning volumes to specific origin servers and " +"domains, you must assign a generic volume to store content from all origin " +"servers and domains that are not listed. This generic volume is also used " +"if the partitions for a particular origin server or domain become corrupt. " +"If you do not assign a generic volume, then Traffic Server will run in " +"proxy-only mode." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:228 +msgid "" +"You do *not* need to stop Traffic Server before you assign volumes to " +"particular hosts or domains. However, this type of configuration is time-" +"consuming and can cause a spike in memory usage. Therefore, it's best to " +"configure partition assignment during periods of low traffic." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:234 +msgid "To partition the cache according to hostname and domain:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:236 +msgid "" +"Configure the cache volumes according to size and protocol, as described in " +"`Creating Cache Partitions for Specific Protocols`_." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:238 +msgid "" +"Create a separate volume based on protocol for each host and domain, as " +"well as an additional generic partition to use for content that does not " +"belong to these origin servers or domains. The volumes do not need to be " +"the same size." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:242 +msgid "" +"Enter a line in the :file:`hosting.config` file to allocate the volume(s) " +"used for each origin server and/or domain" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:244 +msgid "" +"Assign a generic volume to use for content that does not belong to any of " +"the origin servers or domains listed in the file. If all volumes for a " +"particular origin server become corrupt, then Traffic Server will also use " +"the generic volume to store content for that origin server as per :file:" +"`hosting.config`." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:249 +#: ../../admin/configuring-cache.en.rst:262 +msgid "" +"Run the command :option:`traffic_line -x` to apply the configuration " +"changes." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:253 +msgid "Configuring the Cache Object Size Limit" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:255 +msgid "" +"By default, Traffic Server allows objects of any size to be cached. You can " +"change the default behavior and specify a size limit for objects in the " +"cache via the steps below:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:259 +msgid "" +"Set :ts:cv:`proxy.config.cache.max_doc_size` to specify the maximum size " +"allowed for objects in the cache in bytes. ``0`` (zero) if you do not want " +"a size limit." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:268 +msgid "Clearing the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:270 +msgid "" +"When you clear the cache, you remove all data from the entire cache - " +"including data in the host database. You should clear the cache before " +"performing certain cache configuration tasks, such as partitioning. You " +"cannot clear the cache when Traffic Server is running." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:275 +msgid "To clear the cache:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:277 +msgid "" +"Stop Traffic Server (refer to :ref:`Stopping Traffic Server `)" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:278 +msgid "Enter the following command to clear the cache: ::" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:282 +msgid "" +"The ``clear`` command deletes all data in the object store and the host " +"database. Traffic Server does not prompt you to confirm the deletion." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:286 +msgid "" +"Restart Traffic Server (refer to :ref:`Starting Traffic Server `)." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:289 +msgid "Removing an Object From the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:291 +msgid "" +"Traffic Server accepts the custom HTTP request method ``PURGE`` when " +"removing a specific object from cache. If the object is found in the cache " +"and is successfully removed, then Traffic Server responds with a ``200 OK`` " +"HTTP message; otherwise, a ``404 File Not Found`` message is returned." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:297 +msgid "" +"In the following example, Traffic Server is running on the domain ``example." +"com`` and you want to remove the image ``remove_me.jpg`` from cache. " +"Because by default we do not permit ``PURGE`` requests from any other IP, " +"we connect to the daemon via localhost: ::" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:316 +msgid "" +"The next time Traffic Server receives a request for the removed object, it " +"will contact the origin server to retrieve it (i.e., it has been purged " +"from the Traffic Server cache)." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:320 +msgid "" +"Note: The procedure above only removes an object from a *specific* Traffic " +"Server cache. Users may still see the old (removed) content if it was " +"cached by intermediary caches or by the end-users' web browser." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:327 +msgid "Inspecting the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:336 +msgid "Accessing the Cache Inspector Utility" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:338 +msgid "To access the Cache Inspector utility, follow the steps below:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:340 +msgid "Set :ts:cv:`proxy.config.http_ui_enabled` to ``1``." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:341 +msgid "" +"To access the cache inspector in reverse proxy mode, you must add a remap " +"rule to :file:`remap.config` to expose the URL. This should be restricted " +"to a limited set of hosts using the ``@src_ip`` option. To restrict access " +"to the network 172.28.56.0/24, use ::" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:348 +msgid "" +"From the Traffic Server ``bin`` directory, enter the following command to " +"re-read the configuration file: ``traffic_line -x``" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:350 +msgid "" +"Open your web browser and configure it to use your Traffic Server as a " +"proxy server. Type the following URL::" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:355 +msgid "The Cache page opens." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:358 +msgid "Using the Cache Page" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:360 +msgid "" +"The **Cache page** provides several options that enable you to view and " +"delete the contents of your cache:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:363 +msgid "" +"Click **Lookup url** to search for a particular URL in the cache. When " +"Traffic Server finds the URL in the cache, it displays details about the " +"object that corresponds to the URL (such as the header length and the " +"number of alternates). From the display page, you can delete the URL from " +"the cache." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:368 +msgid "" +"Click **Delete url** to delete a particular URL or list of URLs from the " +"cache. Traffic Server indicates if a delete is successful." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:370 +msgid "" +"Click **Regex lookup** to search for URLs that match one or more regular " +"expressions. From the display page, you can delete the URLs listed. For " +"example, enter the following to search for all URLs that end in html and " +"are prefixed with ``http://www.dianes.com``: ``http://www.dianes.com/.*\\." +"html$``" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:375 +msgid "" +"Click **Regex delete** to delete all URLs that match a specified regular " +"expression. For example, enter the following to delete all HTTP URLs that " +"end in ``html``: ``http://.*\\.html$``" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:378 +msgid "" +"Click **Regex invalidate** to invalidate URLs that match a specified " +"regular expression. When you invalidate a URL, Traffic Server marks the " +"object that corresponds to the URL as stale in the cache. Traffic Server " +"then contacts the origin server to check if the object is still fresh " +"(revalidates) before serving it from the cache." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:386 +msgid "" +"Only one administrator should delete and invalidate cache entries from the " +"Cache page at any point in time. Changes made by multiple administrators at " +"the same time can lead to unpredictable results." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:58 +msgid "" +"Override cache directives for a requested domain name, regex on a url, " +"hostname or ip, with extra filters for time, port, method of the request " +"(and more). ATS can be configured to never cache; always cache; ignore no-" +"cache directives, etc. These are configured in :file:`cache.config`." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:72 +msgid "" +"The RAM cache supports two cache eviction algorithms, a regular **LRU** " +"(*Least Recently Used*) and the more advanced **CLFUS** (*Clocked Least " +"Frequently Used by Size*, which balances recentness, frequency and size to " +"maximize hit rate -- similar to a most frequently used algorithm). The " +"default is to use **CLFUS**, and this is controlled via :ts:cv:`proxy." +"config.cache.ram_cache.algorithm`." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:329 +msgid "" +"Traffic Server provides a Cache Inspector utility that enables you to view, " +"delete, and invalidate URLs in the cache (HTTP only). The Cache Inspector " +"utility is a powerful tool that's capable of deleting *all* the objects in " +"your cache; therefore, make sure that only authorized administrators are " +"allowed to access this utility, see :ref:`controlling-client-access-to-" +"cache` and the ``@src_ip`` option in :file:`remap.config`." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/admin/configuring-traffic-server.en.po b/doc/locale/ja/LC_MESSAGES/admin/configuring-traffic-server.en.po new file mode 100644 index 00000000000..e97d31408e0 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/configuring-traffic-server.en.po @@ -0,0 +1,110 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/configuring-traffic-server.en.rst:5 +msgid "Configuring Traffic Server" +msgstr "Traffic Server の設定" + +#: ../../admin/configuring-traffic-server.en.rst:24 +msgid "Traffic Server provides several options for configuring the system." +msgstr "" +"Traffic Server はシステムを設定するためのいくつかの方法を提供しています。" + +#: ../../admin/configuring-traffic-server.en.rst:32 +msgid "Configure Traffic Server Using Traffic Line" +msgstr "Traffic Line を使用して Traffic Server を設定する" + +#: ../../admin/configuring-traffic-server.en.rst:34 +msgid "" +"Traffic Line enables you to quickly and easily change your Traffic Server " +"configuration via command-line interface. Alternatively, you can also use :" +"program:`traffic_shell` to configure Traffic Server." +msgstr "" +"Traffic Line はコマンドラインインターフェースで手早く簡単に Traffic Server " +"の設定を変更することを可能にします。あるいは Traffic Server を設定するため" +"に :program:`traffic_shell` を使用することもできます。" + +#: ../../admin/configuring-traffic-server.en.rst:39 +msgid "View Configuration Options in Traffic Line" +msgstr "Traffic Line で設定項目を見る" + +#: ../../admin/configuring-traffic-server.en.rst:41 +msgid "To view a configuration setting, enter the following command::" +msgstr "設定内容を見るには次のコマンドを入力してください" + +#: ../../admin/configuring-traffic-server.en.rst:45 +msgid "" +"where ``var`` is the variable associated with the configuration option. For " +"a list of variables, refer to :ref:`configuration-variables`." +msgstr "" +"``var`` の部分は設定項目に対応する変数です。変数の一覧については :ref:" +"`configuration-variables` を参照してください。" + +#: ../../admin/configuring-traffic-server.en.rst:49 +msgid "Change Configuration Options in Traffic Line" +msgstr "Traffic Line で設定項目を変更する" + +#: ../../admin/configuring-traffic-server.en.rst:51 +msgid "" +"To change the value of a configuration setting, enter the following " +"command::" +msgstr "設定内容の値を変更するには次のコマンドを入力してください。" + +#: ../../admin/configuring-traffic-server.en.rst:56 +msgid "" +"where ``var`` is the variable associated with the configuration option and " +"``value`` is the value you want to use. For a list of the variables, see :" +"ref:`configuration-variables`." +msgstr "" +"``var`` の部分は設定項目に対応する変数、``value`` は設定したい値です。変数の" +"一覧については :ref:`configuration-variables` を見てください。" + +#: ../../admin/configuring-traffic-server.en.rst:61 +msgid "Configure Traffic Server Using Configuration Files" +msgstr "設定ファイルを使用して Traffic Server を設定する" + +#: ../../admin/configuring-traffic-server.en.rst:63 +msgid "" +"As an alternative to using Traffic Line or Traffic Shell, you can change " +"Traffic Server configuration options by manually editing specific variables " +"in the :file:`records.config` file. After modifying the :file:`records." +"config` file, Traffic Server must reread the configuration files: enter " +"the Traffic Line command :option:`traffic_line -x`. You may need to restart " +"Traffic Server to apply some of the configuration changes." +msgstr "" +"Traffic Line や Traffic Shell を使用する代わりに、:file:`records.config` " +"ファイルの具体的な変数を手動で編集することで Traffic Server の設定項目を変更" +"することができます。:file:`records.config` ファイルの修正後、Traffic Server " +"は必ず設定ファイルを再読み込みしなくてはなりません。Traffic Line コマンド :" +"option:`traffic_line -x` を入力してください。いくつかの設定の変更を適用する" +"には Traffic Server を再起動する必要があるかもしれません。" + +#: ../../admin/configuring-traffic-server.en.rst:71 +msgid "The following is a sample portion of the :file:`records.config` file:" +msgstr "以下は :file:`records.config` ファイルの部分的なサンプルです" + +#: ../../admin/configuring-traffic-server.en.rst:78 +msgid "Sample records.config file" +msgstr "records.config ファイルのサンプル" + +#: ../../admin/configuring-traffic-server.en.rst:80 +msgid "" +"In addition to the :file:`records.config` file, Traffic Server provides " +"other configuration files that are used to configure specific features. You " +"can manually edit all configuration files as described in :ref:" +"`configuration-file-reference`." +msgstr "" +":file:`records.config` ファイルに加え、Traffic Server は特定の機能を設定する" +"ために使用されるその他の複数の設定ファイルを提供します。:ref:`configuration-" +"file-reference` で説明されているように、すべての設定ファイルを手動で編集する" +"ことができます。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/event-logging-formats.en.po b/doc/locale/ja/LC_MESSAGES/admin/event-logging-formats.en.po new file mode 100644 index 00000000000..a120f5b2ee6 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/event-logging-formats.en.po @@ -0,0 +1,1007 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: 2014-01-12 17:37+0900\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/event-logging-formats.en.rst:4 +msgid "Event Logging Formats" +msgstr "イベントロギングフォーマット" + +#: ../../admin/event-logging-formats.en.rst:23 +msgid "" +"This document provides a reference for all the different logging formats " +"Traffic Server supports. Rather than just reading about those formats, you " +"may also want to try our `online event log builder `_ for an interactive way of building and " +"understanding log formats." +msgstr "" +"このドキュメントは Traffic Server がサポートしている全ての異なるロギング" +"フォーマットについてのリファレンスを提供します。これらのフォーマットについて" +"単に読むよりも、ログフォーマットのビルドと理解をインタラクティブに行うため" +"に `online event log builder `_ を試す方がいいでしょう。" + +#: ../../admin/event-logging-formats.en.rst:36 +msgid "Custom Logging Fields" +msgstr "カスタムログギングフィールド" + +#: ../../admin/event-logging-formats.en.rst:38 +msgid "The following list describes Traffic Server custom logging fields." +msgstr "次のリストは Traffic Server のカスタムロギングフィールドの説明です。" + +#: ../../admin/event-logging-formats.en.rst:43 +msgid "``{HTTP header field name}cqh``" +msgstr "``{HTTP header field name}cqh``" + +#: ../../admin/event-logging-formats.en.rst:41 +msgid "" +"Logs the information in the requested field of the client request HTTP " +"header. For example, ``%<{Accept-Language}cqh>`` logs the ``Accept-Language:" +"`` field in client request headers." +msgstr "" +"クライアントのリクエストの HTTP ヘッダの指定されたフィールドの情報のログで" +"す。例えば ``%<{Accept-Language}cqh>`` はクライアントリクエストヘッダーの " +"``Accept-Language:`` フィールドを記録します。" + +#: ../../admin/event-logging-formats.en.rst:48 +msgid "``{HTTP header field name}pqh``" +msgstr "``{HTTP header field name}pqh``" + +#: ../../admin/event-logging-formats.en.rst:46 +msgid "" +"Logs the information in the requested field of the proxy request HTTP " +"header. For example, ``%<{Authorization}pqh>`` logs the ``Authorization:`` " +"field in proxy request headers." +msgstr "" +"プロキシーのリクエストの HTTP ヘッダーの指定されたフィールドの情報を記録しま" +"す。例えば ``%<{Authorization}pqh>`` はプロキシーリクエストヘッダー内の " +"``Authorization:`` フィールドを記録します。" + +#: ../../admin/event-logging-formats.en.rst:53 +msgid "``{HTTP header field name}psh``" +msgstr "``{HTTP header field name}psh``" + +#: ../../admin/event-logging-formats.en.rst:51 +msgid "" +"Logs the information in the requested field of the proxy response HTTP " +"header. For example, ``%<{Retry-After}psh>`` logs the ``Retry-After:`` " +"field in proxy response headers." +msgstr "" +"プロキシーのレスポンスの HTTP ヘッダーの指定されたフィールドの情報を記録しま" +"す。例えば ``%<{Retry-After}psh>`` はプロキシーレスポンスヘッダーの ``Retry-" +"After:`` フィールドを記録します。" + +#: ../../admin/event-logging-formats.en.rst:58 +msgid "``{HTTP header field name}ssh``" +msgstr "``{HTTP header field name}ssh``" + +#: ../../admin/event-logging-formats.en.rst:56 +msgid "" +"Logs the information in the requested field of the server response HTTP " +"header. For example, ``%<{Age}ssh>`` logs the ``Age:`` field in server " +"response headers." +msgstr "" +"サーバーのレスポンスの HTTP ヘッダーの指定されたフィールドの情報を記録しま" +"す。例えば ``%<{Age}ssh>`` はサーバーレスポンスヘッダーの ``Age:`` フィール" +"ドを記録します。" + +#: ../../admin/event-logging-formats.en.rst:62 +#: ../../admin/event-logging-formats.en.rst:332 +#: ../../admin/event-logging-formats.en.rst:347 +#: ../../admin/event-logging-formats.en.rst:364 +#: ../../admin/event-logging-formats.en.rst:390 +msgid "``caun``" +msgstr "``caun``" + +#: ../../admin/event-logging-formats.en.rst:61 +msgid "" +"The client authenticated username; result of the RFC931/ident lookup of the " +"client username." +msgstr "" +"クライアントの認証されたユーザー名で、RFC931/ident lookup の結果のクライアン" +"トユーザー名です。" + +#: ../../admin/event-logging-formats.en.rst:67 +#: ../../admin/event-logging-formats.en.rst:405 +msgid "``cfsc``" +msgstr "``cfsc``" + +#: ../../admin/event-logging-formats.en.rst:65 +msgid "" +"The client finish status code; specifies whether the client request to " +"Traffic Server was successfully completed (``FIN``) or interrupted " +"(``INTR``)." +msgstr "" +"クライアントの終了ステータスコード、 Traffic Server へのクライアントリクエス" +"トが正しく完了した (``FIN``) もしくは中断された (``INTR``) のどちらかが記述" +"されます。" + +#: ../../admin/event-logging-formats.en.rst:70 +#: ../../admin/event-logging-formats.en.rst:327 +#: ../../admin/event-logging-formats.en.rst:346 +#: ../../admin/event-logging-formats.en.rst:363 +#: ../../admin/event-logging-formats.en.rst:389 +msgid "``chi``" +msgstr "``chi``" + +#: ../../admin/event-logging-formats.en.rst:70 +msgid "The IP address of the client's host machine." +msgstr "クライアントのホストマシンの IP アドレス。" + +#: ../../admin/event-logging-formats.en.rst:73 +msgid "``chih``" +msgstr "``chih``" + +#: ../../admin/event-logging-formats.en.rst:73 +msgid "The IP address of the client's host machine in hexadecimal." +msgstr "16 進数表記でのクライアントのホストマシンの IP アドレス。" + +#: ../../admin/event-logging-formats.en.rst:80 +#: ../../admin/event-logging-formats.en.rst:371 +#: ../../admin/event-logging-formats.en.rst:397 +msgid "``cqbl``" +msgstr "``cqbl``" + +#: ../../admin/event-logging-formats.en.rst:79 +msgid "" +"The client request transfer length; the body length in the client request " +"to Traffic Server (in bytes)." +msgstr "" +"クライアントリクエストの転送長、Traffic Server へのクライアントリクエストの" +"ボディの長さです。( byte 単位 )" + +#: ../../admin/event-logging-formats.en.rst:84 +#: ../../admin/event-logging-formats.en.rst:373 +#: ../../admin/event-logging-formats.en.rst:399 +msgid "``cqhl``" +msgstr "``cqhl``" + +#: ../../admin/event-logging-formats.en.rst:83 +msgid "" +"The client request header length; the header length in the client request " +"to Traffic Server." +msgstr "" +"クライアントリクエストヘッダーの長さ。Traffic Server へのクライアントリクエ" +"ストのヘッダーの長さです。" + +#: ../../admin/event-logging-formats.en.rst:88 +#: ../../admin/event-logging-formats.en.rst:330 +msgid "``cqhm``" +msgstr "``cqhm``" + +#: ../../admin/event-logging-formats.en.rst:87 +msgid "" +"The HTTP method in the client request to Traffic Server: ``GET``, ``POST``, " +"and so on (subset of ``cqtx``)." +msgstr "" +"Traffic Server へのクライアントリクエストの HTTP メソッド。``GET`` や " +"``POST`` やその他のものです。( ``cqtx`` のサブセット )" + +#: ../../admin/event-logging-formats.en.rst:91 +msgid "``cqhv``" +msgstr "``cqhv``" + +#: ../../admin/event-logging-formats.en.rst:91 +msgid "The client request HTTP version." +msgstr "クライアントリクエストの HTTP バージョン。" + +#: ../../admin/event-logging-formats.en.rst:96 +msgid "``cqtd``" +msgstr "``cqtd``" + +#: ../../admin/event-logging-formats.en.rst:94 +msgid "" +"The client request timestamp. Specifies the date of the client request in " +"the format yyyy-mm-dd, where yyyy is the 4-digit year, mm is the 2-digit " +"month, and dd is the 2-digit day." +msgstr "" +"クライアントリクエストのタイムスタンプ。クライアントリクエストの日付を yyyy-" +"mm-dd のフォーマットで記述します。。yyyy は 4 桁で年、mm は 2 桁で月、dd は " +"2 桁で日を表します。" + +#: ../../admin/event-logging-formats.en.rst:100 +msgid "``cqtn``" +msgstr "``cqtn``" + +#: ../../admin/event-logging-formats.en.rst:99 +msgid "" +"The client request timestamp; date and time of the client's request (in the " +"Netscape timestamp format)." +msgstr "" +"クライアントリクエストのタイムスタンプ。クライアントのリクエストの" +"( Netscape タイムスタンプフォーマットでの) 日付と時間。" + +#: ../../admin/event-logging-formats.en.rst:103 +msgid "``cqtq``" +msgstr "``cqtq``" + +#: ../../admin/event-logging-formats.en.rst:103 +msgid "The client request timestamp, with millisecond resolution." +msgstr "ミリ秒精度のクライアントリクエストのタイムスタンプ。" + +#: ../../admin/event-logging-formats.en.rst:108 +#: ../../admin/event-logging-formats.en.rst:325 +msgid "``cqts``" +msgstr "``cqts``" + +#: ../../admin/event-logging-formats.en.rst:106 +msgid "" +"The client-request timestamp in Squid format; the time of the client " +"request since January 1, 1970 UTC. Time is expressed in seconds, with " +"millisecond resolution." +msgstr "" +"Squid フォーマットでのクライアントリクエストのタイムスタンプ。 1970 年 1 月 " +"1 日からのクライアントリクエストの時間。時間は秒単位で、ミリ秒の精度です。" + +#: ../../admin/event-logging-formats.en.rst:114 +msgid "``cqtt``" +msgstr "``cqtt``" + +#: ../../admin/event-logging-formats.en.rst:111 +msgid "" +"The client request timestamp. The time of the client request in the format " +"hh:mm:ss, where hh is the two-digit hour in 24-hour format, mm is the two-" +"digit minutes value, and ss is the 2-digit seconds value (for example, " +"16:01:19)." +msgstr "" +"クライアントリクエストのタイムスタンプ。hh:mm:ss フォーマット\n" +"でのクライアントリクエストの時間で、hh は 2 桁の 24 時間表記で、mm は 2 桁の" +"分の値、ss は 2 桁の秒の値です。(例 16:01:19)" + +#: ../../admin/event-logging-formats.en.rst:123 +msgid "``cqtx``" +msgstr "``cqtx``" + +#: ../../admin/event-logging-formats.en.rst:117 +msgid "The full HTTP client request text, minus headers; for example, ::" +msgstr "ヘッダーを除く HTTP クライアントリクエストテキストの全て。例えば" + +#: ../../admin/event-logging-formats.en.rst:121 +#: ../../admin/event-logging-formats.en.rst:129 +msgid "" +"In reverse proxy mode, Traffic Server logs the rewritten/mapped URL " +"(according to the rules in the :file:`remap.config` file), _not_ the " +"pristine/unmapped URL." +msgstr "" +"リバースプロキシーモードでは Traffic Server は pristine/unmapped URL ではな" +"く ( :file:`remap.config` ファイル内のルールに従って ) rewritten/mapped URL " +"を記録します。" + +#: ../../admin/event-logging-formats.en.rst:132 +msgid "``cqu``" +msgstr "``cqu``" + +#: ../../admin/event-logging-formats.en.rst:126 +msgid "" +"The universal resource identifier (URI) of the request from client to " +"Traffic Server (subset of ``cqtx`` )." +msgstr "" +"Traffic Server へのクライアントからのリクエストの universal resource " +"identifier (URI) (``cqtx`` のサブセット)" + +#: ../../admin/event-logging-formats.en.rst:141 +#: ../../admin/event-logging-formats.en.rst:331 +msgid "``cquc``" +msgstr "``cquc``" + +#: ../../admin/event-logging-formats.en.rst:135 +msgid "" +"The client request canonical URL. This differs from ``cqu`` in that blanks " +"(and other characters that might not be parsed by log analysis tools) are " +"replaced by escape sequences. The escape sequence is a percentage sign " +"followed by the ASCII code number in hex." +msgstr "" +"クライアントリクエストの正規化 URL。 ``cqu`` との違いは空白 ( 他のログ分析" +"ツールでパースされないかもしれない文字 ) がエスケープシーケンスに置換されて" +"いることです。" + +#: ../../admin/event-logging-formats.en.rst:141 +msgid "See `cquuc`_." +msgstr "`cquuc`_ を参照してください。" + +#: ../../admin/event-logging-formats.en.rst:149 +msgid "``cqup``" +msgstr "``cqup``" + +#: ../../admin/event-logging-formats.en.rst:144 +msgid "" +"The client request URL path; specifies the argument portion of the URL " +"(everything after the host). For example, if the URL is ``http://www." +"company.com/images/x.gif``, then this field displays ``/images/x.gif``" +msgstr "" +"クライアントリクエスト URL のパス。URL ( ホストの後ろの全て ) の項の部分を記" +"述します。例えば URL が ``http://www.company.com/images/x.gif`` であれば、こ" +"のフィールドは ``/images/x.gif`` と表示されます。" + +#: ../../admin/event-logging-formats.en.rst:149 +msgid "See `cquup`_." +msgstr "`cquup`_　を参照してください。" + +#: ../../admin/event-logging-formats.en.rst:152 +msgid "``cqus``" +msgstr "``cqus``" + +#: ../../admin/event-logging-formats.en.rst:152 +msgid "The client request URL scheme." +msgstr "クライアントリクエスト URL のスキーム。" + +#: ../../admin/event-logging-formats.en.rst:158 +msgid "``cquuc``" +msgstr "``cquuc``" + +#: ../../admin/event-logging-formats.en.rst:157 +msgid "" +"The client request unmapped URL canonical. This field records a URL before " +"it is remapped (reverse proxy mode)." +msgstr "" +"クライアントリクエストのマップされていない正規化 URL。このフィールドは リ" +"マップされる前の URL を記録します。( リバースプロキシーモード )" + +#: ../../admin/event-logging-formats.en.rst:164 +msgid "``cquup``" +msgstr "``cquup``" + +#: ../../admin/event-logging-formats.en.rst:163 +msgid "" +"The client request unmapped URL path. This field records a URL path before " +"it is remapped (reverse proxy mode)." +msgstr "" +"クライアントリクエストのマップされていない URL パス。このフィールドはリマッ" +"プされる前の URL パスを記録します。( リバースプロキシーモード )" + +#: ../../admin/event-logging-formats.en.rst:170 +msgid "``cquuh``" +msgstr "``cquuh``" + +#: ../../admin/event-logging-formats.en.rst:169 +msgid "" +"The client request unmapped URL host. This field records a URL's host " +"before it is remapped (reverse proxy mode)." +msgstr "" +"クライアントリクエストのマップされていない URL ホスト。このフィールドはリ" +"マップされる前の URL のホストを記録します。( リバースプロキシーモード )" + +#: ../../admin/event-logging-formats.en.rst:173 +msgid "``crat``" +msgstr "``crat``" + +#: ../../admin/event-logging-formats.en.rst:173 +msgid "The Retry-After time in seconds, if specified by the origin server." +msgstr "" +"オリジンサーバーによって指定されている場合、秒単位の Retry-After 時間。" + +#: ../../admin/event-logging-formats.en.rst:177 +#: ../../admin/event-logging-formats.en.rst:407 +msgid "``crc``" +msgstr "``crc``" + +#: ../../admin/event-logging-formats.en.rst:176 +msgid "" +"The cache result code; specifies how the cache responded to the request " +"(``HIT``, ``MISS``, and so on)." +msgstr "" +"キャッシュ結果コード。どんなキャッシュをリクエストへ返したかを記述します。" +"( ``HIT`` や ``MISS`` やその他 )" + +#: ../../admin/event-logging-formats.en.rst:181 +msgid "``csscl``" +msgstr "``csscl``" + +#: ../../admin/event-logging-formats.en.rst:180 +msgid "" +"The cached response length (in bytes) from origin server to Traffic Server." +msgstr "" +"キャッシュしたオリジンサーバーから Traffic Server へのレスポンスの長さ。" +"( byte 単位 )" + +#: ../../admin/event-logging-formats.en.rst:185 +msgid "``csshl``" +msgstr "``csshl``" + +#: ../../admin/event-logging-formats.en.rst:184 +msgid "" +"The cached header length in the origin server response to Traffic Server " +"(in bytes)." +msgstr "" +"キャッシュしたオリジンサーバーから Traffic Server へのヘッダーの長さ。" +"( byte 単位 )" + +#: ../../admin/event-logging-formats.en.rst:188 +msgid "``csshv``" +msgstr "``csshv``" + +#: ../../admin/event-logging-formats.en.rst:188 +msgid "The cached server response HTTP version (1.0, 1.1, etc.)." +msgstr "キャッシュしたサーバーレスポンス HTTP バージョン。( 1.0 や 1.1 等 )" + +#: ../../admin/event-logging-formats.en.rst:192 +msgid "``csssc``" +msgstr "``csssc``" + +#: ../../admin/event-logging-formats.en.rst:191 +msgid "" +"The cached HTTP response status code from origin server to Traffic Server." +msgstr "" +"キャッシュしたオリジンサーバーから Traffic Server への HTTP レスポンスステー" +"タスコード。" + +#: ../../admin/event-logging-formats.en.rst:195 +msgid "``cwr``" +msgstr "``cwr``" + +#: ../../admin/event-logging-formats.en.rst:195 +msgid "" +"The cache write result (``-``, ``WL_MISS``, ``INTR```, ``ERR`` or ``FIN``)" +msgstr "" +"キャッシュ書き込み結果。( ``-``、 ``WL_MISS``、 ``INTR```、 ``ERR`` または " +"``FIN`` )" + +#: ../../admin/event-logging-formats.en.rst:198 +msgid "``cwtr``" +msgstr "``cwtr``" + +#: ../../admin/event-logging-formats.en.rst:198 +msgid "The cache write transform result" +msgstr "キャッシュ書き込みトランスフォーム結果。" + +#: ../../admin/event-logging-formats.en.rst:201 +msgid "``fsiz``" +msgstr "``fsiz``" + +#: ../../admin/event-logging-formats.en.rst:201 +msgid "The size of the file (*n* bytes) as seen by the origin server." +msgstr "オリジンサーバーから見えるファイルサイズ。( *n* バイト )" + +#: ../../admin/event-logging-formats.en.rst:206 +#: ../../admin/event-logging-formats.en.rst:406 +msgid "``pfsc``" +msgstr "``pfsc``" + +#: ../../admin/event-logging-formats.en.rst:204 +msgid "" +"The proxy finish status code; specifies whether the Traffic Server request " +"to the origin server was successfully completed (``FIN``), interrupted " +"(``INTR``) or timed out (``TIMEOUT``)." +msgstr "" +"プロキシー終了ステータスコード。Traffic Server からオリジンサーバーへのリク" +"エストが正常に完了した (``FIN``) もしくは中断された (``INTR``) かタイムアウ" +"トした (``TIMEOUT``) かどうか。" + +#: ../../admin/event-logging-formats.en.rst:210 +msgid "``phn``" +msgstr "``phn``" + +#: ../../admin/event-logging-formats.en.rst:209 +msgid "" +"The hostname of the Traffic Server that generated the log entry in collated " +"log files." +msgstr "" +"ログファイルに収集されるログエントリーを生成した Traffic Server のホスト名。" + +#: ../../admin/event-logging-formats.en.rst:214 +msgid "``phi``" +msgstr "``phi``" + +#: ../../admin/event-logging-formats.en.rst:213 +msgid "" +"The IP of the Traffic Server that generated the log entry in collated log " +"files." +msgstr "" +"ログファイルに収集されるログエントリーを生成した Traffic Server の IP。" + +#: ../../admin/event-logging-formats.en.rst:218 +#: ../../admin/event-logging-formats.en.rst:404 +msgid "``phr``" +msgstr "``phr``" + +#: ../../admin/event-logging-formats.en.rst:217 +msgid "" +"The proxy hierarchy route; the route Traffic Server used to retrieve the " +"object." +msgstr "" +"プロキシー階層の経路。Traffic Server がオプジェクトを検索するために使用した" +"経路。" + +#: ../../admin/event-logging-formats.en.rst:222 +#: ../../admin/event-logging-formats.en.rst:372 +#: ../../admin/event-logging-formats.en.rst:398 +msgid "``pqbl``" +msgstr "``pqbl``" + +#: ../../admin/event-logging-formats.en.rst:221 +msgid "" +"The proxy request transfer length; the body length in Traffic Server's " +"request to the origin server." +msgstr "" +"プロキシーリクエスト転送長。Traffic Server からオリジンサーバーへのリクエス" +"トのボディの長さ。" + +#: ../../admin/event-logging-formats.en.rst:226 +#: ../../admin/event-logging-formats.en.rst:375 +#: ../../admin/event-logging-formats.en.rst:401 +msgid "``pqhl``" +msgstr "``pqhl``" + +#: ../../admin/event-logging-formats.en.rst:225 +msgid "" +"The proxy request header length; the header length in Traffic Server's " +"request to the origin server." +msgstr "" +"プロキシーリクエストヘッダーの長さ。Traffic Server からオリジンサーバーへの" +"リクエストのヘッダーの長さ。" + +#: ../../admin/event-logging-formats.en.rst:230 +msgid "``pqsi``" +msgstr "``pqsi``" + +#: ../../admin/event-logging-formats.en.rst:229 +msgid "" +"The proxy request server IP address (0 on cache hits and parent-ip for " +"requests to parent proxies)." +msgstr "" +"プロキシーリクエストサーバー IP アドレス。( キャッシュヒットした場合と親プロ" +"キシーへのリクエストのペアレント IP は 0 )" + +#: ../../admin/event-logging-formats.en.rst:234 +msgid "``pqsn``" +msgstr "``pqsn``" + +#: ../../admin/event-logging-formats.en.rst:233 +msgid "" +"The proxy request server name; the name of the server that fulfilled the " +"request." +msgstr "プロキシーリクエストサーバー名。リクエストを満たしたサーバーの名前。" + +#: ../../admin/event-logging-formats.en.rst:237 +#: ../../admin/event-logging-formats.en.rst:351 +#: ../../admin/event-logging-formats.en.rst:368 +#: ../../admin/event-logging-formats.en.rst:394 +msgid "``pscl``" +msgstr "``pscl``" + +#: ../../admin/event-logging-formats.en.rst:237 +msgid "The length of the Traffic Server response to the client (in bytes)." +msgstr "Traffic Server からクライアントへのレスポンスの長さ。( byte 単位 )" + +#: ../../admin/event-logging-formats.en.rst:241 +#: ../../admin/event-logging-formats.en.rst:334 +msgid "``psct``" +msgstr "``psct``" + +#: ../../admin/event-logging-formats.en.rst:240 +msgid "" +"The content type of the document from server response header: (for example, " +"``img/gif`` )." +msgstr "" +"サーバーレスポンスヘッダーのドキュメントのコンテンツタイプ。( 例えば ``img/" +"gif`` )" + +#: ../../admin/event-logging-formats.en.rst:244 +#: ../../admin/event-logging-formats.en.rst:374 +#: ../../admin/event-logging-formats.en.rst:400 +msgid "``pshl``" +msgstr "``pshl``" + +#: ../../admin/event-logging-formats.en.rst:244 +msgid "The header length in Traffic Server's response to the client." +msgstr "Traffic Server からクライアントへのレスポンスのヘッダーの長さ。" + +#: ../../admin/event-logging-formats.en.rst:248 +#: ../../admin/event-logging-formats.en.rst:329 +msgid "``psql``" +msgstr "``psql``" + +#: ../../admin/event-logging-formats.en.rst:247 +msgid "" +"The proxy response transfer length in Squid format (includes header and " +"content length)." +msgstr "" +"Squid フォーマットでのプロキシーレスポンス転送長。( ヘッダーとコンテンツの長" +"さを含む )" + +#: ../../admin/event-logging-formats.en.rst:251 +#: ../../admin/event-logging-formats.en.rst:350 +#: ../../admin/event-logging-formats.en.rst:367 +#: ../../admin/event-logging-formats.en.rst:393 +msgid "``pssc``" +msgstr "``pssc``" + +#: ../../admin/event-logging-formats.en.rst:251 +msgid "The HTTP response status code from Traffic Server to the client." +msgstr "Traffic Server からクライアントへの HTTP レスポンスステータスコード。" + +#: ../../admin/event-logging-formats.en.rst:262 +msgid "``shi``" +msgstr "``shi``" + +#: ../../admin/event-logging-formats.en.rst:254 +msgid "" +"The IP address resolved from the DNS name lookup of the host in the " +"request. For hosts with multiple IP addresses, this field records the IP " +"address resolved from that particular DNS lookup." +msgstr "" +"リクエスト内のホストの DNS 名からルックアップして解決された IP アドレス。複" +"数の IP アドレスを持つホストの場合、このフィールドは特定の DNS ルックアップ" +"により解決された IP アドレスを記録します。" + +#: ../../admin/event-logging-formats.en.rst:258 +msgid "" +"This can be misleading for cached documents. For example: if the first " +"request was a cache miss and came from **``IP1``** for server **``S``** and " +"the second request for server **``S``** resolved to **``IP2``** but came " +"from the cache, then the log entry for the second request will show " +"**``IP2``**." +msgstr "" +"これはキャッシュされたドキュメントで誤解を与えるかもしれません。例えば、最初" +"のリクエストがキャッシュミスでサーバー **``S``** へ **``IP1``** が来て、次の" +"サーバー **``S``** へのリクエストが **``IP2``** に解決され、キャッシュから来" +"た場合、2 番目のリクエストのログエントリーは **``IP2``** と記録します。" + +#: ../../admin/event-logging-formats.en.rst:265 +msgid "``shn``" +msgstr "``shn``" + +#: ../../admin/event-logging-formats.en.rst:265 +msgid "The hostname of the origin server." +msgstr "オリジンサーバーのホスト名。" + +#: ../../admin/event-logging-formats.en.rst:268 +#: ../../admin/event-logging-formats.en.rst:370 +#: ../../admin/event-logging-formats.en.rst:396 +msgid "``sscl``" +msgstr "``sscl``" + +#: ../../admin/event-logging-formats.en.rst:268 +msgid "The response length (in bytes) from origin server to Traffic Server." +msgstr "" +"オリジンサーバーから Traffic Server へのレスポンスの長さ。( byte 単位 )" + +#: ../../admin/event-logging-formats.en.rst:272 +#: ../../admin/event-logging-formats.en.rst:376 +#: ../../admin/event-logging-formats.en.rst:402 +msgid "``sshl``" +msgstr "``sshl``" + +#: ../../admin/event-logging-formats.en.rst:271 +msgid "" +"The header length in the origin server response to Traffic Server (in " +"bytes)." +msgstr "" +"オリジンサーバーが Traffic Server へ返すヘッダーの長さ。 ( byte 単位 )" + +#: ../../admin/event-logging-formats.en.rst:275 +msgid "``sshv``" +msgstr "``sshv``" + +#: ../../admin/event-logging-formats.en.rst:275 +msgid "The server response HTTP version (1.0, 1.1, etc.)." +msgstr "サーバーレスポンス HTTP バージョン。( 1.0、1.1 等 )" + +#: ../../admin/event-logging-formats.en.rst:278 +#: ../../admin/event-logging-formats.en.rst:369 +#: ../../admin/event-logging-formats.en.rst:395 +msgid "``sssc``" +msgstr "``sssc``" + +#: ../../admin/event-logging-formats.en.rst:278 +msgid "The HTTP response status code from origin server to Traffic Server." +msgstr "" +"オリジンサーバーから Traffic Server への HTTP レスポンスステータスコード。" + +#: ../../admin/event-logging-formats.en.rst:284 +#: ../../admin/event-logging-formats.en.rst:326 +msgid "``ttms``" +msgstr "``ttms``" + +#: ../../admin/event-logging-formats.en.rst:281 +msgid "" +"The time Traffic Server spends processing the client request; the number of " +"milliseconds between the time the client establishes the connection with " +"Traffic Server and the time Traffic Server sends the last byte of the " +"response back to the client." +msgstr "" +"Traffic Server がクライアントリクエストを処理するのに費やした時間。クライア" +"ントが Traffic Server とコネクションを確立した時間から Traffic Server がクラ" +"イアントにレスポンスブロックの最後のバイトを送り返した時間までのミリ秒の数。" + +#: ../../admin/event-logging-formats.en.rst:287 +msgid "``ttmsh``" +msgstr "``ttmsh``" + +#: ../../admin/event-logging-formats.en.rst:287 +msgid "Same as ``ttms`` but in hexadecimal." +msgstr "``ttms`` と同様だが 16 進法表記。" + +#: ../../admin/event-logging-formats.en.rst:298 +msgid "``ttmsf``" +msgstr "``ttmsf``" + +#: ../../admin/event-logging-formats.en.rst:290 +msgid "" +"The time Traffic Server spends processing the client request as a " +"fractional number of seconds. Time is specified in millisecond resolution; " +"however, instead of formatting the output as an integer (as with ``ttms``), " +"the display is formatted as a floating-point number representing a " +"fractional number of seconds." +msgstr "" +"少数秒での Traffic Server がクライアントリクエストを処理するのに費やした時" +"間。時間はミリ秒の精度で記述されます。しかし ( ``ttms`` のように ) 整数とし" +"てフォーマットして出力する代わりに、秒単位の少数精度の浮動小数点数でフォー" +"マットして表示します。" + +#: ../../admin/event-logging-formats.en.rst:296 +msgid "" +"For example: if the time is 1500 milliseconds, then this field displays 1.5 " +"while the ``ttms`` field displays 1500 and the ``tts`` field displays 1." +msgstr "" +"例: 時間が 1500 ミリ秒の場合、このフィールドは 1.5 と表示します。一方 " +"``ttms`` フィールドは 1500 、 ``tts`` は 1 と表示します。" + +#: ../../admin/event-logging-formats.en.rst:305 +#: ../../admin/event-logging-formats.en.rst:377 +#: ../../admin/event-logging-formats.en.rst:403 +msgid "``tts``" +msgstr "``tts``" + +#: ../../admin/event-logging-formats.en.rst:301 +msgid "" +"The time Traffic Server spends processing the client request; the number of " +"seconds between the time at which the client establishes the connection " +"with Traffic Server and the time at which Traffic Server sends the last " +"byte of the response back to the client." +msgstr "" +"Traffic Server がクライアントリクエストを処理するのに費やした時間。クライア" +"ントが Traffic Server とコネクションを確立した時間から、Traffic Server がク" +"ライアントにレスポンスの最後の byte を返した時間の間の秒数。" + +#: ../../admin/event-logging-formats.en.rst:310 +msgid "Logging Format Cross-Reference" +msgstr "ログフォーマットクロスリファレンス" + +#: ../../admin/event-logging-formats.en.rst:312 +msgid "" +"The following sections illustrate the correspondence between Traffic Server " +"logging fields and standard logging fields for the Squid and Netscape " +"formats." +msgstr "" +"次の章では Traffic Server のロギングフィールドと Squid と Netdcape フォー" +"マットの標準ロギングフィールドの対応を解説します。" + +#: ../../admin/event-logging-formats.en.rst:317 +msgid "Squid Logging Formats" +msgstr "Squid ロギングフォーマット" + +#: ../../admin/event-logging-formats.en.rst:319 +msgid "" +"The following is a list of the Squid logging fields and the corresponding " +"logging field symbols." +msgstr "" +"下記は Squid ロギングフィールドと対応するロギングフィールド記号の表です。" + +#: ../../admin/event-logging-formats.en.rst:323 +msgid "Squid" +msgstr "Squid" + +#: ../../admin/event-logging-formats.en.rst:323 +#: ../../admin/event-logging-formats.en.rst:344 +#: ../../admin/event-logging-formats.en.rst:361 +#: ../../admin/event-logging-formats.en.rst:387 +msgid "Field Symbols" +msgstr "フィールド記号" + +#: ../../admin/event-logging-formats.en.rst:325 +msgid "``time``" +msgstr "``time``" + +#: ../../admin/event-logging-formats.en.rst:326 +msgid "``elapsed``" +msgstr "``elapsed``" + +#: ../../admin/event-logging-formats.en.rst:327 +msgid "``client``" +msgstr "``client``" + +#: ../../admin/event-logging-formats.en.rst:328 +msgid "``action/code``" +msgstr "``action/code``" + +#: ../../admin/event-logging-formats.en.rst:328 +msgid "``crc/pssc``" +msgstr "``crc/pssc``" + +#: ../../admin/event-logging-formats.en.rst:329 +msgid "``size``" +msgstr "``size``" + +#: ../../admin/event-logging-formats.en.rst:330 +msgid "``method``" +msgstr "``method``" + +#: ../../admin/event-logging-formats.en.rst:331 +msgid "``url``" +msgstr "``url``" + +#: ../../admin/event-logging-formats.en.rst:332 +msgid "``ident``" +msgstr "``ident``" + +#: ../../admin/event-logging-formats.en.rst:333 +msgid "``hierarchy/from``" +msgstr "``hierarchy/from``" + +#: ../../admin/event-logging-formats.en.rst:333 +msgid "``phr/pqsn``" +msgstr "``phr/pqsn``" + +#: ../../admin/event-logging-formats.en.rst:334 +msgid "``content``" +msgstr "``content``" + +#: ../../admin/event-logging-formats.en.rst:338 +msgid "Netscape Common Logging Formats" +msgstr "Netscape Common ロギングフォーマット" + +#: ../../admin/event-logging-formats.en.rst:340 +msgid "" +"The following is a list of the Netscape Common logging fields and the " +"corresponding Traffic Server logging field symbols." +msgstr "" +"下記は Netscape Common ロギングフィールドと対応する Traffic Server ロギング" +"フィールド記号の表です。" + +#: ../../admin/event-logging-formats.en.rst:344 +msgid "Netscape Common" +msgstr "Netscape Common" + +#: ../../admin/event-logging-formats.en.rst:346 +#: ../../admin/event-logging-formats.en.rst:363 +#: ../../admin/event-logging-formats.en.rst:389 +msgid "``host``" +msgstr "``host``" + +#: ../../admin/event-logging-formats.en.rst:347 +#: ../../admin/event-logging-formats.en.rst:364 +#: ../../admin/event-logging-formats.en.rst:390 +msgid "``usr``" +msgstr "``usr``" + +#: ../../admin/event-logging-formats.en.rst:348 +#: ../../admin/event-logging-formats.en.rst:365 +#: ../../admin/event-logging-formats.en.rst:391 +msgid "``[time]``" +msgstr "``[time]``" + +#: ../../admin/event-logging-formats.en.rst:348 +#: ../../admin/event-logging-formats.en.rst:365 +#: ../../admin/event-logging-formats.en.rst:391 +msgid "``[cqtn]``" +msgstr "``[cqtn]``" + +#: ../../admin/event-logging-formats.en.rst:349 +#: ../../admin/event-logging-formats.en.rst:366 +#: ../../admin/event-logging-formats.en.rst:392 +msgid "``\"req\"``" +msgstr "``\"req\"``" + +#: ../../admin/event-logging-formats.en.rst:349 +#: ../../admin/event-logging-formats.en.rst:366 +#: ../../admin/event-logging-formats.en.rst:392 +msgid "``\"cqtx\"``" +msgstr "``\"cqtx\"``" + +#: ../../admin/event-logging-formats.en.rst:350 +#: ../../admin/event-logging-formats.en.rst:367 +#: ../../admin/event-logging-formats.en.rst:393 +msgid "``s1``" +msgstr "``s1``" + +#: ../../admin/event-logging-formats.en.rst:351 +#: ../../admin/event-logging-formats.en.rst:368 +#: ../../admin/event-logging-formats.en.rst:394 +msgid "``c1``" +msgstr "``c1``" + +#: ../../admin/event-logging-formats.en.rst:355 +msgid "Netscape Extended Logging Formats" +msgstr "Netscape Extended ロギングフォーマット" + +#: ../../admin/event-logging-formats.en.rst:357 +msgid "" +"The following table lists the Netscape Extended logging fields and the " +"corresponding Traffic Server logging field symbols." +msgstr "" +"下記は Netscape Extended ロギングフォーマットフィールドと対応する Traffic " +"Server ロギングフィールド記号の表です。" + +#: ../../admin/event-logging-formats.en.rst:361 +msgid "Netscape Extended" +msgstr "Netscape Extended" + +#: ../../admin/event-logging-formats.en.rst:369 +#: ../../admin/event-logging-formats.en.rst:395 +msgid "``s2``" +msgstr "``s2``" + +#: ../../admin/event-logging-formats.en.rst:370 +#: ../../admin/event-logging-formats.en.rst:396 +msgid "``c2``" +msgstr "``c2``" + +#: ../../admin/event-logging-formats.en.rst:371 +#: ../../admin/event-logging-formats.en.rst:397 +msgid "``b1``" +msgstr "``b1``" + +#: ../../admin/event-logging-formats.en.rst:372 +#: ../../admin/event-logging-formats.en.rst:398 +msgid "``b2``" +msgstr "``b2``" + +#: ../../admin/event-logging-formats.en.rst:373 +#: ../../admin/event-logging-formats.en.rst:399 +msgid "``h1``" +msgstr "``h1``" + +#: ../../admin/event-logging-formats.en.rst:374 +#: ../../admin/event-logging-formats.en.rst:400 +msgid "``h2``" +msgstr "``h2``" + +#: ../../admin/event-logging-formats.en.rst:375 +#: ../../admin/event-logging-formats.en.rst:401 +msgid "``h3``" +msgstr "``h3``" + +#: ../../admin/event-logging-formats.en.rst:376 +#: ../../admin/event-logging-formats.en.rst:402 +msgid "``h4``" +msgstr "``h4``" + +#: ../../admin/event-logging-formats.en.rst:377 +#: ../../admin/event-logging-formats.en.rst:403 +msgid "``xt``" +msgstr "``xt``" + +#: ../../admin/event-logging-formats.en.rst:381 +msgid "Netscape Extended-2 Logging Formats" +msgstr "Netscape Extended-2 ロギングフォーマット" + +#: ../../admin/event-logging-formats.en.rst:383 +msgid "" +"The following is a list of the Netscape Extended-2 logging fields and the " +"corresponding Traffic Server logging field symbols." +msgstr "" +"下記は Netscape Extended-2 ロギングフィールドと対応する Traffic Server ロギ" +"ングフィールド記号の表です。" + +#: ../../admin/event-logging-formats.en.rst:387 +msgid "Netscape Extended-2" +msgstr "Netscape Extended-2" + +#: ../../admin/event-logging-formats.en.rst:404 +msgid "``route``" +msgstr "``route``" + +#: ../../admin/event-logging-formats.en.rst:405 +msgid "``pfs``" +msgstr "``pfs``" + +#: ../../admin/event-logging-formats.en.rst:406 +msgid "``ss``" +msgstr "``ss``" + +#: ../../admin/event-logging-formats.en.rst:76 +msgid "``chp``" +msgstr "``chp``" + +#: ../../admin/event-logging-formats.en.rst:76 +msgid "The port number of the client's host machine." +msgstr "クライアントのホストマシンのポート番号。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/explicit-proxy-caching.en.po b/doc/locale/ja/LC_MESSAGES/admin/explicit-proxy-caching.en.po new file mode 100644 index 00000000000..8f429711788 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/explicit-proxy-caching.en.po @@ -0,0 +1,108 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/explicit-proxy-caching.en.rst:4 +msgid "Explicit Proxy Caching" +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:26 +msgid "" +"If you want to use Traffic Server as an explicit proxy cache, you must " +"configure client software (i.e., browsers) to send requests directly to " +"Traffic Server." +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:30 +msgid "" +"If you do not configure Traffic Server to use the transparency option (with " +"which client requests are intercepted en route to origin servers by a " +"switch/router and rerouted to the Traffic Server machine), then clients " +"must configure their web browsers to send HTTP requests to the Traffic " +"Server proxy cache by configuring their browsers to download proxy " +"configuration instructions from a :ref:`PAC file ` " +"(Proxy Auto-Configuration file)." +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:39 +msgid "Configuring Browsers Manually" +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:41 +msgid "" +"To manually configure a browser to send HTTP requests to Traffic Server, " +"clients must provide the following information:" +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:44 +msgid "The fully-qualified hostname or IP address of the Traffic Server node" +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:45 +msgid "The Traffic Server proxy server port (port 8080)" +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:47 +msgid "" +"In addition, clients can specify *not* to use Traffic Server for certain " +"sites - in such cases, requests to the listed sites go directly to the " +"origin server. The procedures for manual configuration vary among browser " +"versions; refer to specific browser documentation for complete proxy " +"configuration instructions. You do not need to set any special " +"configuration options on Traffic Server if you want to accept requests from " +"manually-configured browsers." +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:58 +msgid "Using a PAC File" +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:60 +msgid "" +"A **PAC file** is a specialized JavaScript function definition that a " +"browser calls to determine how requests are handled. Clients must specify " +"(in their browser settings) the URL from which the PAC file is loaded. You " +"can store a PAC file on Traffic Server (or on any server in your network) " +"and then provide the URL for this file to your clients." +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:66 +msgid "" +"If you want to store a PAC file on the Traffic Server system, then you must " +"perform the following configuration:" +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:69 +msgid "" +"Either copy an existing PAC file into the Traffic Server ``config`` " +"directory or enter a script that defines the proxy server configuration " +"settings in the ``proxy.pac`` file provided. The file is empty by default. " +"A sample script is provided in `Sample PAC File`_." +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:74 +msgid "" +"Specify the port Traffic Server uses to serve the PAC file. The default " +"port is 8083, see :ts:cv:`proxy.config.admin.autoconf_port`." +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:78 +msgid "Sample PAC File" +msgstr "" + +#: ../../admin/explicit-proxy-caching.en.rst:80 +msgid "" +"The following sample PAC file instructs browsers to connect directly to all " +"hosts without a fully-qualified domain name and to all hosts in the local " +"domain. All other requests go to the Traffic Server named ``myproxy.company." +"com``.::" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/admin/faqs.en.po b/doc/locale/ja/LC_MESSAGES/admin/faqs.en.po new file mode 100644 index 00000000000..b7e4fbb057f --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/faqs.en.po @@ -0,0 +1,745 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/faqs.en.rst:4 +msgid "FAQ and Troubleshooting Tips" +msgstr "FAQ と トラブルシューティングの秘訣" + +#: ../../admin/faqs.en.rst:27 +msgid "FAQs" +msgstr "FAQ" + +#: ../../admin/faqs.en.rst:30 +msgid "" +"How do you create a raw disk for the cache if all your disks have mounted " +"file systems?" +msgstr "" +"全ディスクがファイルシステムにマウントされている場合、キャッシュ用の raw " +"ディスクの作成はどうすればいいですか？" + +#: ../../admin/faqs.en.rst:37 +msgid "" +"How do disk I/O errors affect the cache and what does Traffic Server do " +"when a cache disk fails?" +msgstr "" +"ディスク I/O エラーはキャッシュにどのように影響し、キャッシュディスクが動か" +"なくなったとき Traffic Server は何を行いますか？" + +#: ../../admin/faqs.en.rst:39 +msgid "" +"If a disk drive fails five successive I/O operations, then Traffic Server " +"considers the drive inaccessible and removes the entire disk from the " +"cache. Normal cache operations continue for all other Traffic Server disk " +"drives." +msgstr "" +"ディスクドライブが I/O 操作に連続して五回失敗すると、Traffic Server はドライ" +"ブがアクセス不能とみなしキャッシュからディスク全体を外します。通常のキャッ" +"シュ操作は Traffic Server の他のすべてのディスクドライブで継続します。" + +#: ../../admin/faqs.en.rst:45 +msgid "" +"If a client disconnects during the time that Traffic Server is downloading " +"a large object, is any of the object saved in the cache?" +msgstr "" +"Traffic Server が大きいオブジェクトをダウンロード中にクライアントが接続を閉" +"じた場合、オブジェクトはキャッシュに保存されますか？" + +#: ../../admin/faqs.en.rst:47 +msgid "" +"When a client disconnects during an HTTP operation, Traffic Server " +"continues to download the object from the origin server for up to 10 " +"seconds. If the transfer from the origin server completes successfully " +"within 10 seconds after the client disconnect, then Traffic Server stores " +"the object in cache. If the origin server download does *not* complete " +"successfully within 10 seconds, then Traffic Server disconnects from the " +"origin server and deletes the object from cache. Traffic Server does not " +"store partial documents in the cache." +msgstr "" +"HTTP の処理中にクライアントが接続を閉じたとき、Traffic Server は 10 秒までオ" +"リジンサーバーからのオブジェクトのダウンロードを継続します。クライアントが接" +"続を閉じた後、オリジンサーバーからの転送が 10 秒以内に正常に完了した場合、" +"Traffic Server はオブジェクトをキャッシュに保存します。オリジンサーバーから" +"のダウンロードが 10 秒以内に正常に完了しない場合、Traffic Server はオリジン" +"サーバーとの接続を閉じ、キャッシュからオブジェクトを削除します。Traffic " +"Server は部分的なオブジェクトをキャッシュに保存しません。" + +#: ../../admin/faqs.en.rst:57 +msgid "" +"Can Traffic Server cache Java applets, JavaScript programs, or other " +"application files like VBScript?" +msgstr "" +"Traffic Server は Java アプレット、JavaScript のブログラムもしくは VBScript " +"の様なその他のアプリケーションファイルをキャッシュできますか？" + +#: ../../admin/faqs.en.rst:59 +msgid "" +"Yes, Traffic Server can store and serve Java applets, JavaScript programs, " +"VBScripts, and other executable objects from its cache according to the " +"freshness and cacheability rules for HTTP objects. Traffic Server does not " +"execute the applets, scripts, or programs, however - these objects run only " +"when the client system (ie, the one that sent the request) loads them." +msgstr "" +"はい、Traffic Server は Java アプレット、JavaScript プログラム、VBScript、そ" +"の他実行可能なオブジェクトを保存し、HTTP オブジェクトの新鮮さとキャッシュ" +"ルールにもとづいて配信することができます。Traffic Server はアプレット、スク" +"リプト、プログラムを実行せず、クライアントはこれらシステムに読み込んだときに" +"のみ実行されます。" + +#: ../../admin/faqs.en.rst:67 +msgid "" +"In Squid- and Netscape-format log files, what do the cache result codes " +"mean?" +msgstr "" +"Squid や Netscape フォーマットのログファイルで、キャッシュ結果コードは何を意" +"味していますか？" + +#: ../../admin/faqs.en.rst:69 +msgid "" +"This is described in detail in the :ref:`log-formats-squid-format` " +"documentation." +msgstr "" +"これについては :ref:`log-formats-squid-format` に詳細に説明されています。" + +#: ../../admin/faqs.en.rst:72 +msgid "What is recorded by the ``cqtx`` field in a custom log file?" +msgstr "" +"カスタムログファイル内の ``cqtx`` フィールドには何が記録されていますか？" + +#: ../../admin/faqs.en.rst:74 +msgid "" +"In **forward proxy mode**, the cqtx field records the complete client " +"request in the log file (for example, ``GET http://www.company.com " +"HTTP/1.0``)." +msgstr "" +"**フォワードプロキシーモード** では、cqtx フィールドはクライアントの完全なリ" +"クエストを記録しています (例えば、``GET http://www.company.com HTTP/1.0`` な" +"ど) 。" + +#: ../../admin/faqs.en.rst:76 +msgid "" +"In **reverse proxy mode**, the cqtx field records the hostname or IP " +"address of the origin server because Traffic Server first remaps the " +"request as per map rules in the :file:`remap.config` file." +msgstr "" +"**リバースプロキシーモード** では、Traffic Server はまずリクエストを :file:" +"`remap.config` ファイル内のマップルールごとにリマップを行うので、cqtx フィー" +"ルドはオリジンサーバーのホスト名もしくは IP アドレスを記録しています。" + +#: ../../admin/faqs.en.rst:81 +msgid "" +"Does Traffic Server refresh entries in its host database after a certain " +"period of time if they have not been used?" +msgstr "" +"Traffic Server はホストデータベース内のエントリーが一定期間使われなかった場" +"合にそれらを更新しますか？" + +#: ../../admin/faqs.en.rst:83 +msgid "" +"By default, the Traffic Server host database observes the time-to-live " +"(``ttl``) values set by name servers. You can reconfigure Traffic Server to " +"ignore the ``ttl`` set by name servers and use a specific Traffic Server " +"setting instead. Alternatively, you can configure Traffic Server to compare " +"the ``ttl`` value set by the name server with the ``ttl`` value set by " +"Traffic Server, and then use either the lower or the higher value." +msgstr "" +"デフォルトでは、Traffic Server のホストデータベースはネームサーバーにより" +"セットされた time-to-live (``ttl``) を監視します。ネームサーバーによってセッ" +"トされた ``ttl`` を無視して指定した設定を使用するように Traffic Server を再" +"設定することも可能です。もしくは、ネームサーバーによってセットされた " +"``ttl`` の値と Traffic Server の設定値を比較し、低いものか高いものかどちらか" +"を使用するように Traffic Serverを設定することも可能です。" + +#: ../../admin/faqs.en.rst:91 +msgid "see :ts:cv:`proxy.config.hostdb.ttl_mode` for more info" +msgstr "詳しくは :ts:cv:`proxy.config.hostdb.ttl_mode` を観てください。" + +#: ../../admin/faqs.en.rst:94 +msgid "" +"Can you improve the look of your custom response pages by using images, " +"animated .gifs, and Java applets?" +msgstr "" +"カスタムレスポンスメッセージの見た目を画像やアニメーション GIF や Java アプ" +"レットを使用して改善することはできますか？" + +#: ../../admin/faqs.en.rst:96 +msgid "" +"No, because Traffic Server can only respond to clients with a single text " +"or HTML document. As a workaround, however, you can provide references on " +"your custom response pages to images, animated .gifs, Java applets, or " +"objects other than text which are located on a web server. Add links in the " +"body_factory template files in the same way you would for any image in an " +"HTML document (i.e., with the full URL in the ``SRC`` attribute)." +msgstr "" +"いいえ、Traffic Server はクライアントに一つのテキストもしくは HTML ドキュメ" +"ントしか返せません。次善策ではありますが、カスタマイズレスポンスページで " +"Web サーバー上にある画像、アニメーション GIF 、Java アプレット、その他テキス" +"トではないオブジェクトの参照を提供することは可能です。HTML ドキュメントに画" +"像を追加するのと同じ方法で body_factory テンプレートファイルにリンクを追加し" +"てください (例、\\ ``SRC`` 属性に完全な URL を指定するなど) 。" + +#: ../../admin/faqs.en.rst:105 +msgid "" +"Can Traffic Server run in forward proxy and reverse proxy modes at the same " +"time?" +msgstr "" +"Traffic Server はフォワードプロキシーモードとリバースプロキシーモードを同時" +"に実行できますか？" + +#: ../../admin/faqs.en.rst:107 +msgid "" +"Yes. When you enable reverse proxy mode, Traffic Server remaps incoming " +"requests according to the map rules in the :file:`remap.config` file. All " +"other requests that do not match a map rule are simply served in forward " +"proxy mode." +msgstr "" +"はい。リバースプロキシーモードを有効にした場合、Traffic Server は入ってきた" +"リクエストを :file:`remap.config` ファイル内のマップルールにもとづいて " +"remap します。マップルールにマッチしないその他のすべてのリクエストはフォワー" +"ドプロキシーモードで単純に処理されます。" + +#: ../../admin/faqs.en.rst:112 +msgid "" +"If you want to run in reverse proxy only mode (wherein Traffic Server does " +"*not* serve requests that fail to match a map rule), then you must set the " +"configuration variable :ts:cv:`proxy.config.url_remap.remap_required` to " +"``1`` in the :file:`records.config` file." +msgstr "" +"リバースプロキシーモードのみで実行したい場合 (Traffic Server はマップルール" +"にマッチしなかったリクエストに応え\\ *ません*\\ ) は、:file:`records." +"config` ファイル内の設定変数 :ts:cv:`proxy.config.url_remap.remap_required` " +"を ``1`` にセットしなければなりません。" + +#: ../../admin/faqs.en.rst:118 +msgid "How do I enable forward proxy mode" +msgstr "どうやってフォワードプロキシーモードを有効するのですか？" + +#: ../../admin/faqs.en.rst:120 +msgid "Please refer to the :ref:`forward-proxy` documentation." +msgstr ":ref:`forward-proxy` を参照してください。" + +#: ../../admin/faqs.en.rst:123 +msgid "How do I interpret the Via: header code?" +msgstr "どうやって Via: ヘッダーコードを解釈するのですか？" + +#: ../../admin/faqs.en.rst:128 +msgid "Support for HTTP Expect: Header" +msgstr "HTTP Expect: ヘッダーのサポート" + +#: ../../admin/faqs.en.rst:130 +msgid "" +"Traffic Server currently does not handle request Expect: headers according " +"to the HTTP/1.1 spec." +msgstr "" +"Traffic Server は現在 HTTP/1.1 仕様による Expect: ヘッダーを扱いません。" + +#: ../../admin/faqs.en.rst:133 +msgid "" +"Note that clients such as cURL automatically send Expect: for POST requests " +"with large POST bodies, with a 1 second timeout if a 100 Continue response " +"is not received. To avoid the timeout when using cURL as a client to " +"Traffic Server, you can turn off the Expect: header as follows::" +msgstr "" +"cURL などのクライアントは大きい POST ボディを持つ POST リクエストで、1 秒の" +"タイムアウトで 100 Continue レスポンスを受け取らない場合に自動的に Expect: " +"ヘッダーを送信することに注意してください。cURL を Traffic Server のクライア" +"ントとして使用する際のタイムアウトを防ぐためには、次のように Expect: ヘッ" +"ダーをオフにすることができます。" + +#: ../../admin/faqs.en.rst:141 +msgid "C (libcurl)::" +msgstr "C (libcurl)::" + +#: ../../admin/faqs.en.rst:147 +msgid "php::" +msgstr "php::" + +#: ../../admin/faqs.en.rst:152 +msgid "Troubleshooting Tips" +msgstr "トラブルシューティングの秘訣" + +#: ../../admin/faqs.en.rst:155 +msgid "The throughput statistic is inaccurate" +msgstr "スループットの統計が不正確" + +#: ../../admin/faqs.en.rst:157 +msgid "" +"Traffic Server updates the throughput statistic after it has transferred an " +"entire object. For larger files, the byte count increases sharply at the " +"end of a transfer. The complete number of bytes transferred is attributed " +"to the last 10-second interval, although it can take several minutes to " +"transfer the object. This inaccuracy is more noticeable with a light load. " +"A heavier load yields a more accurate statistic." +msgstr "" +"Traffic Server はスループットの統計をオブジェクト全体を転送した後で更新しま" +"す。大きいファイルではバイト数が転送の終わりで鋭く上昇します。オブジェクトを" +"転送するのに数分かかることもありますが完全な転送バイト数は直近の 10 秒間とな" +"ります。この不正確さは負荷が軽い場合に顕著です。重い負荷はより正確な統計をも" +"たらします。" + +#: ../../admin/faqs.en.rst:165 +msgid "You are unable to execute Traffic Line commands" +msgstr "Traffic Line コマンドが実行できない" + +#: ../../admin/faqs.en.rst:167 +msgid "Traffic Line commands do not execute under the following conditions:" +msgstr "Traffic Line コマンドは次の状況で動作しません。" + +#: ../../admin/faqs.en.rst:169 +msgid "" +"**When the traffic_manager process is not running** Check to see if the :" +"program:`traffic_manager` process is running by entering the following " +"command: ``pgrep -l traffic_manager``" +msgstr "" +"**traffic_manager プロセスが実行されていない場合**\\ 次のコマンドを入力し" +"て :program:`traffic_manager` プロセスが実行中であることを確認してください。" + +#: ../../admin/faqs.en.rst:173 +msgid "" +"If the :program:`traffic_manager` process is not running, then enter the " +"following command from the Traffic Server ``bin`` directory to start it: " +"``./traffic_manager``" +msgstr "" +":program:`traffic_manager` プロセスが実行中ではない場合は、開始するために " +"Traffic Server の ``bin`` ディレクトリで次のコマンドを入力してください。``./" +"traffic_manager``" + +#: ../../admin/faqs.en.rst:179 +msgid "" +"You should always start and stop Traffic Server with the :program:" +"`trafficserver start`` and :program:`trafficserver stop` commands to ensure " +"that all the processes start and stop correctly. For more information, " +"refer to :ref:`getting-started`." +msgstr "" +"すべてのプロセスで正常に開始と終了が行われることを確実にするために、Traffic " +"Server は :program:`trafficserver start` と :program:`trafficserver stop` コ" +"マンドで開始と終了をすべきです。詳しくは :ref:`getting-started` を参照してく" +"ださい。" + +#: ../../admin/faqs.en.rst:184 +msgid "" +"**When you are not executing the command from $TSHome/bin** If the Traffic " +"Server ``bin`` directory is not in your path, then prepend the Traffic Line " +"commands with ``./`` (for example, ``./traffic_line -h``)." +msgstr "" +"**コマンドを $TSHome/bin で実行していない場合** Traffic Server の ``bin`` " +"ディレクトリがパスに含まれていない場合、Traffic Line コマンドの前に ``./`` " +"を追加してください (例えば、``./traffic_line -h``) 。" + +#: ../../admin/faqs.en.rst:188 +msgid "" +"**When multiple Traffic Server installations are present and you are not " +"executing the Traffic Line command from the active Traffic Server path " +"specified in ``/etc/trafficserver``**" +msgstr "" +"**複数のインストール済み Traffic Server が存在し、``/etc/trafficserver`` で" +"指定された Traffic Server のパスから Traffic Line コマンドが実行されていない" +"場合。**" + +#: ../../admin/faqs.en.rst:194 +msgid "" +"You observe inconsistent behavior when one node obtains an object from " +"another node in the cluster" +msgstr "" +"クラスター内の他のノードからあるノードがオブジェクトを取得する際に矛盾した振" +"る舞いを観測した" + +#: ../../admin/faqs.en.rst:196 +msgid "" +"As part of the initial system preparation, you must synchronize the clocks " +"on all nodes in your cluster. Minor time differences do not cause problems, " +"but differences of more than a few minutes can affect Traffic Server " +"operation." +msgstr "" +"最初のシステム準備の一環で、クラスター内のすべてのノードの時刻を同期しなけれ" +"ば成りません。多少の違いは問題となりませんが、数分以上のずれは Traffic " +"Server の動作に影響を与えます。" + +#: ../../admin/faqs.en.rst:201 +msgid "" +"You should run a clock synchronization daemon such as xntpd. To obtain the " +"latest version of xntpd, go to ``http://www.eecis.udel.edu/~ntp/``" +msgstr "" +"xntpd などの時刻同期デーモンを実行するべきです。xntpd の最新バージョンを取得" +"するには ``http://www.eecis.udel.edu/~ntp/`` にアクセスしてください。" + +#: ../../admin/faqs.en.rst:205 +msgid "Web browsers display an error document with a 'data missing' message" +msgstr "" +"ウェブブラウザーが 'data missing' というメッセージのエラードキュメントを表示" +"します" + +#: ../../admin/faqs.en.rst:207 +msgid "A message similar to the following might display in web browsers: ::" +msgstr "次のようなメッセージがウェブブラウザーに表示されるかもしれません。" + +#: ../../admin/faqs.en.rst:221 +msgid "Traffic Server does not resolve any websites" +msgstr "Traffic Server がどのウェブサイトも解決しません" + +#: ../../admin/faqs.en.rst:223 +msgid "" +"The browser indicates that it is contacting the host and then times out " +"with the following message: ::" +msgstr "" +"ブラウザーはホストへ接続しようとしてタイムアウトしたことを次のメッセージで示" +"しています。" + +#: ../../admin/faqs.en.rst:228 +msgid "" +"Make sure the system is configured correctly and that Traffic Server can " +"read the name resolution file:" +msgstr "" +"システムが正しく設定されていることと Traffic Server が名前解決ファイルを読み" +"込めるを確認してください。" + +#: ../../admin/faqs.en.rst:231 +msgid "" +"Check if the server can resolve DNS lookups by issuing the nslookup command " +"(for example, ``nslookup www.myhost.com``)." +msgstr "" +"nslookup コマンドでサーバーが DNS 問い合わせを解決できるか ( 例えば、" +"``nslookup www.myhost.com``) 確認してください。" + +#: ../../admin/faqs.en.rst:233 +msgid "" +"Check if the :manpage:`resolv.conf(5)` file contains valid IP addresses for " +"your DNS servers." +msgstr "" +":manpage:`resolv.conf(5)` ファイルが DNS サーバーの妥当な IP アドレスを含ん" +"でいるか確認してください。" + +#: ../../admin/faqs.en.rst:235 +msgid "" +"On some systems, if the :manpage:`resolv.conf(5)` file is unreadable or has " +"no name server entry, then the operating system uses ``localhost`` as a " +"name server. Traffic Server, however, does not use this convention. If you " +"want to use ``localhost`` as a name server, then you must add a name server " +"entry for ``127.0.0.1`` or ``0.0.0.0`` in the :manpage:`resolv.conf(5)` " +"file." +msgstr "" +"いくつかのシステムでは、:manpage:`resolv.conf(5)` ファイルが読み込めないか" +"ネームサーバーの項目がない場合、オペレーティングシステムは ``localhost`` を" +"ネームサーバーとして使用します。しかし Traffic Server はこの慣習を使用しませ" +"ん。``localhost`` をネームサーバーとして使用したい場合は、''127.0.0.1`` もし" +"くは ``0.0.0.0`` へのネームサーバーの項目を :manpage:`resolv.conf(5)` ファイ" +"ルに追加しなければ成りません。" + +#: ../../admin/faqs.en.rst:241 +msgid "" +"Check that the Traffic Server user account has permission to read the /etc/" +"resolv.conf file. If it does not, then change the file permissions to ``rw-" +"r--r--`` (``644``)" +msgstr "" +"Traffic Server のユーザーアカウントが /etc/resolv.conf ファイルを読み込む権" +"限を持っていることを確認してください。もし権限がない場合はファイルのパーミッ" +"ションを ``rw-r--r--`` (``644``) に変更してください。" + +#: ../../admin/faqs.en.rst:246 +msgid "'Maximum document size exceeded' message in the system log file" +msgstr "" +"システムログファイル内の 'Maximum document size exceeded' というメッセージ" + +#: ../../admin/faqs.en.rst:248 +msgid "The following message appears in the system log file: ::" +msgstr "次のメッセージがシステムログファイルに現れます。" + +#: ../../admin/faqs.en.rst:252 +msgid "" +"A requested object was larger than the maximum size allowed in the Traffic " +"Server cache, so Traffic Server provided proxy service for the oversized " +"object but did not cache it. To set the object size limit for the cache, " +"modify the :ts:cv:`proxy.config.cache.limits.http.max_doc_size` variable in " +"the records.config file. If you do not want to limit the size of objects in " +"the cache, then set the document size to ``0`` (zero)." +msgstr "" +"リクエストされたオブジェクトが Traffic Server のキャッシュで許された最大サイ" +"ズより大きかったので、Traffic Server はその大きすぎるオブジェクトへのプロキ" +"シーは提供しましたがキャッシュは行いませんでした。キャッシュのオブジェクトサ" +"イズ制限を設定するには、records.config ファイルの :ts:cv:`proxy.config." +"cache.limits.http.max_doc_size` 設定変数を変更してください。キャッシュ内のオ" +"ブジェクトとのサイズを制限したくない場合は、ドキュメントサイズを ``0`` ( ゼ" +"ロ ) に設定してください。" + +#: ../../admin/faqs.en.rst:261 +msgid "'DrainIncomingChannel' message in the system log file" +msgstr "システムログファイル内の 'DrainIncomingChannel' というメッセージ" + +#: ../../admin/faqs.en.rst:263 +msgid "The following messages may appear in the system log file: ::" +msgstr "次のメッセージがシステムログファイルに現れるかもしれません。" + +#: ../../admin/faqs.en.rst:269 +msgid "" +"These error messages indicate that a browser is sending HTTP requests to " +"one of the Traffic Server cluster ports - either ``rsport`` (default port " +"8088) or ``mcport`` (default port 8089). Traffic Server discards the " +"request; this error does not cause any Traffic Server problems. The " +"misconfigured browser must be reconfigured to use the correct proxy port. " +"Traffic Server clusters work best when configured to use a separate network " +"interface and cluster on a private subnet, so that client machines have no " +"access to the cluster ports." +msgstr "" +"これらのエラーメッセージはブラウザーが HTTP リクエストを Traffic Server のク" +"ラスターポートに送信したことを示しています。これは ``rsport`` ( デフォルト" +"ポートは 8088) もしくは ``mcport`` ( デフォルトポートは 8089) です。Traffic " +"Server はこのリクエストを破棄します。このエラーは Traffic Server になんの問" +"題ももたらしません。間違って設定されたブラウザーは正しいプロキシーポートを使" +"用するために再設定されなければなりません。Traffic Server クラスターはクライ" +"アントマシンがクラスターポートにアクセスできないよう別のネットワークインタ" +"フェースを使用しプライベートサブネット上で使用するよう設定された場合によく動" +"作します。" + +#: ../../admin/faqs.en.rst:279 +msgid "'No cop file' message in the system log file" +msgstr "システムログファイル内の 'No cop file' というメッセージ" + +#: ../../admin/faqs.en.rst:281 +msgid "The following message appears repeatedly in the system log file: ::" +msgstr "次のメッセージがシステムログファイルに繰り返し現れます。" + +#: ../../admin/faqs.en.rst:285 +msgid "" +"The file ``var/trafficserver/no_cop`` acts as an administrative control " +"that instructs the :program:`traffic_cop` process to exit immediately " +"without starting :program:`traffic_manager` or performing any health " +"checks. The ``no_cop`` file prevents Traffic Server from starting " +"automatically when it has been stopped with the option:`trafficserver stop` " +"command. Without this static control, Traffic Server would restart " +"automatically upon system reboot. The ``no_cop`` control keeps Traffic " +"Server off until it is explicitly restarted with the ::" +msgstr "" +"``var/trafficserver/no_cop`` は :program:`traffic_cop` が :program:" +"`traffic_manager` を起動せずヘルスチェックを行わずに直ちに終了するように指示" +"する管理制御として振る舞います。``no_cop`` ファイルは Traffic Server が " +"option:`trafficserver stop` で停止されたときに自動的に開始するのを抑止しま" +"す。この静的な制御を行わないと、Traffic Server はシステムリブートにより自動" +"的に再開します。``no_cop`` 制御は" + +#: ../../admin/faqs.en.rst:296 +msgid "command." +msgstr "コマンドで明示的に再開されるまで Traffic Server を停止し続けます。" + +#: ../../admin/faqs.en.rst:300 +msgid "Warning in the system log file when manually editing vaddrs.config" +msgstr "vaddrs.config を手動で編集したときのシステムログファイルの警告" + +#: ../../admin/faqs.en.rst:302 +msgid "" +"If you manually edit the vaddrs.config file as a non-root user, then " +"Traffic Server issues a warning message in the system log file similar to " +"the following::" +msgstr "" +"vaddrs.config ファイルを非 root ユーザーとして手動で編集すると、Traffic " +"Server はシステムログファイルに次のような警告メッセージを発行します。" + +#: ../../admin/faqs.en.rst:308 +msgid "" +"You can safely ignore this message; Traffic Server *does* apply your " +"configuration edits." +msgstr "" +"このメッセージは安全に無視することができます。Traffic Server は設定ファイル" +"の編集を適用\\ *します*\\ 。" + +#: ../../admin/faqs.en.rst:312 +msgid "Traffic Server is running but no log files are created" +msgstr "Traffic Server は実行中だがログファイルが作られない" + +#: ../../admin/faqs.en.rst:314 +msgid "" +"Traffic Server only writes event log files when there is information to " +"record. If Traffic Server is idle, then it's possible/probable that no log " +"files exist. In addition:" +msgstr "" +"Traffic Server は記録する情報があるときにだけイベントログファイルに書き込み" +"ます。Traffic Server がアイドル状態の場合、ログファイルは存在しない可能性が" +"あります。" + +#: ../../admin/faqs.en.rst:318 +msgid "" +"Make sure you're looking in the correct directory. By default, Traffic " +"Server creates log files in the logs directory. Check the location of log " +"files by checking the value of the variable proxy.config.log.logfile_dir in " +"the records.config file. Check that the log directory has read/write " +"permissions for the Traffic Server user account. If the log directory does " +"not have the correct permissions, then the traffic_server process is unable " +"to open or create log files. Check that logging is enabled by checking the " +"value of the proxy.config.log.logging_enabled variable in the records." +"config file. Check that a log format is enabled. In the records.config " +"file, select the standard or custom format by editing variables in the " +"Logging Config section." +msgstr "" +"正しいディレクトリを見ていることを確認してください。デフォルトでは、Traffic " +"Server はログファイルをログディレクトリに作成します。records.config の " +"variable proxy.config.log.logfile_dir 変数の値を確認しログファイルの場所を確" +"認してください。ログディレクトリに Traffic Server ユーザーアカウントに対する" +"読み書きのパーミッションがあることを確認してください。ログディレクトリが正し" +"いパーミッションを持っていない場合、traffic_server プロセスはログファイルを" +"作成したり開いたりできません。records.config の proxy.config.log." +"logging_enabled 変数の値を確認し、ロギングが有効化されていることを確認してく" +"ださい。ログフォーマットが有効化されていることを確認してください。records." +"config ファイルで、ロギング設定セクションの変数を編集して標準もしくはカスタ" +"ムフォーマットを選択してください。" + +#: ../../admin/faqs.en.rst:332 +msgid "Traffic Server shows an error indicating too many network connections" +msgstr "Traffic Server がネットワーク接続が多すぎることを示すエラーを表示する" + +#: ../../admin/faqs.en.rst:334 +msgid "" +"By default, Traffic Server supports 8000 network connections: half of this " +"number is allocated for client connections and the remaining half is for " +"origin server connections. A **connection throttle event** occurs when " +"client or origin server connections reach 90% of half the configured limit " +"(3600 by default). When a connection throttle event occurs, Traffic Server " +"continues processing all existing connections but will not accept new " +"client connection requests until the connection count falls below the limit." +msgstr "" +"デフォルトでは、Traffic Server は 8000 のネットワーク接続に対応しています。" +"このうちの半分がクライアントとの接続に割り当てられ、残りの半分はオリジンサー" +"バーとの接続のためのものです。クライアントまたはオリジンサーバーの接続が設定" +"された制限の半分の 90% ( デフォルトでは 3600) に達すると **connection " +"throttle event** が発生します。connection throttle event が発生すると、" +"Traffic Server はすべての既存の接続の処理を継続しますが、接続数が制限を下回" +"るまで新規の接続要求を受け付けません。" + +#: ../../admin/faqs.en.rst:343 +msgid "Connection throttle events can occur under the following conditions:" +msgstr "Connection throttle event は次の条件で発生します。" + +#: ../../admin/faqs.en.rst:345 +msgid "" +"If there is a **connection spike** (e.g., if thousands of client requests " +"all reach Traffic Server at the same time). Such events are typically " +"transient and require no corrective action." +msgstr "" +"**接続のスパイク**\\ がある場合 ( 例えば、数千のクライアントのリクエストすべ" +"てが Traffic Server に同時に届いたなど ) 。このようなイベントは一般的に一時" +"的なもので修正の必要はありません。" + +#: ../../admin/faqs.en.rst:348 +msgid "" +"If there is a **service overload** (e.g., if client requests continuously " +"arrive faster than Traffic Server can service them). Service overloads " +"often indicate network problems between Traffic Server and origin servers. " +"Conversely, it may indicate that Traffic Server needs more memory, CPU, " +"cache disks, or other resources to handle the client load." +msgstr "" +"**サービス過負荷**\\ がある場合 ( 例えば、クライアントのリクエストが " +"Traffic Server が捌けるよりも早く継続的に届く場合) 。サービス過負荷は " +"Traffic Server とオリジンサーバーとの間のネットワークの問題を示していること" +"がよくあります。逆に言えば、Traffic Server はその負荷を扱うためにより多くの" +"メモリー、CPU 、キャッシュディスク、その他のリソースを必要としていることを示" +"しているかもしれません。" + +#: ../../admin/faqs.en.rst:355 +msgid "" +"If necessary, you can reset the maximum number of connections supported by " +"Traffic Server by editing the value of the :ref:`proxy.config.net." +"connections_throttle` configuration variable in the records.config file. Do " +"not increase the connection throttle limit unless the system has adequate " +"memory to handle the client connections required. A system with limited RAM " +"might need a throttle limit lower than the default value. Do not set this " +"variable below the minimum value of 100." +msgstr "" +"必要であれば、records.config ファイルの :ref:`proxy.config.net." +"connections_throttle` 設定変数を編集して Traffic Server がサポートする最大接" +"続数を再設定することができます。システムがクライアントの接続を扱うのに必要と" +"される十分なメモリーを持っていない限りは connection throttle 制限を増加しな" +"いでください。限られた RAM を持つシステムはデフォルト値よりも低い throttle " +"制限が必要かもしれません。この変数を最低値の 100 よりも低く設定しないでくだ" +"さい。" + +#: ../../admin/faqs.en.rst:365 +msgid "Low memory symptoms" +msgstr "メモリ不足の兆候" + +#: ../../admin/faqs.en.rst:367 +msgid "" +"Under heavy load, the Linux kernel can run out of RAM. This low memory " +"condition can cause slow performance and a variety of other system " +"problems. In fact, RAM exhaustion can occur even if the system has plenty " +"of free swap space." +msgstr "" +"高負荷な状態において、Linux カーネルは RAM を使い切る可能性があります。この" +"メモリの少ない状態はパフォーマンスの低下とその他様々なシステムの問題を引き起" +"こします。事実、RAM の枯渇 はシステムが豊富な空きスワップ領域を持っていたと" +"しても発生し得ます。" + +#: ../../admin/faqs.en.rst:372 +msgid "" +"Symptoms of extreme memory exhaustion include the following messages in the " +"system log files (``/var/log/messages``)::" +msgstr "" +"極限のメモリー消耗の兆候はシステムログファイル (``/var/log/messages``) の次" +"のメッセージを含みます。" + +#: ../../admin/faqs.en.rst:381 +msgid "" +"To avoid memory exhaustion, add more RAM to the system or reduce the load " +"on Traffic Server." +msgstr "" +"メモリーの消耗を防ぐために、システムにもっと RAM を追加するか Traffic " +"Server の負荷を減らしてください。" + +#: ../../admin/faqs.en.rst:385 +msgid "Connection timeouts with the origin server" +msgstr "オリジンサーバーとの接続タイムアウト" + +#: ../../admin/faqs.en.rst:387 +msgid "" +"Certain origin servers take longer than 30 seconds to post HTTP requests, " +"which results in connection timeouts with Traffic Server. To prevent such " +"connection timeouts, you must change the value of the configuration " +"variable proxy.config.http.connect_attempts_timeout in the records.config " +"file to 60 seconds or more." +msgstr "" +"いくらかのオリジンサーバーが HTTP リクエストを投稿するのに 30 秒以上を費や" +"し、これが Traffic Server で接続タイムアウトとなります。このような接続タイム" +"アウトを防ぐためには、records.config ファイルの proxy.config.http." +"connect_attempts_timeout 設定変数を 60 秒かそれ以上に変更しなければなりませ" +"ん。" + +#: ../../admin/faqs.en.rst:32 +msgid "" +"Create a large file on filesystem (with :manpage:`dd(1)`) and mount it as " +"loopback device. This is accomplished with :manpage:`losetup(8)` on Linux, :" +"manpage:`lofiadm(1m)` on Solaris and Illumos, and :manpage:`mdconfig(8)` on " +"FreeBSD." +msgstr "" +"ファイルシステム上に大きなファイルを ( :manpage:`dd(1)` を使って ) 作成し、" +"それをループバックデバイスとしてマウントしてください。これは Linux 上では :" +"manpage:`losetup(8)` で、Solaris と Illumos 上では :manpage:`lofiadm(1m)` 、" +"FreeBSD 上では :manpage:`mdconfig(8)` を使って行えます。" + +#: ../../admin/faqs.en.rst:125 +msgid "" +"The ``Via`` header string can be decoded with the `Via Decoder Ring `_." +msgstr "" +"``Via`` ヘッダー文字列は `Via Decoder Ring `_ でデコードできます。" + +#: ../../admin/faqs.en.rst:213 +msgid "" +"This is a Web browser issue and not a problem specific to (or caused by) " +"Traffic Server. Because Web browsers maintain a separate local cache in " +"memory and/or disk on the client system, messages about documents that have " +"expired from cache refer to the browser's local cache and *not* to the " +"Traffic Server cache. There is no Traffic Server message or condition that " +"can cause such messages to appear in a web browser." +msgstr "" +"これはウェブブラウザーの課題であり、Traffic Server に限ったもの ( もしく" +"は引き起こされるもの ) ではありません。ウェブブラウザーはクライアントシス" +"テム上にメモリと/またはディスクに別にローカルキャッシュを持っているので、" +"有効期限の切れたドキュメントに関するメッセージは Traffic Server のキャッ" +"シュでは\\ *なく*\\ ブラウザーのローカルキャッシュを参照します。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/forward-proxy.en.po b/doc/locale/ja/LC_MESSAGES/admin/forward-proxy.en.po new file mode 100644 index 00000000000..ee73a72976d --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/forward-proxy.en.po @@ -0,0 +1,139 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/forward-proxy.en.rst:4 +msgid "Forward Proxy" +msgstr "フォワードプロキシー" + +#: ../../admin/forward-proxy.en.rst:23 +msgid "" +"The Apache Traffic Server is a general purpose *proxy*. As such it can also " +"be used as forward proxy." +msgstr "" +"Apache Traffic Server は汎用の\\ *プロキシー*\\ です。つまりフォワードプロキ" +"シーとしても使用できます。" + +#: ../../admin/forward-proxy.en.rst:26 +msgid "" +"A forward proxy is can be used as a central tool in your infrastructure to " +"access the web. In combination with a cache that means overall reduced " +"bandwidth usage." +msgstr "" +"フォワードプロキシーは Web へアクセスするためのインフラの中心となるツールと" +"して使われます。キャッシュと組み合わせることで使用帯域を削減できます。" + +#: ../../admin/forward-proxy.en.rst:30 +msgid "" +"If your forward proxy is not also configured as :ref:`transparent-proxy` " +"your clients will have to be configured to actually use it." +msgstr "" +"フォワードプロキシーが :ref:`transparent-proxy` として設定されていない場合は" +"クライアントがそれを使うように設定する必要があるでしょう。" + +#: ../../admin/forward-proxy.en.rst:33 +msgid "" +"The main difference between a forward and a transparent proxy is that User " +"Agents *know* that they are accessing a proxy, thus forming their requests " +"like so: ::" +msgstr "" +"フォワードプロキシーと透過プロキシーの主な違いはユーザーエージェントがプロキ" +"シーにアクセスしていることを\\ *知っている*\\ ことで、次のようにリクエストを" +"行います。::" + +#: ../../admin/forward-proxy.en.rst:39 +msgid "This request, then is translated by the proxy to::" +msgstr "このリクエストはプロキシーによって次のように変換されます。::" + +#: ../../admin/forward-proxy.en.rst:44 +msgid "" +"Apache Traffic Server offers two ways to User Agents: They can either be " +"pointed directly to the default ``8080`` port. Alternatively, they can be " +"pointed to the more dynamic :ts:cv:`proxy.config.url_remap." +"default_to_server_pac`" +msgstr "" +"Apache Traffic Server はユーザーエージェントに二通りの方法を提供します。どち" +"らもデフォルトの ``8080`` ポートを直接指定できます。あるいは、より動的にも指" +"定できます。:ts:cv:`proxy.config.url_remap.default_to_server_pac`" + +#: ../../admin/forward-proxy.en.rst:48 +msgid "" +"This port will then serve a JavaScript like configuration that User Agents " +"can use to determine where to send their requests to." +msgstr "" +"このポートはユーザーエージェントがどこにリクエストを送るのかを決定するための" +"設定ファイルのような JavaScript を返します。" + +#: ../../admin/forward-proxy.en.rst:52 +msgid "Configuration" +msgstr "設定" + +#: ../../admin/forward-proxy.en.rst:57 +msgid ":ts:cv:`proxy.config.url_remap.remap_required` to ``0``" +msgstr ":ts:cv:`proxy.config.url_remap.remap_required` を ``0`` にする" + +#: ../../admin/forward-proxy.en.rst:59 +msgid "" +"If your proxy is serving as *pure* forward proxy, you will also want to set" +msgstr "" +"プロキシーが\\ *ピュアな*\\ フォワードプロキシーの場合、次の設定も必要となる" +"でしょう。" + +#: ../../admin/forward-proxy.en.rst:62 +msgid ":ts:cv:`proxy.config.reverse_proxy.enabled` to ``0``" +msgstr ":ts:cv:`proxy.config.reverse_proxy.enabled` を ``0`` にする" + +#: ../../admin/forward-proxy.en.rst:64 +msgid "Other configuration variables to consider:" +msgstr "その他に考慮すべき設定変数は次のとおりです。" + +#: ../../admin/forward-proxy.en.rst:66 +msgid ":ts:cv:`proxy.config.http.no_dns_just_forward_to_parent`" +msgstr ":ts:cv:`proxy.config.http.no_dns_just_forward_to_parent`" + +#: ../../admin/forward-proxy.en.rst:67 +msgid ":ts:cv:`proxy.config.http.forward.proxy_auth_to_parent`" +msgstr ":ts:cv:`proxy.config.http.forward.proxy_auth_to_parent`" + +#: ../../admin/forward-proxy.en.rst:68 +msgid ":ts:cv:`proxy.config.http.insert_squid_x_forwarded_for`" +msgstr ":ts:cv:`proxy.config.http.insert_squid_x_forwarded_for`" + +#: ../../admin/forward-proxy.en.rst:71 +msgid "Security Considerations" +msgstr "セキュリティの考慮" + +#: ../../admin/forward-proxy.en.rst:73 +msgid "" +"It's important to note that once your Apache Traffic Server is configured " +"as forward proxy it will indiscriminately accept proxy requests from " +"anyone. That means, if it's reachable on the internet, you have configured " +"an *Open Proxy*. Most of the time, this is *not* what you want, so you'll " +"have to make sure it's either only reachable within your NAT or is secured " +"by firewall rules that permit only those clients to access it which you " +"want to it to access." +msgstr "" +"Apache Traffic Server をフォワードプロキシーとして設定すると誰からのリクエス" +"トでも無差別に受け付けてしまうことに注意することが重要です。これは、もしイン" +"ターネットからアクセス可能な場合、\\ *オープンプロキシー*\\ を作ってしまった" +"ことを意味します。ほとんどの場合これは望んでいるものでは\\ *ない*\\ ので、" +"NAT からのみアクセス可能、もしくはファイアーウォールのルールによりアクセスさ" +"せたいクライアントだけにアクセスを許すよう保護されることを確かにしておく必要" +"があります。" + +#: ../../admin/forward-proxy.en.rst:54 +msgid "" +"In order to configure Apache Traffic Server as forward proxy you will have " +"to edit :file:`records.config` and set" +msgstr "" +"Apache Traffic Server をフォワードプロキシーとして設定するためには :file:" +"`records.config` を編集し次の設定を行う必要があります。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/getting-started.en.po b/doc/locale/ja/LC_MESSAGES/admin/getting-started.en.po new file mode 100644 index 00000000000..13a9b8f1056 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/getting-started.en.po @@ -0,0 +1,333 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: 2013-11-23 01:06+0900\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/getting-started.en.rst:5 +msgid "Getting Started" +msgstr "はじめに" + +#: ../../admin/getting-started.en.rst:29 +msgid "Before you start" +msgstr "始める前に" + +#: ../../admin/getting-started.en.rst:31 +msgid "" +"Before you get started with Traffic Server you may have to decide which " +"version you want to use. Traffic Server follows the `Semantic Versioning " +"`_ guidelines, in summary" +msgstr "" +"Traffic Server を使い始める前に、どのバージョンを使うか決める必要がありま" +"す。Traffic Server は `Semantic Versioning`_ ガイドライン" +"に従っています。" + +#: ../../admin/getting-started.en.rst:35 +msgid "A version is made of a version-triplet: ``MAJOR.MINOR.PATCH``" +msgstr "" +"バージョンは次のような 3つ組みのバージョンで構成されています。 ``MAJOR." +"MINOR.PATCH``" + +#: ../../admin/getting-started.en.rst:37 +msgid "" +"As of v4.0.0, there are no longer any development (or unstable) releases. " +"All releases are considered stable and ready for production use, releases " +"within a major version are always upgrade compatible. More details are " +"available on the `Wiki page `_." +msgstr "" +"v4.0.0 から開発版(もしくは非安定版) リリースを行わなくなりました。全てのリ" +"リースは安定性を考慮され、プロダクションでの使用の準備ができています。メ" +"ジャーバージョンの同じリリースは常に後方互換性を持っています。詳しくは " +"`Wiki page `_ にあります。" + +#: ../../admin/getting-started.en.rst:43 +msgid "" +"Sometimes we speak of trunk, master or HEAD, all of which are used " +"interchangeably: trunk or master or sometimes TIP or HEAD, refer to the " +"latest code in a Git Version Control System. Master is always kept " +"releasable, and compatible with the current major release version. " +"Incompatible changes are sometimes committed on a next-major release " +"branch, for example we have the ``5.0.x`` branch where changes incompatible " +"with 4.x are managed." +msgstr "" +"トランクやマスターもしくはヘッドと言うこともありますが、これらは同じ意味で使" +"われています。トランクやマスターまた TIP や HEAD は Git Version Control " +"System での最新のコードを指します。マスターは常にリリース可能な状態に保たれ" +"ており、カレントのメジャーリリースバージョンと互換性があります。互換性のない" +"変更は next-major リリースブランチにコミットされることがあります。例えば 4." +"x と互換性のない変更が管理されている ``5.0.x`` というブランチがあります。" + +#: ../../admin/getting-started.en.rst:50 +msgid "" +"If your distribution does not come with a prepackaged Traffic Server, " +"please go to `downloads `_ to choose the version that you " +"consider most appropriate for yourself. If you want to really be on the " +"bleeding edge you can clone our `git repository `_." +msgstr "" +"お使いのディストリビューションが Traffic Server をあらかじめパッケージしてい" +"ない場合、 `downloads `_ へ行き、最も適切だと考えられるバージョ" +"ンを選んでください。最先端のものが本当に欲しい場合は `git repository " +"`_ をクローンして" +"ください。" + +#: ../../admin/getting-started.en.rst:56 +msgid "" +"Please note that while we do have a `GitHub Mirror `_ that you can also use to submit pull requests, it " +"may not be entirely up-to-date." +msgstr "" +"Pull-Request を送ることができる `GitHub Mirror `_ を持っていますが、これは最新版ではないかもしれないことに注" +"意してください。" + +#: ../../admin/getting-started.en.rst:61 +msgid "Building Traffic Server" +msgstr "Traffic Server のビルド" + +#: ../../admin/getting-started.en.rst:63 +msgid "" +"In order to build Traffic Server from source you will need the following " +"(development) packages:" +msgstr "" +"Traffic Server をソースコードからビルドするために、次の(開発)パッケージが必" +"要です。" + +#: ../../admin/getting-started.en.rst:66 +msgid "pkgconfig" +msgstr "pkgconfig" + +#: ../../admin/getting-started.en.rst:67 +msgid "libtool" +msgstr "libtool" + +#: ../../admin/getting-started.en.rst:68 +msgid "gcc (>= 4.3 or clang > 3.0)" +msgstr "gcc (>= 4.3 or clang > 3.0)" + +#: ../../admin/getting-started.en.rst:69 +msgid "make (GNU Make!)" +msgstr "make (GNU Make!)" + +#: ../../admin/getting-started.en.rst:70 +msgid "openssl" +msgstr "openssl" + +#: ../../admin/getting-started.en.rst:71 +msgid "tcl" +msgstr "tcl" + +#: ../../admin/getting-started.en.rst:72 +msgid "expat" +msgstr "expat" + +#: ../../admin/getting-started.en.rst:73 +msgid "pcre" +msgstr "pcre" + +#: ../../admin/getting-started.en.rst:74 +msgid "libcap" +msgstr "libcap" + +#: ../../admin/getting-started.en.rst:75 +msgid "flex (for TPROXY)" +msgstr "flex (for TPROXY)" + +#: ../../admin/getting-started.en.rst:76 +msgid "hwloc" +msgstr "hwloc" + +#: ../../admin/getting-started.en.rst:77 +msgid "lua" +msgstr "lua" + +#: ../../admin/getting-started.en.rst:78 +msgid "curses" +msgstr "curses" + +#: ../../admin/getting-started.en.rst:81 +msgid "if you're building from a git clone, you'll also need" +msgstr "git クローンからビルドする場合は、次のものも必要です。" + +#: ../../admin/getting-started.en.rst:83 +msgid "git" +msgstr "git" + +#: ../../admin/getting-started.en.rst:84 +msgid "autoconf" +msgstr "autoconf" + +#: ../../admin/getting-started.en.rst:85 +msgid "automake" +msgstr "automake" + +#: ../../admin/getting-started.en.rst:87 +msgid "We will show-case a build from git::" +msgstr "git からビルドする例をお見せしましょう。" + +#: ../../admin/getting-started.en.rst:91 +msgid "Next, we ``cd trafficserver`` and run::" +msgstr "次に、``cd trafficserver`` を実行し、次のコマンドを実行します。" + +#: ../../admin/getting-started.en.rst:95 +msgid "" +"This will generate a ``configure`` file from ``configure.ac``, so now we " +"can run that::" +msgstr "" +"これは ``configure`` ファイルを ``configure.ac`` から生成するので、次のコマ" +"ンドを実行できます。" + +#: ../../admin/getting-started.en.rst:100 +msgid "" +"Note well, that by default Traffic Server uses the user ``nobody``, as well " +"as user's primary group as Traffic Server user. If you want to change that, " +"you can override it here::" +msgstr "" +"デフォルトでは Traffic Server ユーザーとして ``nobody`` ユーザーを使用するこ" +"とに注意してください。プライマリーグループについても同様です。これを変更した" +"い場合、上書きすることができます。" + +#: ../../admin/getting-started.en.rst:106 +msgid "" +"If dependencies are not in standard paths (``/usr/local`` or ``/usr``), you " +"need to pass options to ``configure`` to account for that::" +msgstr "" +"標準的なパス ( ``/usr/local`` や ``/usr`` ) に依存関係がない場合、次のよう" +"に ``configure`` にオプションを通す必要があります。" + +#: ../../admin/getting-started.en.rst:111 +msgid "" +"Most ``configure`` path-options accept a format of ``\"INCLUDE_PATH:" +"LIBRARY_PATH\"``::" +msgstr "" +"ほとんどの ``configure`` パスオプションは ``\"INCLUDE_PATH:LIBRARY_PATH\"`` " +"というフォーマットを受け入れます。" + +#: ../../admin/getting-started.en.rst:117 +msgid "" +"We can run ``make`` to build the project. We highly recommend to run ``make " +"check`` to verify the build's general sanity::" +msgstr "" +"プロジェクトをビルドするために ``make`` コマンドを実行しましょう。ビルドの一" +"般的な正常さを確かめるために ``make check`` コマンドを実行することを強く推奨" +"します。" + +#: ../../admin/getting-started.en.rst:123 +msgid "" +"We can finally run ``make install`` to install (you may have to switch to " +"root to do this)::" +msgstr "" +"最後に ``make install`` コマンドを実行しましょう。(おそらく root になること" +"が必要でしょう)" + +#: ../../admin/getting-started.en.rst:128 +msgid "" +"We also recommend to run a regression test. Please note that this will only " +"work successfully with the default ``layout``::" +msgstr "" +"レグレッションテストを実行することも推奨します。これはデフォルト``レイアウト" +"``で正常に動作することに注意してください。" + +#: ../../admin/getting-started.en.rst:134 +msgid "" +"After you have installed Traffic Server on your system, you can do any of " +"the following:" +msgstr "" +"Traffic Server をシステム上にインストールした後、次のどれでもできます。" + +#: ../../admin/getting-started.en.rst:140 +msgid "Start Traffic Server" +msgstr "Traffic Server を起動する" + +#: ../../admin/getting-started.en.rst:142 +msgid "" +"To start Traffic Server manually, issue the ``trafficserver`` command, " +"passing in the attribute ``start``. This command starts all the processes " +"that work together to process Traffic Server requests as well as manage, " +"control, and monitor the health of the Traffic Server system." +msgstr "" +"Traffic Server を手動で起動するには ``trafficserver`` コマンドに ``start`` " +"を発行します。このコマンドは Traffic Server へのリクエストを処理したり、" +"Traffic Server システムの状態を管理、制御、監視するためのすべてのプロセスを" +"起動します。" + +#: ../../admin/getting-started.en.rst:147 +msgid "To run the ``trafficserver start`` command, e.g.::" +msgstr "``trafficserver start`` コマンドを実行するには次のようにします。" + +#: ../../admin/getting-started.en.rst:151 +msgid "" +"At this point your server is up and running in the default configuration of " +"a :ref:`reverse-proxy-and-http-redirects`." +msgstr "" +"この時点でサーバーは :ref:`../reverse-proxy-http-redirects` のデフォルト設定" +"で起動し、動作しています。" + +#: ../../admin/getting-started.en.rst:157 +msgid "Start Traffic Line" +msgstr "Traffic Line を使用する" + +#: ../../admin/getting-started.en.rst:159 +msgid "" +"Traffic Line provides a quick way of viewing Traffic Server statistics and " +"configuring the Traffic Server system via command-line interface. To " +"execute individual commands or script multiple commands, refer to :program:" +"`traffic_line`." +msgstr "" +"Traffic Line は Traffic Server の統計を見たり、コマンドラインインターフェー" +"スによる Traffic Server の設定をする簡単な方法を提供しています。独立したコマ" +"ンドの実行または複数のコマンドのスクリプトについては :program:" +"`traffic_line` を参照してください。" + +#: ../../admin/getting-started.en.rst:164 +msgid "Traffic Line commands take the following form::" +msgstr "Traffic Line コマンドは次のようなフォームを受け取ります。" + +#: ../../admin/getting-started.en.rst:168 +msgid "For a list of :program:`traffic_line` commands, enter::" +msgstr "" +":program:`traffic_line` のコマンドのリストを見るにはこのように実行してくださ" +"い。" + +#: ../../admin/getting-started.en.rst:172 +msgid "" +"Please note that :program:`traffic_line`, while a fine tool for an " +"administrator, is a poor choice for automation, especially that of " +"monitoring. See our chapter on :ref:`monitoring-traffic` for how to do that " +"better." +msgstr "" +"次のことに注意してください。 :program:`traffic_line` は管理者にとっては十分" +"なツールである一方で、自動化のためには貧弱な選択です。とくに監視については。" +"正しく監視する方法については :ref:`monitoring-traffic` の章を参照してくださ" +"い。" + +#: ../../admin/getting-started.en.rst:180 +msgid "Stop Traffic Server" +msgstr "Traffic Server を停止する" + +#: ../../admin/getting-started.en.rst:182 +msgid "" +"To stop Traffic Server, always use the :program:`trafficserver` command, " +"passing in the attribute ``stop``. This command stops all the Traffic " +"Server processes (:program:`traffic_manager`, :program:`traffic_server`, " +"and :program:`traffic_cop`). Do not manually stop processes, as this can " +"lead to unpredictable results.::" +msgstr "" +"Traffic Server を停止するには常に :program:`trafficserver` コマンドに " +"``stop`` を渡します。このコマンドは全ての Traffic Server プロセス ( :" +"program:`traffic_manager`, :program:`traffic_server`, :program:" +"`traffic_cop` ) を停止します。予想できない結果を招くので、手動で各プロセスを" +"止めないでください。" + +#: ../../admin/getting-started.en.rst:79 +msgid "curl (both for :program:`traffic_top`)" +msgstr "curl (both for :program:`traffic_top`)" diff --git a/doc/locale/ja/LC_MESSAGES/admin/hierachical-caching.en.po b/doc/locale/ja/LC_MESSAGES/admin/hierachical-caching.en.po new file mode 100644 index 00000000000..be1520537ca --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/hierachical-caching.en.po @@ -0,0 +1,169 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/hierachical-caching.en.rst:4 +msgid "Hierarchical Caching" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:28 +msgid "Understanding Cache Hierarchies" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:30 +msgid "" +"A cache hierarchy consists of cache levels that communicate with each " +"other. Traffic Server supports several types of cache hierarchies. All " +"cache hierarchies recognize the concept of **parent** and **child**. A " +"parent cache is a cache higher up in the hierarchy, to which Traffic Server " +"can forward requests. A child cache is a cache for which Traffic Server is " +"a parent." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:37 +msgid "Traffic Server supports the following hierarchical caching options:" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:40 +msgid "Parent Caching" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:42 +msgid "" +"If a Traffic Server node cannot find a requested object in its cache, then " +"it searches a parent cache (which itself can search other caches) before " +"finally retrieving the object from the origin server. You can configure a " +"Traffic Server node to use one or more parent caches so that if one parent " +"is unavailable, then another parent is availale to service requests. This " +"is called `Parent Failover`_. Traffic Server will support parent caching " +"for HTTP and HTTPS requests." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:55 +msgid "" +"The figure below illustrates a simple cache hierarchy with a Traffic Server " +"node configured to use a parent cache. In the following scenario, a client " +"sends a request to a Traffic Server node that is a child in the cache " +"hierarchy (because it's configured to forward missed requests to a parent " +"cache). The request is a cache miss, so Traffic Server then forwards the " +"request to the parent cache, where it is a cache hit. The parent sends a " +"copy of the content to the Traffic Server, where it is cached and then " +"served to the client. Future requests for this content can now be served " +"directly from the Traffic Server cache (until the data is stale or expired)." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:70 +msgid "Parent caching" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:72 +msgid "" +"**Note:** If the request is a cache miss on the parent, then the parent " +"retrieves the content from the origin server (or from another cache, " +"depending on the parent’s configuration). The parent caches the content and " +"then sends a copy to Traffic Server (its child), where it is cached and " +"served to the client." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:79 +msgid "Parent Failover" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:81 +msgid "" +"Traffic Server supports use of several parent caches. This ensures that if " +"one parent cache is not available, another parent cache can service client " +"requests." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:85 +msgid "" +"When you configure your Traffic Server to use more than one parent cache, " +"Traffic Server detects when a parent is not available and sends missed " +"requests to another parent cache. If you specify more than two parent " +"caches, then the order in which the parent caches are queried depends upon " +"the parent proxy rules configured in the file:`parent.config` configuration " +"file. By default, the parent caches are queried in the order they are " +"listed in the configuration file." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:96 +msgid "Configuring Traffic Server to Use a Parent Cache" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:98 +msgid "" +"To configure Traffic Server to use one or more parent caches, you must " +"complete the following steps:" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:101 +msgid "Enable the parent caching option." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:102 +msgid "" +"Identify the parent cache you want to use to service missed requests. To " +"use **parent failover**, you must identify more than one parent cache so " +"that when a parent cache is unavailable, requests are sent to another " +"parent cache." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:107 +msgid "" +"You need to configure the child cache only. No additional configuration is " +"needed for the Traffic Server parent cache." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:109 +msgid "" +"Configure Traffic Server to use a parent cache by editing the following " +"variable :ts:cv:`proxy.config.http.parent_proxy_routing_enable` in :file:" +"`records.config` file." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:112 +msgid "" +"Edit the :file:`parent.config` file located in the Traffic Server " +"``config`` directory to set parent proxy rules to specify the parent cache " +"to which you want missed requests to be forwarded;" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:116 +msgid "" +"The following example configures Traffic Server to route all requests " +"containing the regular expression ``politics`` and the path ``/viewpoint`` " +"directly to the origin server (bypassing any parent hierarchies): ::" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:123 +msgid "" +"The following example configures Traffic Server to direct all missed " +"requests with URLs beginning with ``http://host1`` to the parent cache " +"``parent1``. If ``parent1`` cannot serve the requests, then requests are " +"forwarded to ``parent2``. Because ``round-robin=true``, Traffic Server goes " +"through the parent cache list in a round-robin based on client IP address.::" +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:132 +msgid "" +"Run the command :option:`traffic_line -x` to apply the configuration " +"changes." +msgstr "" + +#: ../../admin/hierachical-caching.en.rst:50 +msgid "" +"**Note:** If you do not want all requests to go to the parent cache, then " +"simply configure Traffic Server to route certain requests (such as requests " +"containing specific URLs) directly to the origin server. Simply set parent " +"proxy rules in :file:`parent.config`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/admin/http-proxy-caching.en.po b/doc/locale/ja/LC_MESSAGES/admin/http-proxy-caching.en.po new file mode 100644 index 00000000000..83de3d33436 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/http-proxy-caching.en.po @@ -0,0 +1,1870 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: 2013-12-15 14:15+0900\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/http-proxy-caching.en.rst:4 +msgid "HTTP Proxy Caching" +msgstr "HTTP プロキシーキャッシュ" + +#: ../../admin/http-proxy-caching.en.rst:23 +msgid "" +"Web proxy caching enables you to store copies of frequently-accessed web " +"objects (such as documents, images, and articles) and then serve this " +"information to users on demand. It improves performance and frees up " +"Internet bandwidth for other tasks." +msgstr "" +"ウェブプロキシーキャッシュは頻繁にアクセスされるウェブオブジェクト(ドキュメ" +"ントや画像、記事など)のコピーを保存し、ユーザーの求めに応じてこれらを配信す" +"ることを可能にします。これはパフォーマンスを向上させ、インターネットの帯域を" +"他のタスクのために空けます。" + +#: ../../admin/http-proxy-caching.en.rst:32 +msgid "Understanding HTTP Web Proxy Caching" +msgstr "HTTP ウェブプロキシーキャッシュの理解" + +#: ../../admin/http-proxy-caching.en.rst:34 +msgid "" +"Internet users direct their requests to web servers all over the Internet. " +"A caching server must act as a **web proxy server** so it can serve those " +"requests. After a web proxy server receives requests for web objects, it " +"either serves the requests or forwards them to the **origin server** (the " +"web server that contains the original copy of the requested information). " +"The Traffic Server proxy supports **explicit proxy caching**, in which the " +"user's client software must be configured to send requests directly to the " +"Traffic Server proxy. The following overview illustrates how Traffic Server " +"serves a request." +msgstr "" +"インターネットユーザはインターネット上のウェブサーバーへリクエストを出しま" +"す。キャッシュサーバーはこれらのリクエストを満たすために **ウェブプロキシ" +"サーバー** として振る舞わなくてはなりません。ウェブプロキシーサーバーがウェ" +"ブオブジェクトへのリクエストを受け取った後は、そのリクエストを返すか、**オリ" +"ジンサーバー** (リクエストされた情報のオリジナルコピーを持っているウェブサー" +"バー)へ転送します。Traffic Server プロキシーは **explicit proxy caching** を" +"サポートしています。この際、ユーザーのクライアントソフトが Traffic Server プ" +"ロキシーへ直接リクエストを送るように設定されている必要があります。次のオー" +"バービューは Traffic Server がどのようにリクエストを返すかを描いています。" + +#: ../../admin/http-proxy-caching.en.rst:44 +msgid "Traffic Server receives a client request for a web object." +msgstr "" +"Traffic Server がウェブオブジェクトへのクライアントリクエストを受け取りま" +"す。" + +#: ../../admin/http-proxy-caching.en.rst:46 +msgid "" +"Using the object address, Traffic Server tries to locate the requested " +"object in its object database (**cache**)." +msgstr "" +"オブジェクトのアドレスを用いて、Traffic Server はオブジェクトデータベース" +"( **キャッシュ** )からリクエストされたオブジェクトを探します。" + +#: ../../admin/http-proxy-caching.en.rst:49 +msgid "" +"If the object is in the cache, then Traffic Server checks to see if the " +"object is fresh enough to serve. If it is fresh, then Traffic Server serves " +"it to the client as a **cache hit** (see the figure below)." +msgstr "" +"キャッシュにオブジェクトがある場合、Traffic Server はオブジェクトが提供する" +"のに十分新しいか確認します。新しい場合、Traffic Server は *キャッシュヒット" +"* (下の図を見てください) としてクライアントにそれを提供します。" + +#: ../../admin/http-proxy-caching.en.rst:58 +msgid "A cache hit" +msgstr "キャッシュヒット" + +#: ../../admin/http-proxy-caching.en.rst:60 +msgid "" +"If the data in the cache is stale, then Traffic Server connects to the " +"origin server and checks if the object is still fresh (a :term:" +"`revalidation`). If it is, then Traffic Server immediately sends the cached " +"copy to the client." +msgstr "" +"キャッシュのデータが古い場合、Traffic Server はオリジンサーバーへ接続し、オ" +"ブジェクトが依然新しいかどうか確認します。( :term:`再確認` ) 新しい場合、" +"Traffic Server はすぐにキャッシュしているコピーをクライアントに送ります。" + +#: ../../admin/http-proxy-caching.en.rst:65 +msgid "" +"If the object is not in the cache (a **cache miss**) or if the server " +"indicates the cached copy is no longer valid, then Traffic Server obtains " +"the object from the origin server. The object is then simultaneously " +"streamed to the client and the Traffic Server local cache (see the figure " +"below). Subsequent requests for the object can be served faster because the " +"object is retrieved directly from cache." +msgstr "" +"オブジェクトがキャッシュに無い場合 ( **キャッシュミス**) やサーバーがキャッ" +"シュしたコピーをもはや有効ではないと判断した場合、 Traffic Server はオリジン" +"サーバーからオブジェクトを取得します。オブジェクトはクライアントと Traffic " +"Server のローカルキャッシュに同時に流されます。(下の図を見てください) 続いて" +"起こるオブジェクトへのリクエストはよりはやく提供することができます。それはオ" +"ブジェクトがキャッシュから直接検索されるからです。" + +#: ../../admin/http-proxy-caching.en.rst:76 +msgid "A cache miss" +msgstr "キャッシュミス" + +#: ../../admin/http-proxy-caching.en.rst:78 +msgid "" +"Caching is typically more complex than the preceding overview suggests. In " +"particular, the overview does not discuss how Traffic Server ensures " +"freshness, serves correct HTTP alternates, and treats requests for objects " +"that cannot/should not be cached. The following sections discuss these " +"issues in greater detail." +msgstr "" +"一般的にキャッシュは前述の概要で説明したものよりも複雑です。 詳しく述べる" +"と、概要では Traffic Server がどのように新鮮さを保証し、正しい HTTP オブジェ" +"クトの代替を提供し、キャッシュできない/するべきではないオブジェクトへのリク" +"エストを扱うかについて説明されていませんでした。次の章はこれらのことについて" +"とても詳しく説明します。" + +#: ../../admin/http-proxy-caching.en.rst:85 +msgid "Ensuring Cached Object Freshness" +msgstr "キャッシュされたオブジェクトの新鮮さの保証" + +#: ../../admin/http-proxy-caching.en.rst:87 +msgid "" +"When Traffic Server receives a request for a web object, it first tries to " +"locate the requested object in its cache. If the object is in cache, then " +"Traffic Server checks to see if the object is fresh enough to serve. For " +"HTTP objects, Traffic Server supports optional author-specified expiration " +"dates. Traffic Server adheres to these expiration dates; otherwise, it " +"picks an expiration date based on how frequently the object is changing and " +"on administrator-chosen freshness guidelines. Objects can also be " +"revalidated by checking with the origin server to see if an object is still " +"fresh." +msgstr "" +"Traffic Server がウェブオブジェクトへのリクエストを受け取った際、最初にリク" +"エストされたオブジェクトをキャッシュから探します。オブジェクトがキャッシュに" +"ある場合、Traffic Server はオブジェクトが提供するのに十分新しいかどうかを確" +"認します。 Traffic Server は HTTP オブジェクトに作成者が指定した有効期限をサ" +"ポートしています。 Traffic Server はこれらの有効期限を固く守ります。つまり、" +"どれだけ頻繁にオブジェクトが変更されるかと、管理者が選んだフレッシュネスガイ" +"ドラインに基づいて、有効期限を選択します。オブジェクトはまた、依然として新し" +"いかどうかをオリジンサーバーへ見に行くことにより、再検証されます。" + +#: ../../admin/http-proxy-caching.en.rst:98 +msgid "HTTP Object Freshness" +msgstr "HTTP オブジェクトの新鮮さ" + +#: ../../admin/http-proxy-caching.en.rst:100 +msgid "" +"Traffic Server determines whether an HTTP object in the cache is fresh by:" +msgstr "" +"Traffic Server はキャッシュした HTTP オブジェクトが新しいかどうかを次のこと" +"によって決定します。" + +#: ../../admin/http-proxy-caching.en.rst:103 +msgid "**Checking the** ``Expires`` **or** ``max-age`` **header**" +msgstr "``Expires`` **や** ``max-age`` **ヘッダーの確認**" + +#: ../../admin/http-proxy-caching.en.rst:105 +msgid "" +"Some HTTP objects contain ``Expires`` headers or ``max-age`` headers that " +"explicitly define how long the object can be cached. Traffic Server " +"compares the current time with the expiration time to determine if the " +"object is still fresh." +msgstr "" +"いくつかの HTTP オブジェクトは ``Expire`` ヘッダーや ``max-age`` ヘッダーを" +"含んでいます。これらはオブジェクトがどれくらいの期間キャッシュできるかどうか" +"を明確に定義しています。 Traffic Server はオブジェクトが新しいかどうかを決定" +"するために、現在時刻と有効期限を比較します。" + +#: ../../admin/http-proxy-caching.en.rst:110 +msgid "**Checking the** ``Last-Modified`` **/** ``Date`` **header**" +msgstr "``Last-Modified`` **/** ``Date`` **ヘッダーの確認**" + +#: ../../admin/http-proxy-caching.en.rst:112 +msgid "" +"If an HTTP object has no ``Expires`` header or ``max-age`` header, then " +"Traffic Server can calculate a freshness limit using the following formula::" +msgstr "" +"HTTP オブジェクトが ``Expire`` ヘッダーや ``max-age`` ヘッダーを持っていない" +"場合、Traffic Server はフレッシュネスリミットを次の式で計算します。" + +#: ../../admin/http-proxy-caching.en.rst:118 +msgid "" +"where *date* is the date in the object's server response header and " +"*last_modified* is the date in the ``Last-Modified`` header. If there is no " +"``Last-Modified`` header, then Traffic Server uses the date the object was " +"written to cache. The value ``0.10`` (10 percent) can be increased or " +"reduced to better suit your needs (refer to `Modifying Aging Factor for " +"Freshness Computations`_)." +msgstr "" +"この *date* はオブジェクトのサーバーのレスポンスヘッダーの日付で、" +"*last_modified* は ``Last-Modified`` ヘッダーの日付です。 ``Last-Modified`` " +"ヘッダーが無い場合、Traffic Server はオブジェクトがキャッシュに書かれた日時" +"を使用します。 ``0.10`` (10 %) という値は必要に応じて、増減することができま" +"す。 (詳しくは `新鮮さの計算のための期間要素の変更`_ を参照してください)" + +#: ../../admin/http-proxy-caching.en.rst:125 +msgid "" +"The computed freshness limit is bound by a minimum and maximum value - " +"refer to `Setting Absolute Freshness Limits`_ for more information." +msgstr "" +"計算されたフレッシュネスリミットは最小値と最大値に紐づけられます。 - 詳細は " +"`絶対フレッシュネスリミットの設定`_ を参照してください。" + +#: ../../admin/http-proxy-caching.en.rst:128 +msgid "**Checking the absolute freshness limit**" +msgstr "**絶対フレッシュネスリミットの確認**" + +#: ../../admin/http-proxy-caching.en.rst:130 +msgid "" +"For HTTP objects that do not have ``Expires`` headers or do not have both " +"``Last-Modified`` and ``Date`` headers, Traffic Server uses a maximum and " +"minimum freshness limit (refer to `Setting Absolute Freshness Limits`_)." +msgstr "" +"``Expires`` ヘッダーを持っていない、もしくは ``Last-Modified`` と ``Date`` " +"ヘッダーの両方をもっていない HTTP オブジェクトについて、Traffic Server はフ" +"レッシュネスリミットの最小値と最大値を使用します。( `絶対フレッシュネスリ" +"ミットの設定`_ を参照してください。)" + +#: ../../admin/http-proxy-caching.en.rst:134 +msgid "**Checking revalidate rules in the** :file:`cache.config` **file**" +msgstr ":file:`cache.config` **ファイル内の再確認ルールの確認**" + +#: ../../admin/http-proxy-caching.en.rst:136 +msgid "" +"Revalidate rules apply freshness limits to specific HTTP objects. You can " +"set freshness limits for objects originating from particular domains or IP " +"addresses, objects with URLs that contain specified regular expressions, " +"objects requested by particular clients, and so on (refer to :file:`cache." +"config`)." +msgstr "" +"再検証ルールは特定の HTTP オブジェクトにフレッシュネスリミットを適用します。" +"特定のドメインや IP アドレスから来たオブジェクト、特定の正規表現を含む URL " +"を持つオブジェクトや特定のクライアントからリクエストされたオブジェクトなどに" +"フレッシュネスリミットを設定することができます。( :file:`cache.config` を参" +"照してください。)" + +#: ../../admin/http-proxy-caching.en.rst:143 +msgid "Modifying Aging Factor for Freshness Computations" +msgstr "新鮮さの計算のための期間要素の変更" + +#: ../../admin/http-proxy-caching.en.rst:145 +msgid "" +"If an object does not contain any expiration information, then Traffic " +"Server can estimate its freshness from the ``Last-Modified`` and ``Date`` " +"headers. By default, Traffic Server stores an object for 10% of the time " +"that elapsed since it last changed. You can increase or reduce the " +"percentage according to your needs." +msgstr "" +"オブジェクトが有効期限に関する情報を持っていない場合、Traffic Server は " +"``Last-Modified`` と ``Date`` ヘッダーから新鮮さを見積もります。デフォルトで" +"は Traffic Server は最後に更新されてからの経過時間の 10 % キャッシュしま" +"す。 必要に応じて、増減することができます。" + +#: ../../admin/http-proxy-caching.en.rst:151 +msgid "To modify the aging factor for freshness computations" +msgstr "新鮮さの計算のための期間の要素を変更するためには、" + +#: ../../admin/http-proxy-caching.en.rst:153 +msgid "" +"Change the value for :ts:cv:`proxy.config.http.cache.heuristic_lm_factor`." +msgstr "" +":ts:cv:`proxy.config.http.cache.heuristic_lm_factor` の値を変更してくださ" +"い。" + +#: ../../admin/http-proxy-caching.en.rst:155 +#: ../../admin/http-proxy-caching.en.rst:173 +#: ../../admin/http-proxy-caching.en.rst:192 +#: ../../admin/http-proxy-caching.en.rst:281 +#: ../../admin/http-proxy-caching.en.rst:332 +msgid "" +"Run the :option:`traffic_line -x` command to apply the configuration " +"changes." +msgstr "" +"設定変更を適用するために :option:`traffic_line -x` コマンドを実行してくださ" +"い。" + +#: ../../admin/http-proxy-caching.en.rst:159 +msgid "Setting absolute Freshness Limits" +msgstr "絶対フレッシュネスリミットの設定" + +#: ../../admin/http-proxy-caching.en.rst:161 +msgid "" +"Some objects do not have ``Expires`` headers or do not have both ``Last-" +"Modified`` and ``Date`` headers. To control how long these objects are " +"considered fresh in the cache, specify an **absolute freshness limit**." +msgstr "" +"いくつかのオブジェクトは ``Expires`` ヘッダーを持っていない、もしくは " +"``Last-Modified`` と ``Date`` ヘッダーの両方を持っていないことがあります。こ" +"れらのオブジェクトがキャッシュされてどの程度フレッシュであると考えられるか制" +"御するために、 **絶対フレッシュネスリミット** があります。" + +#: ../../admin/http-proxy-caching.en.rst:166 +msgid "To specify an absolute freshness limit" +msgstr "絶対フレッシュネスリミットを明確にするために" + +#: ../../admin/http-proxy-caching.en.rst:168 +msgid "Edit the variables" +msgstr "次の変数を変更してください。" + +#: ../../admin/http-proxy-caching.en.rst:170 +msgid ":ts:cv:`proxy.config.http.cache.heuristic_min_lifetime`" +msgstr ":ts:cv:`proxy.config.http.cache.heuristic_min_lifetime`" + +#: ../../admin/http-proxy-caching.en.rst:171 +msgid ":ts:cv:`proxy.config.http.cache.heuristic_max_lifetime`" +msgstr ":ts:cv:`proxy.config.http.cache.heuristic_max_lifetime`" + +#: ../../admin/http-proxy-caching.en.rst:177 +msgid "Specifying Header Requirements" +msgstr "必須ヘッダーの記述" + +#: ../../admin/http-proxy-caching.en.rst:179 +msgid "" +"To further ensure freshness of the objects in the cache, configure Traffic " +"Server to cache only objects with specific headers. By default, Traffic " +"Server caches all objects (including objects with no headers); you should " +"change the default setting only for specialized proxy situations. If you " +"configure Traffic Server to cache only HTTP objects with ``Expires`` or " +"``max-age`` headers, then the cache hit rate will be noticeably reduced " +"(since very few objects will have explicit expiration information)." +msgstr "" +"よりいっそうキャッシュしているオブジェクトの新鮮さを確かめるために、特定の" +"ヘッダーを持っているオブジェクトだけをキャッシュするように Traffic Server を" +"設定することができます。デフォルトでは Traffic Server は(ヘッダーがないもの" +"も含む)全てのオブジェクトをキャッシュします。特別なプロキシーの状況の場合の" +"みデフォルト設定を変更するべきです。Traffic Server を ``Expires`` もしくは " +"``max-age`` ヘッダーを持つオブジェクトだけをキャッシュするように設定した場" +"合、キャッシュヒット率は明らかに下がるでしょう。(とても少ないオブジェクトし" +"か明確な有効期限の情報をもっていないと考えられるためです。)" + +#: ../../admin/http-proxy-caching.en.rst:188 +msgid "To configure Traffic Server to cache objects with specific headers" +msgstr "" +"特定のヘッダーを持つオブジェクトをキャッシュするように Traffic Server を設定" +"するには" + +#: ../../admin/http-proxy-caching.en.rst:190 +msgid "" +"Change the value for :ts:cv:`proxy.config.http.cache.required_headers`." +msgstr "" +":ts:cv:`proxy.config.http.cache.required_headers` の値を変更してください。" + +#: ../../admin/http-proxy-caching.en.rst:198 +msgid "Cache-Control Headers" +msgstr "Cache-Control ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:200 +msgid "" +"Even though an object might be fresh in the cache, clients or servers often " +"impose their own constraints that preclude retrieval of the object from the " +"cache. For example, a client might request that a object *not* be retrieved " +"from a cache, or if it does, then it cannot have been cached for more than " +"10 minutes. Traffic Server bases the servability of a cached object on " +"``Cache-Control`` headers that appear in both client requests and server " +"responses. The following ``Cache-Control`` headers affect whether objects " +"are served from cache:" +msgstr "" +"キャッシュしたあるオブジェクトが新鮮だと思われる場合であっても、クライアント" +"やサーバーはキャッシュからのオブジェクトの読み出しを妨害するようにたびたび制" +"限を課します。例えば、あるクライアントがキャッシュから復旧するべき *ではない" +"* オブジェクトへリクエストするかもしれません。また、それをした場合、10 分以" +"上はキャッシュすることはできません。 Traffic Server はキャッシュしたオブジェ" +"クトの提供可能性をクライアントのリクエストとサーバーのレスポンス両方に現れ" +"る ``Cache-Control`` ヘッダーを根拠に決定しています。次のような ``Cache-" +"Control`` ヘッダーはキャッシュからオブジェクトを提供するかどうかに影響しま" +"す。" + +#: ../../admin/http-proxy-caching.en.rst:209 +msgid "" +"The ``no-cache`` header, sent by clients, tells Traffic Server that it " +"should not serve any objects directly from the cache; therefore, Traffic " +"Server will always obtain the object from the origin server. You can " +"configure Traffic Server to ignore client ``no-cache`` headers - refer to " +"`Configuring Traffic Server to Ignore Client no-cache Headers`_ for more " +"information." +msgstr "" +"クライアントから送られる ``no-cache`` ヘッダーはどんなオブジェクトもキャッ" +"シュから直接返すべきではないということを Traffic Server に示します。従って、" +"Traffic Server は常にオリジンサーバーからオブジェクトを取得します。 Traffic " +"Server をクライアントからの ``no-cache`` ヘッダーを無視するように設定するこ" +"ともできます。詳細は `クライアントの no-cache ヘッダーを無視する Traffic " +"Server の設定`_ を参照してください。" + +#: ../../admin/http-proxy-caching.en.rst:216 +msgid "" +"The ``max-age`` header, sent by servers, is compared to the object age. If " +"the age is less than ``max-age``, then the object is fresh and can be " +"served." +msgstr "" +"サーバーから送られる ``max-age`` ヘッダーはオブジェクトのキャッシュされてい" +"る時間と比較されます。この時間が ``max-age`` よりも少ない場合、オブジェクト" +"はフレッシュであり配信されます。" + +#: ../../admin/http-proxy-caching.en.rst:220 +msgid "" +"The ``min-fresh`` header, sent by clients, is an **acceptable freshness " +"tolerance**. This means that the client wants the object to be at least " +"this fresh. Unless a cached object remains fresh at least this long in the " +"future, it is revalidated." +msgstr "" +"クライアントからの ``min-fresh`` ヘッダーは **受け入れることが許容できる新鮮" +"さ** です。これはクライアントが少なくとも指定された程度新鮮であることを望ん" +"でいるということを意味します。将来、キャッシュされたオブジェクトがこの長さの" +"新鮮さを失った場合、再検証されます。" + +#: ../../admin/http-proxy-caching.en.rst:225 +msgid "" +"The ``max-stale`` header, sent by clients, permits Traffic Server to serve " +"stale objects provided they are not too old. Some browsers might be willing " +"to take slightly stale objects in exchange for improved performance, " +"especially during periods of poor Internet availability." +msgstr "" +"クライアントからの ``max-stale`` ヘッダーは Traffic Server に古すぎない失効" +"したオブジェクトを配信することを許可します。いくつかのブラウザーは特に貧弱な" +"インターネット環境にあるような場合パフォーマンスを向上させるため、わずかに失" +"効したオブジェクトを受け取ることを望むかもしれません。" + +#: ../../admin/http-proxy-caching.en.rst:231 +msgid "" +"Traffic Server applies ``Cache-Control`` servability criteria ***after*** " +"HTTP freshness criteria. For example, an object might be considered fresh " +"but will not be served if its age is greater than its ``max-age``." +msgstr "" +"Traffic Server は ``Cache-Control`` を HTTP の新鮮さの基準の ***後に*** 配信" +"可能性の基準に適用します。例えば、あるオブジェクトが新鮮だと考えられる場合で" +"も、経過時間が ``max-age`` よりも大きいければ、それは配信されません。" + +#: ../../admin/http-proxy-caching.en.rst:237 +msgid "Revalidating HTTP Objects" +msgstr "HTTP オブジェクトの再検証" + +#: ../../admin/http-proxy-caching.en.rst:239 +msgid "" +"When a client requests an HTTP object that is stale in the cache, Traffic " +"Server revalidates the object. A **revalidation** is a query to the origin " +"server to check if the object is unchanged. The result of a revalidation is " +"one of the following:" +msgstr "" +"クライアントがキャッシュの中で新鮮ではなくなった HTTP オブジェクトをリクエス" +"トした際、Traffic Server はそのオブジェクトを再検証します。**再検証** はオリ" +"ジンサーバーへオブジェクトが変更されているかどうかを確認する問い合わせです。" +"再検証の結果は次のいずれかです。" + +#: ../../admin/http-proxy-caching.en.rst:244 +msgid "" +"If the object is still fresh, then Traffic Server resets its freshness " +"limit and serves the object." +msgstr "" +"オブジェクトが依然として新鮮な場合、Traffic Server はフレッシュネスリミット" +"をリセットして、そのオブジェクトを配信します。" + +#: ../../admin/http-proxy-caching.en.rst:247 +msgid "" +"If a new copy of the object is available, then Traffic Server caches the " +"new object (thereby replacing the stale copy) and simultaneously serves the " +"object to the client." +msgstr "" +"オブジェクトの新しいコピーが有効な場合、Traffic Server は新しいオブジェクト" +"をキャッシュします。(従って、新鮮ではないコピーは置き換えられます)また、同時" +"にオブジェクトをクライアントに配信します。" + +#: ../../admin/http-proxy-caching.en.rst:251 +msgid "" +"If the object no longer exists on the origin server, then Traffic Server " +"does not serve the cached copy." +msgstr "" +"オブジェクトがオリジンサーバー上に存在しない場合、Traffic Server はキャッ" +"シュしたコピーを配信しません。" + +#: ../../admin/http-proxy-caching.en.rst:254 +msgid "" +"If the origin server does not respond to the revalidation query, then " +"Traffic Server serves the stale object along with a ``111 Revalidation " +"Failed`` warning." +msgstr "" +"オリジンサーバーが再検証の問い合わせに応答しない場合、Traffic Server は " +"``111 Revalidation Failed`` 警告と共に新鮮ではないオブジェクトを配信します。" + +#: ../../admin/http-proxy-caching.en.rst:258 +msgid "" +"By default, Traffic Server revalidates a requested HTTP object in the cache " +"if it considers the object to be stale. Traffic Server evaluates object " +"freshness as described in `HTTP Object Freshness`_. You can reconfigure how " +"Traffic Server evaluates freshness by selecting one of the following " +"options:" +msgstr "" +"デフォルトでは Traffic Server はリクエストされた HTTP オブジェクトが新鮮では" +"ないと考えられる場合に再検証します。Traffic Server のオブジェクトの新鮮さの" +"評価については `HTTP オブジェクトの新鮮さ`_ で述べられています。次のオプショ" +"ンの一つを選ぶことによって、 Traffic Server が新鮮さを評価する方法を再設定す" +"ることができます。" + +#: ../../admin/http-proxy-caching.en.rst:264 +msgid "" +"Traffic Server considers all HTTP objects in the cache to be stale: always " +"revalidate HTTP objects in the cache with the origin server." +msgstr "" +"Traffic Server はキャッシュしている全ての HTTP オブジェクトが新鮮ではないと" +"考えます。つまり、常にキャッシュの中の HTTP オブジェクトをオリジンサーバーへ" +"再検証します。" + +#: ../../admin/http-proxy-caching.en.rst:266 +msgid "" +"Traffic Server considers all HTTP objects in the cache to be fresh: never " +"revalidate HTTP objects in the cache with the origin server." +msgstr "" +"Traffic Server はキャッシュしている全ての HTTP オブジェクトを新鮮であると考" +"えます。つまり、オリジンサーバーへ HTTP オブジェクトを再検証することはありま" +"せん。" + +#: ../../admin/http-proxy-caching.en.rst:268 +msgid "" +"Traffic Server considers all HTTP objects without ``Expires`` or ``Cache-" +"control`` headers to be stale: revalidate all HTTP objects without " +"``Expires`` or ``Cache-Control`` headers." +msgstr "" +"Traffic Server は ``Expires`` や ``Cache-Control`` ヘッダーを持っていない " +"HTTP オブジェクトを新鮮ではないと考えます。つまり、常に ``Expires`` や " +"``Cache-Control`` ヘッダーのない HTTP オブジェクトを再検証します。" + +#: ../../admin/http-proxy-caching.en.rst:272 +msgid "" +"To configure how Traffic Server revalidates objects in the cache, you can " +"set specific revalidation rules in :file:`cache.config`." +msgstr "" +"Traffic Server がキャッシュしているオブジェクトを再検証する方法を設定するに" +"は :file:`cache.config` に特定の再検証のルールを設定してください。" + +#: ../../admin/http-proxy-caching.en.rst:275 +msgid "To configure revalidation options" +msgstr "再検証のオプションを設定するには" + +#: ../../admin/http-proxy-caching.en.rst:277 +#: ../../admin/http-proxy-caching.en.rst:490 +#: ../../admin/http-proxy-caching.en.rst:606 +msgid "Edit the following variable in :file:`records.config`" +msgstr ":file:`records.config` の次の変数を変更してください。" + +#: ../../admin/http-proxy-caching.en.rst:279 +msgid ":ts:cv:`proxy.config.http.cache.when_to_revalidate`" +msgstr ":ts:cv:`proxy.config.http.cache.when_to_revalidate`" + +#: ../../admin/http-proxy-caching.en.rst:285 +msgid "Scheduling Updates to Local Cache Content" +msgstr "ローカルキャッシュコンテンツの計画アップデート" + +#: ../../admin/http-proxy-caching.en.rst:287 +msgid "" +"To further increase performance and to ensure that HTTP objects are fresh " +"in the cache, you can use the **Scheduled Update** option. This configures " +"Traffic Server to load specific objects into the cache at scheduled times. " +"You might find this especially beneficial in a reverse proxy setup, where " +"you can *preload* content you anticipate will be in demand." +msgstr "" +"パフォーマンスをはるかに向上させるため、またキャッシュしている HTTP オブジェ" +"クトが新鮮であることを確実にするために、**計画アップデート** オプションを使" +"うことができます。これは特定のオブジェクトをスケジュールされた時間にキャッ" +"シュに読み込むように Traffic Server を設定します。リバースプロキシーをセット" +"アップしている際に、 負荷が心配されるコンテンツを *事前に読み込む* ことがで" +"きるという点で特に役に立つことに気づくかもしれません。" + +#: ../../admin/http-proxy-caching.en.rst:294 +msgid "" +"To use the Scheduled Update option, you must perform the following tasks." +msgstr "" +"計画的アップデートオプションを使うためには次のタスクを行う必要があります。" + +#: ../../admin/http-proxy-caching.en.rst:297 +msgid "" +"Specify the list of URLs that contain the objects you want to schedule for " +"update," +msgstr "スケジュール通りにアップデートしたいオブジェクトを含む URL のリスト" + +#: ../../admin/http-proxy-caching.en.rst:299 +msgid "the time the update should take place," +msgstr "アップデートが実行されるべき時間" + +#: ../../admin/http-proxy-caching.en.rst:300 +msgid "and the recursion depth for the URL." +msgstr "URL の再帰する深さを指定" + +#: ../../admin/http-proxy-caching.en.rst:301 +msgid "" +"Enable the scheduled update option and configure optional retry settings." +msgstr "計画アップデートオプションの有効化とオプショナルなリトライ設定の指定" + +#: ../../admin/http-proxy-caching.en.rst:304 +msgid "" +"Traffic Server uses the information you specify to determine URLs for which " +"it is responsible. For each URL, Traffic Server derives all recursive URLs " +"(if applicable) and then generates a unique URL list. Using this list, " +"Traffic Server initiates an HTTP ``GET`` for each unaccessed URL. It " +"ensures that it remains within the user-defined limits for HTTP concurrency " +"at any given time. The system logs the completion of all HTTP ``GET`` " +"operations so you can monitor the performance of this feature." +msgstr "" +"Traffic Server は責任を持つ URL を決定するために、指定された情報を使います。" +"各 URL に対して Traffic Server は (適用可能であれば) 全ての再帰的な URL を作" +"成し、ユニークな URL リストを生成します。このリストをもとに、Traffic Server " +"はまだアクセスされていない各 URL に対して HTTP ``GET`` リクエストを開始しま" +"す。このリクエストは常に ユーザーが定義した HTTP の並列度の範囲に収まること" +"が保証されています。システムは全ての HTTP ``GET`` オペレーションの完了を記録" +"します。よって、この機能のパフォーマンスを監視することができます。" + +#: ../../admin/http-proxy-caching.en.rst:313 +msgid "" +"Traffic Server also provides a **Force Immediate Update** option that " +"enables you to update URLs immediately without waiting for the specified " +"update time to occur. You can use this option to test your scheduled update " +"configuration (refer to `Forcing an Immediate Update`_)." +msgstr "" +"Traffic Server は **強制即時アップデート** オプションも提供します。これは " +"URL を指定されたアップデート時間になるまで待つことなく、すぐにアップデートす" +"ることを可能にします。このオプションを計画アップデートの設定をテストするため" +"に使うことができます。( `即時アップデートの強制`_ を参照してください)" + +#: ../../admin/http-proxy-caching.en.rst:319 +msgid "Configuring the Scheduled Update Option" +msgstr "計画アップデートオプションの設定" + +#: ../../admin/http-proxy-caching.en.rst:321 +msgid "To configure the scheduled update option" +msgstr "計画アップデートオプションを設定するためには" + +#: ../../admin/http-proxy-caching.en.rst:323 +msgid "" +"Edit :file:`update.config` to enter a line in the file for each URL you " +"want to update." +msgstr "" +":file:`update.config` にアップデートしたい URL を一行毎に書いてください" + +#: ../../admin/http-proxy-caching.en.rst:325 +#: ../../admin/http-proxy-caching.en.rst:346 +#: ../../admin/http-proxy-caching.en.rst:675 +msgid "Edit the following variables" +msgstr "次の変数を変更してください。" + +#: ../../admin/http-proxy-caching.en.rst:327 +msgid ":ts:cv:`proxy.config.update.enabled`" +msgstr ":ts:cv:`proxy.config.update.enabled`" + +#: ../../admin/http-proxy-caching.en.rst:328 +msgid ":ts:cv:`proxy.config.update.retry_count`" +msgstr ":ts:cv:`proxy.config.update.retry_count`" + +#: ../../admin/http-proxy-caching.en.rst:329 +msgid ":ts:cv:`proxy.config.update.retry_interval`" +msgstr ":ts:cv:`proxy.config.update.retry_interval`" + +#: ../../admin/http-proxy-caching.en.rst:330 +msgid ":ts:cv:`proxy.config.update.concurrent_updates`" +msgstr ":ts:cv:`proxy.config.update.concurrent_updates`" + +#: ../../admin/http-proxy-caching.en.rst:336 +msgid "Forcing an Immediate Update" +msgstr "即時アップデートの強制" + +#: ../../admin/http-proxy-caching.en.rst:338 +msgid "" +"Traffic Server provides a **Force Immediate Update** option that enables " +"you to immediately verify the URLs listed in :file:`update.config`. The " +"Force Immediate Update option disregards the offset hour and interval set " +"in :file:`update.config` and immediately updates the URLs listed." +msgstr "" +"Traffic Server は **強制即時アップデート** オプションを提供しています。これ" +"は :file:`update.config` ファイルにリストされた URL を即時に検証す ることを" +"可能にします。強制即時アップデートオプションは :file:`update.config` ファイ" +"ルに設定されたオフセット時間と間隔を無視し、リストされた URL を即時的にアッ" +"プデートします。" + +#: ../../admin/http-proxy-caching.en.rst:344 +msgid "To configure the Force Immediate Update option" +msgstr "強制即時アップデートオプション設定" + +#: ../../admin/http-proxy-caching.en.rst:348 +msgid ":ts:cv:`proxy.config.update.force`" +msgstr ":ts:cv:`proxy.config.update.force`" + +#: ../../admin/http-proxy-caching.en.rst:349 +msgid "Make sure :ts:cv:`proxy.config.update.enabled` is set to 1." +msgstr "" +":ts:cv:`proxy.config.update.enabled` に 1 が設定されていることを確認してくだ" +"さい。" + +#: ../../admin/http-proxy-caching.en.rst:351 +#: ../../admin/http-proxy-caching.en.rst:382 +#: ../../admin/http-proxy-caching.en.rst:436 +#: ../../admin/http-proxy-caching.en.rst:494 +#: ../../admin/http-proxy-caching.en.rst:533 +#: ../../admin/http-proxy-caching.en.rst:557 +#: ../../admin/http-proxy-caching.en.rst:590 +#: ../../admin/http-proxy-caching.en.rst:610 +#: ../../admin/http-proxy-caching.en.rst:635 +#: ../../admin/http-proxy-caching.en.rst:652 +#: ../../admin/http-proxy-caching.en.rst:682 +#: ../../admin/http-proxy-caching.en.rst:708 +#: ../../admin/http-proxy-caching.en.rst:735 +msgid "" +"Run the command :option:`traffic_line -x` to apply the configuration " +"changes." +msgstr "" +"設定変更を適用するために :option:`traffic_line -x` を実行してください。" + +#: ../../admin/http-proxy-caching.en.rst:356 +msgid "" +"When you enable the Force Immediate Update option, Traffic Server " +"continually updates the URLs specified in :file:`update.config` until you " +"disable the option. To disable the Force Immediate Update option, set :ts:" +"cv:`proxy.config.update.force` to ``0`` (zero)." +msgstr "" +"強制即時アップデートオプションを有効にした場合、Traffic Server はこのオプ" +"ションが無効化されるまで :file:`update.config` ファイルに指定された URL を" +"アップデートし続けます。強制即時アップデートオプションを無効化するために" +"は、 :ts:cv:`proxy.config.update.force` 変数を ``0`` (ゼロ) にしてください。" + +#: ../../admin/http-proxy-caching.en.rst:361 +msgid "Pushing Content into the Cache" +msgstr "コンテンツのキャッシュへのプッシュ" + +#: ../../admin/http-proxy-caching.en.rst:363 +msgid "" +"Traffic Server supports the HTTP ``PUSH`` method of content delivery. Using " +"HTTP ``PUSH``, you can deliver content directly into the cache without " +"client requests." +msgstr "" +"Traffic Server はコンテンツ配信に HTTP ``PUSH`` メソッドをサポートして いま" +"す。HTTP ``PUSH`` を使用すると、クライアントからのリクエスト無しに直接コンテ" +"ンツをキャッシュの中に入れることができます。" + +#: ../../admin/http-proxy-caching.en.rst:368 +msgid "Configuring Traffic Server for PUSH Requests" +msgstr "PUSH リクエスト用の Traffic Server の設定" + +#: ../../admin/http-proxy-caching.en.rst:370 +msgid "" +"Before you can deliver content into your cache using HTTP ``PUSH``, you " +"must configure Traffic Server to accept ``PUSH`` requests." +msgstr "" +"HTTP ``PUSH`` を使用してコンテンツをキャッシュの中に入れる前に、Traffic " +"Server が ``PUSH`` リクエストを受け入れるように設定する必要があります。" + +#: ../../admin/http-proxy-caching.en.rst:373 +msgid "To configure Traffic Server to accept ``PUSH`` requests" +msgstr "Traffic Server が ``PUSH`` リクエストを受け入れるように設定するには" + +#: ../../admin/http-proxy-caching.en.rst:375 +msgid "Edit :file:`ip_allow.config` to allow ``PUSH``." +msgstr ":file:`ip_allow.config` を変更して ``PUSH`` を許可してください。" + +#: ../../admin/http-proxy-caching.en.rst:377 +msgid "" +"Edit the following variable in :file:`records.config`, enable the " +"push_method." +msgstr "" +":file:`records.config` の次の変数を編集して、push_method を有効にしてくださ" +"い。" + +#: ../../admin/http-proxy-caching.en.rst:380 +msgid ":ts:cv:`proxy.config.http.push_method_enabled`" +msgstr ":ts:cv:`proxy.config.http.push_method_enabled`" + +#: ../../admin/http-proxy-caching.en.rst:386 +msgid "Understanding HTTP PUSH" +msgstr "HTTP PUSH の理解" + +#: ../../admin/http-proxy-caching.en.rst:388 +msgid "" +"``PUSH`` uses the HTTP 1.1 message format. The body of a ``PUSH`` request " +"contains the response header and response body that you want to place in " +"the cache. The following is an example of a ``PUSH`` request::" +msgstr "" +"``PUSH`` は HTTP 1.1 メッセージフォーマットを使用します。 ``PUSH`` リクエス" +"トのボディはキャッシュに入れたいレスポンスヘッダーとレスポンスボディを含みま" +"す。下記は ``PUSH`` リクエストの例です。" + +#: ../../admin/http-proxy-caching.en.rst:405 +msgid "" +"Your header must include ``Content-length`` - ``Content-length`` must " +"include both ``header`` and ``body byte count``." +msgstr "" +"ヘッダーは ``Contetnt-length`` を含んでいる必要があります - ``Contetn-" +"length`` は ``header`` と ``body byte count`` の両方を含む必 要があります。" + +#: ../../admin/http-proxy-caching.en.rst:409 +msgid "Tools that will help manage pushing" +msgstr "プッシュを手助けするツール" + +#: ../../admin/http-proxy-caching.en.rst:411 +msgid "" +"There is a perl script for pushing, :program:`tspush`, which can help you " +"understanding how to write scripts for pushing content yourself." +msgstr "" +"プッシュするための perl スクリプトがあります。:program:`tspush` です。これは" +"コンテンツをプッシュするためのスクリプトの書き方を理解することに役立ちます。" + +#: ../../admin/http-proxy-caching.en.rst:416 +msgid "Pinning Content in the Cache" +msgstr "コンテンツのキャッシュへのピン留め" + +#: ../../admin/http-proxy-caching.en.rst:418 +msgid "" +"The **Cache Pinning Option** configures Traffic Server to keep certain HTTP " +"objects in the cache for a specified time. You can use this option to " +"ensure that the most popular objects are in cache when needed and to " +"prevent Traffic Server from deleting important objects. Traffic Server " +"observes ``Cache-Control`` headers and pins an object in the cache only if " +"it is indeed cacheable." +msgstr "" +"**キャッシュのピン留めオプション** は特定の時間の間 HTTP オブジェクトを" +"キャッシュに確実に入れておくように Traffic Server を設定します。最もポピュ" +"ラーなオブジェクトが必要とされるときにキャッシュされていることと、 Traffic " +"Server が重要なオブジェクトを削除することを防ぐことを確実にしたい際にこのオ" +"プションが使えます。Traffic Server は ``Cache-Control`` ヘッダーを監視し、本" +"当にキャッシュ可能な場合にオブジェクトをキャッシュに留めます。" + +#: ../../admin/http-proxy-caching.en.rst:425 +msgid "To set cache pinning rules" +msgstr "キャッシュを留めるルールを設定するためには" + +#: ../../admin/http-proxy-caching.en.rst:427 +msgid "Make sure the following variable in :file:`records.config` is set" +msgstr "" +":file:`records.config` の次の変数がセットされていることを確認してください。" + +#: ../../admin/http-proxy-caching.en.rst:429 +msgid ":ts:cv:`proxy.config.cache.permit.pinning`" +msgstr ":ts:cv:`proxy.config.cache.permit.pinning`" + +#: ../../admin/http-proxy-caching.en.rst:431 +msgid "" +"Add a rule in :file:`cache.config` for each URL you want Traffic Server to " +"pin in the cache. For example::" +msgstr "" +"Traffic Server にキャッシュに留めさせたい URL 毎に :file:`cache.config` に" +"ルールを追加してください。例:" + +#: ../../admin/http-proxy-caching.en.rst:440 +msgid "To Cache or Not to Cache?" +msgstr "キャッシュするかキャッシュしないか?" + +#: ../../admin/http-proxy-caching.en.rst:442 +msgid "" +"When Traffic Server receives a request for a web object that is not in the " +"cache, it retrieves the object from the origin server and serves it to the " +"client. At the same time, Traffic Server checks if the object is cacheable " +"before storing it in its cache to serve future requests." +msgstr "" +"Traffic Server がキャッシュしていないウェブオブジェクトへのリクエストを受け" +"取った際、オリジンサーバーからオブジェクトを回収し、クライアントに配信しま" +"す。その際に、Traffic Server は将来のリクエストに備えてキャッシュに保存する" +"前に、オブジェクトがキャッシュ可能かどうか確認します。" + +#: ../../admin/http-proxy-caching.en.rst:448 +msgid "Caching HTTP Objects" +msgstr "HTTP オブジェクトのキャッシュ" + +#: ../../admin/http-proxy-caching.en.rst:450 +msgid "" +"Traffic Server responds to caching directives from clients and origin " +"servers, as well as directives you specify through configuration options " +"and files." +msgstr "" +"Traffic Server は設定オプションやファイルに指定したディレクティブと同じよう" +"に、クライアントやオリジンサーバーからのキャッシュのディレクティブに反応しま" +"す。" + +#: ../../admin/http-proxy-caching.en.rst:455 +msgid "Client Directives" +msgstr "クライアントディレクティブ" + +#: ../../admin/http-proxy-caching.en.rst:457 +msgid "" +"By default, Traffic Server does *not* cache objects with the following " +"**request headers**:" +msgstr "" +"デフォルトではTraffic Server は次の **リクエストヘッダー** を持つオブジェク" +"トをキャッシュ *しません* 。" + +#: ../../admin/http-proxy-caching.en.rst:460 +msgid "``Authorization``: header" +msgstr "``Authorization``: ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:462 +#: ../../admin/http-proxy-caching.en.rst:503 +msgid "``Cache-Control: no-store`` header" +msgstr "``Cache-Control: no-store`` ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:464 +msgid "``Cache-Control: no-cache`` header" +msgstr "``Cache-Control: no-cache`` ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:466 +msgid "" +"To configure Traffic Server to ignore the ``Cache-Control: no-cache`` " +"header, refer to `Configuring Traffic Server to Ignore Client no-cache " +"Headers`_" +msgstr "" +"``Cache-Control: no-cache`` ヘッダーを無視するように Traffic Server を設定す" +"るには `クライアントの no-cache ヘッダーを無視する Traffic Server の設定`_ " +"を参照してください。" + +#: ../../admin/http-proxy-caching.en.rst:469 +msgid "``Cookie``: header (for text objects)" +msgstr "``Cookie``: ヘッダー (テキストオブジェクト用)" + +#: ../../admin/http-proxy-caching.en.rst:471 +msgid "" +"By default, Traffic Server caches objects served in response to requests " +"that contain cookies (unless the object is text). You can configure Traffic " +"Server to not cache cookied content of any type, cache all cookied content, " +"or cache cookied content that is of image type only. For more information, " +"refer to `Caching Cookied Objects`_." +msgstr "" +"デフォルトでは、クッキーを含むリクエストへ返されるオブジェクト(テキストを除" +"くオブジェクト) を Traffic Server はキャッシュします。Traffic Server を次の" +"用に設定することができます。クッキーを持ったどんなタイプのコンテンツでも" +"キャッシュしない、クッキーを持った全てのコンテンツをキャッシュする、もしくは" +"クッキーを持った画像だけをキャッシュする。より詳しくは `クッキーオブジェクト" +"のキャッシュ`_ を参照してください。" + +#: ../../admin/http-proxy-caching.en.rst:478 +msgid "Configuring Traffic Server to Ignore Client no-cache Headers" +msgstr "クライアントの no-cache ヘッダーを無視する Traffic Server の設定" + +#: ../../admin/http-proxy-caching.en.rst:480 +msgid "" +"By default, Traffic Server strictly observes client ``Cache-Control: no-" +"cache`` directives. If a requested object contains a ``no-cache`` header, " +"then Traffic Server forwards the request to the origin server even if it " +"has a fresh copy in cache. You can configure Traffic Server to ignore " +"client ``no-cache`` directives such that it ignores ``no-cache`` headers " +"from client requests and serves the object from its cache." +msgstr "" +"デフォルトでは Traffic Server はクライアントの ``Cache-Control: no-cache`` " +"ディレクティブを正確に守ります。リクエストされたオブジェクトが ``no-cache`` " +"を含んでいる場合、Traffic Server はキャッシュのコピーが新鮮であったとして" +"も、オリジンサーバーにリクエストを転送します。Traffic Server がクライアント" +"からの ``no-cache`` ディレクティブを無視するように設定することもできます。こ" +"の場合、クライアントからのリクエストの ``no-cache`` ヘッダーを無視して、" +"キャッシュからオブジェクトを配信します。" + +#: ../../admin/http-proxy-caching.en.rst:488 +msgid "To configure Traffic Server to ignore client ``no-cache`` headers" +msgstr "``no-cache`` ヘッダーを無視するように Traffic Server を設定するには" + +#: ../../admin/http-proxy-caching.en.rst:492 +msgid ":ts:cv:`proxy.config.http.cache.ignore_client_no_cache`" +msgstr ":ts:cv:`proxy.config.http.cache.ignore_client_no_cache`" + +#: ../../admin/http-proxy-caching.en.rst:498 +msgid "Origin Server Directives" +msgstr "オリジンサーバーディレクティブ" + +#: ../../admin/http-proxy-caching.en.rst:500 +msgid "" +"By default, Traffic Server does *not* cache objects with the following " +"**response headers**:" +msgstr "" +"デフォルトでは Traffic Server は次の **レスポンスヘッダー** を持つようなオブ" +"ジェクトをキャッシュ *しません*。" + +#: ../../admin/http-proxy-caching.en.rst:504 +msgid "``Cache-Control: private`` header" +msgstr "``Cache-Control: private`` ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:505 +msgid "``WWW-Authenticate``: header" +msgstr "``WWW-Authenticate``: ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:507 +msgid "" +"To configure Traffic Server to ignore ``WWW-Authenticate`` headers, refer " +"to `Configuring Traffic Server to Ignore WWW-Authenticate Headers`_." +msgstr "" +"``WWW-Authenticate`` ヘッダーを無視するように Traffic Server を設定 するに" +"は `WWW-Authenticate ヘッダーを無視する Traffic Server の設定`_ を参照してく" +"ださい。" + +#: ../../admin/http-proxy-caching.en.rst:510 +msgid "``Set-Cookie``: header" +msgstr "``Set-Cookie``: ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:511 +msgid "``Cache-Control: no-cache`` headers" +msgstr "``Cache-Control: no-cache`` ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:513 +msgid "" +"To configure Traffic Server to ignore ``no-cache`` headers, refer to " +"`Configuring Traffic Server to Ignore Server no-cache Headers`_." +msgstr "" +"``no-cache`` ヘッダーを無視するように Traffic Server を設定するには `サー" +"バーの no-cache ヘッダーを無視する Traffic Server の設定`_ を参照してくださ" +"い。" + +#: ../../admin/http-proxy-caching.en.rst:516 +msgid "``Expires``: header with value of 0 (zero) or a past date" +msgstr "値が 0 (ゼロ)もしくは過去の日付の ``Expires`` ヘッダー" + +#: ../../admin/http-proxy-caching.en.rst:519 +msgid "Configuring Traffic Server to Ignore Server no-cache Headers" +msgstr "サーバーの no-cache ヘッダーを無視する Traffic Server の設定" + +#: ../../admin/http-proxy-caching.en.rst:521 +msgid "" +"By default, Traffic Server strictly observes ``Cache-Control: no-cache`` " +"directives. A response from an origin server with a ``no-cache`` header is " +"not stored in the cache and any previous copy of the object in the cache is " +"removed. If you configure Traffic Server to ignore ``no-cache`` headers, " +"then Traffic Server also ignores ``no-store`` headers. The default behavior " +"of observing ``no-cache`` directives is appropriate in most cases." +msgstr "" +"デフォルトでは Traffic Server は ``Cache-Control: no-cache`` ディレクティブ" +"を正確に守ります。``no-cache`` ヘッダーが付いているオリジンサーバーからのレ" +"スポンスはキャッシュに保存されません。また、以前キャッシュされたオブジェクト" +"のコピーは削除されます。 ``no-cache`` ヘッダーを無視するように Traffic " +"Server を設定した場合、Traffic Server は ``no-store`` ヘッダーも無視します。" +"``no-cache`` ディレクティブを守るデフォルトの振る舞いはほとんどの場合に適切" +"です。" + +#: ../../admin/http-proxy-caching.en.rst:529 +msgid "To configure Traffic Server to ignore server ``no-cache`` headers" +msgstr "" +"サーバーの ``no-cache`` ヘッダーを無視するように Traffic Server を設定するに" +"は" + +#: ../../admin/http-proxy-caching.en.rst:531 +msgid "" +"Edit the variable :ts:cv:`proxy.config.http.cache.ignore_server_no_cache`" +msgstr "" +":ts:cv:`proxy.config.http.cache.ignore_server_no_cache` 変数を変更してくださ" +"い。" + +#: ../../admin/http-proxy-caching.en.rst:537 +msgid "Configuring Traffic Server to Ignore WWW-Authenticate Headers" +msgstr "WWW-Authenticate ヘッダーを無視する Traffic Server の設定" + +#: ../../admin/http-proxy-caching.en.rst:539 +msgid "" +"By default, Traffic Server does not cache objects that contain ``WWW-" +"Authenticate`` response headers. The ``WWW-Authenticate`` header contains " +"authentication parameters the client uses when preparing the authentication " +"challenge response to an origin server." +msgstr "" +"デフォルトでは Traffic Server は ``WWW-Authenticate`` レスポンスヘッダーを含" +"むオブジェクトをキャッシュしません。 ``WWW-Authenticate`` ヘッダーはクライア" +"ントがオリジンサーバーへのチャレンジレスポンス認証の際に使う認証パラメーター" +"を含んでいます。" + +#: ../../admin/http-proxy-caching.en.rst:544 +msgid "" +"When you configure Traffic Server to ignore origin server ``WWW-" +"Authenticate`` headers, all objects with ``WWW-Authenticate`` headers are " +"stored in the cache for future requests. However, the default behavior of " +"not caching objects with ``WWW-Authenticate`` headers is appropriate in " +"most cases. Only configure Traffic Server to ignore server ``WWW-" +"Authenticate`` headers if you are knowledgeable about HTTP 1.1." +msgstr "" +"オリジンサーバーの ``WWW-Authenticate`` ヘッダーを無視するように Traffic " +"Server を設定した場合、 ``WWW-Authenticate`` ヘッダーを持つ全てのオブジェク" +"トは次のリクエストの為にキャッシュに保存されます。しかし、 ``WWW-" +"Authenticate`` ヘッダーを持つオブジェクトをキャッシュしないデフォルトの振る" +"舞いは多くの場合に適切です。 ``WWW-Authenticate`` ヘッダーを無視するように " +"Traffic Server を設定するのは HTTP 1.1 に精通してる場合にだけにしてくださ" +"い。" + +#: ../../admin/http-proxy-caching.en.rst:552 +msgid "" +"To configure Traffic Server to ignore server ``WWW-Authenticate`` headers" +msgstr "" +"``WWW-Authenticate`` ヘッダーを無視するように Traffic Server を設定するには" + +#: ../../admin/http-proxy-caching.en.rst:555 +msgid "" +"Edit the variable :ts:cv:`proxy.config.http.cache.ignore_authentication`" +msgstr "" +":ts:cv:`proxy.config.http.cache.ignore_authentication` 変数を変更してくださ" +"い。" + +#: ../../admin/http-proxy-caching.en.rst:561 +msgid "Configuration Directives" +msgstr "設定ディレクティブ" + +#: ../../admin/http-proxy-caching.en.rst:563 +msgid "" +"In addition to client and origin server directives, Traffic Server responds " +"to directives you specify through configuration options and files." +msgstr "" +"クライアントやオリジンサーバーのディレクティブに加えて、Traffic Server は設" +"定オプションやファイルを通じて設定したディレクティブにも反応します。" + +#: ../../admin/http-proxy-caching.en.rst:567 +msgid "You can configure Traffic Server to do the following:" +msgstr "次のように Traffic Server を設定することができます。" + +#: ../../admin/http-proxy-caching.en.rst:569 +msgid "" +"*Not* cache any HTTP objects (refer to `Disabling HTTP Object Caching`_)." +msgstr "" +"どんな HTTP オブジェクトもキャッシュ *しない* ( `HTTP オブジェクトキャッシュ" +"の無効化`_ 参照)" + +#: ../../admin/http-proxy-caching.en.rst:570 +msgid "" +"Cache **dynamic content** - that is, objects with URLs that end in ``.asp`` " +"or contain a question mark (``?``), semicolon (**``;``**), or **``cgi``**. " +"For more information, refer to `Caching Dynamic Content`_." +msgstr "" +"**動的コンテンツ** をキャッシュする - ``.asp`` で終わったり、クエスチョン" +"マーク (``?``)、セミコロン (``;``) や ``cgi`` を含んでいたりする URL のオブ" +"ジェクト。より詳しくは `動的コンテンツのキャッシュ`_ を参照してください。" + +#: ../../admin/http-proxy-caching.en.rst:573 +msgid "" +"Cache objects served in response to the ``Cookie:`` header (refer to " +"`Caching Cookied Objects`_." +msgstr "" +"``Cookie:`` ヘッダーに対して返されるオブジェクトをキャッシュする ( `クッキー" +"オブジェクトのキャッシュ`_ 参照)" + +#: ../../admin/http-proxy-caching.en.rst:575 +msgid "Observe ``never-cache`` rules in the :file:`cache.config` file." +msgstr ":file:`cache.config` ファイルの ``never-cache`` ルールに従う" + +#: ../../admin/http-proxy-caching.en.rst:578 +msgid "Disabling HTTP Object Caching" +msgstr "HTTP オブジェクトキャッシュの無効化" + +#: ../../admin/http-proxy-caching.en.rst:580 +msgid "" +"By default, Traffic Server caches all HTTP objects except those for which " +"you have set ``never-cache`` as :ref:`action rules ` in the :file:`cache.config` file. You can disable HTTP object " +"caching so that all HTTP objects are served directly from the origin server " +"and never cached, as detailed below." +msgstr "" +"デフォルトでは Traffic Server は :file:`cache.config` ファイルに設定した " +"``never-cache`` :ref:`アクションルール ` を除く" +"全ての HTTP オブジェクトをキャッシュします。後述するように　HTTP オブジェク" +"トがオリジンサーバーから直接配信され、決してキャッシュされな いように HTTP " +"オブジェクトのキャッシュを無効化することができます。" + +#: ../../admin/http-proxy-caching.en.rst:586 +msgid "To disable HTTP object caching manually" +msgstr "HTTP オブジェクトを手動で無効化するには" + +#: ../../admin/http-proxy-caching.en.rst:588 +msgid "Set the variable :ts:cv:`proxy.config.http.enabled` to ``0``." +msgstr ":ts:cv:`proxy.config.http.enabled` 変数に ``0`` を設定してください。." + +#: ../../admin/http-proxy-caching.en.rst:594 +msgid "Caching Dynamic Content" +msgstr "動的コンテンツのキャッシュ" + +#: ../../admin/http-proxy-caching.en.rst:596 +msgid "" +"A URL is considered **dynamic** if it ends in **``.asp``** or contains a " +"question mark (``?``), a semicolon (``;``), or ``cgi``. By default, Traffic " +"Server caches dynamic content. You can configure the system to ignore " +"dyanamic looking content, although this is recommended only if the content " +"is *truely* dyanamic, but fails to advertise so with appropriate ``Cache-" +"Control`` headers." +msgstr "" +"``.asp`` で終わったり、クエスチョンマーク (``?``)、セミコロン (``;``) や " +"``cgi`` を含んでいたりする URL は **動的** であると考えられます。デフォルト" +"では Traffic Server は動的コンテンツをキャッシュします。コンテンツが *本当に" +"* 動的である場合にだけ推奨されますが、適切な ``Cache-Control`` ヘッダーに" +"よって伝えることができないとき、動的だと思われるコンテンツを無視するようにシ" +"ステムを設定することができます。" + +#: ../../admin/http-proxy-caching.en.rst:603 +msgid "" +"To configure Traffic Server's cache behaviour in regard to dynamic content" +msgstr "動的コンテンツに配慮した Traffic Server の振る舞いを設定するには" + +#: ../../admin/http-proxy-caching.en.rst:608 +msgid ":ts:cv:`proxy.config.http.cache.cache_urls_that_look_dynamic`" +msgstr ":ts:cv:`proxy.config.http.cache.cache_urls_that_look_dynamic`" + +#: ../../admin/http-proxy-caching.en.rst:614 +msgid "Caching Cookied Objects" +msgstr "クッキーオブジェクトのキャッシュ" + +#: ../../admin/http-proxy-caching.en.rst:618 +msgid "" +"By default, Traffic Server caches objects served in response to requests " +"that contain cookies. This is true for all types of objects except for " +"text. Traffic Server does not cache cookied text content because object " +"headers are stored along with the object, and personalized cookie header " +"values could be saved with the object. With non-text objects, it is " +"unlikely that personalized headers are delivered or used." +msgstr "" +"デフォルトではクッキーを含むリクエストに対するレスポンスとして配信されたオブ" +"ジェクトを Traffic Server はキャッシュします。これはテキストを除いた全てのタ" +"イプのオブジェクトについても同じです。Traffic Server はクッキーをもつテキス" +"トコンテンツをキャッシュしません。それはオブジェクトのヘッダーはオブジェクト" +"共に保存され、個人的なクッキーヘッダーの値もオブジェクトと共に保存されるため" +"です。テキストではないオブジェクトの場合、個人的なヘッダーは配信されたり使わ" +"れたりしません。" + +#: ../../admin/http-proxy-caching.en.rst:625 +msgid "You can reconfigure Traffic Server to:" +msgstr "次のように Traffic Server を設定し直すことができます。" + +#: ../../admin/http-proxy-caching.en.rst:627 +msgid "*Not* cache cookied content of any type." +msgstr "クッキーを含む全てのコンテンツをキャッシュ *しない*" + +#: ../../admin/http-proxy-caching.en.rst:628 +msgid "Cache cookied content that is of image type only." +msgstr "クッキーを含む画像のみキャッシュする" + +#: ../../admin/http-proxy-caching.en.rst:629 +msgid "Cache all cookied content regardless of type." +msgstr "タイプを考慮せずクッキーを含む全てのコンテンツをキャッシュする" + +#: ../../admin/http-proxy-caching.en.rst:631 +msgid "To configure how Traffic Server caches cookied content" +msgstr "" +"クッキーを含むコンテンツをどのようにキャッシュするか Traffic Server を設定す" +"るには" + +#: ../../admin/http-proxy-caching.en.rst:633 +msgid "" +"Edit the variable :ts:cv:`proxy.config.http.cache." +"cache_responses_to_cookies`" +msgstr "" +":ts:cv:`proxy.config.http.cache.cache_responses_to_cookies` 変数を変更してく" +"ださい。" + +#: ../../admin/http-proxy-caching.en.rst:639 +msgid "Forcing Object Caching" +msgstr "オブジェクトの強制キャッシュ" + +#: ../../admin/http-proxy-caching.en.rst:641 +msgid "" +"You can force Traffic Server to cache specific URLs (including dynamic " +"URLs) for a specified duration, regardless of ``Cache-Control`` response " +"headers." +msgstr "" +"``Cache-Control`` レスポンスヘッダーを無視して、特定の期間に特定の URL (動" +"的 URL も含む) をキャッシュすることを Traffic Server に強制することができま" +"す。" + +#: ../../admin/http-proxy-caching.en.rst:645 +msgid "To force document caching" +msgstr "ドキュメントを強制的にキャッシュするには" + +#: ../../admin/http-proxy-caching.en.rst:647 +msgid "" +"Add a rule for each URL you want Traffic Server to pin to the cache :file:" +"`cache.config`::" +msgstr "" +"Traffic Server にキャッシュに留めさせたい URL 毎に :file:`cache.config` に" +"ルールを追加してください。" + +#: ../../admin/http-proxy-caching.en.rst:656 +msgid "Caching HTTP Alternates" +msgstr "HTTP オブジェクトの代替のキャッシュ" + +#: ../../admin/http-proxy-caching.en.rst:658 +msgid "" +"Some origin servers answer requests to the same URL with a variety of " +"objects. The content of these objects can vary widely, according to whether " +"a server delivers content for different languages, targets different " +"browsers with different presentation styles, or provides different document " +"formats (HTML, XML). Different versions of the same object are termed " +"**alternates** and are cached by Traffic Server based on ``Vary`` response " +"headers. You can specify additional request and response headers for " +"specific ``Content-Type``\\s that Traffic Server will identify as " +"alternates for caching. You can also limit the number of alternate versions " +"of an object allowed in the cache." +msgstr "" +"いくつかの同一の URL へ複数のオブジェクトを回答するオリジンサーバーもありま" +"す。これらのオブジェクトのコンテンツはサーバーが異なる言語ごとにコンテンツを" +"配信したり、異なるブラウザ毎にプレゼンテーションスタイルを用意していたり、異" +"なるドキュメントフォーマット(HTML, XML) を提供しているか等により、多岐にわた" +"ります。同一オブジェクトの異なるバージョンは **代替** と呼ばれ、``Vary`` レ" +"スポンスヘッダーに基づいて Traffic Server にキャッシュされます。Traffic " +"Server がキャッシュする代替を判別する特別な ``Content-Type`` をリクエストや" +"レスポンスヘッダに追加することができます。キャッシュする代替バージョンの数を" +"制限することもできます。" + +#: ../../admin/http-proxy-caching.en.rst:670 +msgid "Configuring How Traffic Server Caches Alternates" +msgstr "Traffic Server がキャッシュする代替の設定" + +#: ../../admin/http-proxy-caching.en.rst:672 +msgid "" +"To configure how Traffic Server caches alternates, follow the steps below" +msgstr "" +"Traffic Server が代替をキャッシュするように設定するには、次のステップに従っ" +"てください。" + +#: ../../admin/http-proxy-caching.en.rst:677 +msgid ":ts:cv:`proxy.config.http.cache.enable_default_vary_headers`" +msgstr ":ts:cv:`proxy.config.http.cache.enable_default_vary_headers`" + +#: ../../admin/http-proxy-caching.en.rst:678 +msgid ":ts:cv:`proxy.config.http.cache.vary_default_text`" +msgstr ":ts:cv:`proxy.config.http.cache.vary_default_text`" + +#: ../../admin/http-proxy-caching.en.rst:679 +msgid ":ts:cv:`proxy.config.http.cache.vary_default_images`" +msgstr ":ts:cv:`proxy.config.http.cache.vary_default_images`" + +#: ../../admin/http-proxy-caching.en.rst:680 +msgid ":ts:cv:`proxy.config.http.cache.vary_default_other`" +msgstr ":ts:cv:`proxy.config.http.cache.vary_default_other`" + +#: ../../admin/http-proxy-caching.en.rst:687 +msgid "" +"If you specify ``Cookie`` as the header field on which to vary in the above " +"variables, make sure that the variable :ts:cv:`proxy.config.http.cache." +"cache_responses_to_cookies` is set appropriately." +msgstr "" +"上の変数に ``Cookie`` を切り替えるためのヘッダーフィールドとして指定した場" +"合、 :ts:cv:`proxy.config.http.cache.cache_responses_to_cookies` が適切に" +"セットされていることを確認して下さい。" + +#: ../../admin/http-proxy-caching.en.rst:693 +msgid "Limiting the Number of Alternates for an Object" +msgstr "オブジェクトの代替数の制限" + +#: ../../admin/http-proxy-caching.en.rst:695 +msgid "" +"You can limit the number of alternates Traffic Server can cache per object " +"(the default is 3)." +msgstr "" +"Traffic Server がオブジェクト毎にキャッシュする代替数を制限することができま" +"す。(デフォルトは 3 です)" + +#: ../../admin/http-proxy-caching.en.rst:700 +msgid "" +"Large numbers of alternates can affect Traffic Server cache performance " +"because all alternates have the same URL. Although Traffic Server can look " +"up the URL in the index very quickly, it must scan sequentially through " +"available alternates in the object store." +msgstr "" +"全ての代替は同一の URL を持つため、代替の数が多いと Traffic Server のキャッ" +"シュパフォーマンスに影響を与えるかもしれません。Traffic Server はインデック" +"ス中の URL をとても高速に検索しますが、キャッシュストアの中に使用可能な代替" +"があるかはシーケンシャルにスキャンしなければなりません。" + +#: ../../admin/http-proxy-caching.en.rst:705 +msgid "To limit the number of alternates" +msgstr "代替の数を制限するには" + +#: ../../admin/http-proxy-caching.en.rst:707 +msgid "Edit the variable :ts:cv:`proxy.config.cache.limits.http.max_alts`" +msgstr "" +":ts:cv:`proxy.config.cache.limits.http.max_alts` 変数を変更してください。" + +#: ../../admin/http-proxy-caching.en.rst:714 +msgid "Using Congestion Control" +msgstr "輻輳制御" + +#: ../../admin/http-proxy-caching.en.rst:716 +msgid "" +"The **Congestion Control** option enables you to configure Traffic Server " +"to stop forwarding HTTP requests to origin servers when they become " +"congested. Traffic Server then sends the client a message to retry the " +"congested origin server later." +msgstr "" +"**輻輳制御** オプションはオリジンサーバーが混雑しているときに Traffic " +"Server が HTTP リクエストを転送することを止めることを可能にします。Traffic " +"Server はその後、混雑してるオリジンサーバーに後でリトライするメッセージをク" +"ライアントに送ります。" + +#: ../../admin/http-proxy-caching.en.rst:721 +msgid "" +"To use the **Congestion Control** option, you must perform the following " +"tasks:" +msgstr "**輻輳制御** オプションを使うには、次のタスクを実行してください。" + +#: ../../admin/http-proxy-caching.en.rst:724 +msgid "" +"Set the variable :ts:cv:`proxy.config.http.congestion_control.enabled` to " +"``1``" +msgstr "" +":ts:cv:`proxy.config.http.congestion_control.enabled` 変数を ``1`` にセット" +"して下さい。" + +#: ../../admin/http-proxy-caching.en.rst:726 +msgid "Create rules in the :file:`congestion.config` file to specify:" +msgstr "" +"ルールを作成して :file:`congestion.config` ファイルに次のように記述してくだ" +"さい。" + +#: ../../admin/http-proxy-caching.en.rst:727 +msgid "which origin servers Traffic Server tracks for congestion" +msgstr "混雑しているか Traffic Server が追跡するオリジンサーバー" + +#: ../../admin/http-proxy-caching.en.rst:728 +msgid "" +"the timeouts Traffic Server uses, depending on whether a server is congested" +msgstr "" +"サーバーが混雑していると判定するために Traffic Sever が使用するタイムアウト" +"値" + +#: ../../admin/http-proxy-caching.en.rst:730 +msgid "" +"the page Traffic Server sends to the client when a server becomes congested" +msgstr "サーバー混雑時に Traffic Server がクライアントに送るページ" + +#: ../../admin/http-proxy-caching.en.rst:732 +msgid "" +"if Traffic Server tracks the origin servers per IP address or per hostname" +msgstr "" +"Traffic Server が IP アドレス毎に追跡するか、ホストネーム毎に追跡するかどう" +"か" + +#: ../../admin/http-proxy-caching.en.rst:741 +msgid "Using Transaction Buffering Control" +msgstr "トランザクションバッファリング制御" + +#: ../../admin/http-proxy-caching.en.rst:743 +msgid "" +"By default I/O operations are run at full speed, as fast as either Traffic " +"Server, the network, or the cache can go. This can be problematic for large " +"objects if the client side connection is significantly slower. In such " +"cases the content will be buffered in ram while waiting to be sent to the " +"client. This could potentially also happen for ``POST`` requests if the " +"client connection is fast and the origin server connection slow. If very " +"large objects are being used this can cause the memory usage of Traffic " +"Server to become `very large `_." +msgstr "" +"デフォルトでは I/O オペレーションは Traffic Server やネットワークやキャッ" +"シュが実行できる限り速くフルスピードで実行されます。これはクライアント側のコ" +"ネクションが遅い場合に、大きなオブジェクトにとって問題になる可能性がありま" +"す。このような場合、クライアントに送られるのを待っている間、コンテンツはメモ" +"リにバッファーされます。これはクライアントのコネクションが早く、オリジンサー" +"バーのコネクションが遅い場合に ``POST`` リクエストでも発生し得ます。とても大" +"きなオブジェクトが使われているとこれは Traffic Server のメモリ使用量がとても" +"大きくなる原因になり得ます。 `very large `_" + +#: ../../admin/http-proxy-caching.en.rst:750 +msgid "" +"This problem can be ameloriated by controlling the amount of buffer space " +"used by a transaction. A high water and low water mark are set in terms of " +"bytes used by the transaction. If the buffer space in use exceeds the high " +"water mark, the connection is throttled to prevent additional external data " +"from arriving. Internal operations continue to proceed at full speed until " +"the buffer space in use drops below the low water mark and external data I/" +"O is re-enabled." +msgstr "" +"この問題はトランザクションが使うバッファースペースの量をコントロールすること" +"で改善されるかもしれません。high water と low water マークはトランザクション" +"で使用されるバイトの幅をセットします。バッファースペースが high water マーク" +"を越えた場合、コネクションは追加のデータがやってくることを止める為に減速しま" +"す。使われているバッファースペースが low water マークを下回り、外部のデータ " +"I/O が再開されるまで内側のオペレーションはフルスピードで進み続けます。" + +#: ../../admin/http-proxy-caching.en.rst:755 +msgid "" +"Although this is intended primarily to limit the memory usage of Traffic " +"Server it can also serve as a crude rate limiter by setting a buffer limit " +"and then throttling the client side connection either externally or via a " +"transform. This will cause the connection to the origin server to be " +"limited to roughly the client side connection speed." +msgstr "" +"主に Traffic Server のメモリ使用量を制限することを意図していますが、これはま" +"た大雑把なレートリミッターも提供します。これはバッファーリミットの設定と、外" +"部やトランスフォームの影響により、クライアント側のコネクションを減速させるこ" +"とによります。これはオリジンサーバーへのコネクションがクライアント側のコネク" +"ションスピードにより大まかに制限されることをもたします。" + +#: ../../admin/http-proxy-caching.en.rst:759 +msgid "" +"Traffic Server does network I/O in large chunks (32K or so) and therefore " +"the granularity of transaction buffering control is limited to a similar " +"precision." +msgstr "" +"Traffic Server はネットワーク I/O をラージチャンク(32K など) で行います。" +"よって、トランザクションバッファリングコントロールの粒度は同じような値に制限" +"されています。" + +#: ../../admin/http-proxy-caching.en.rst:762 +msgid "" +"The buffer size calculations include all elements in the transaction, " +"including any buffers associated with :ref:`transform plugins `." +msgstr "" +"バッファーサイズの計算はトランザクションの全ての要素を含んでいます。これは :" +"ref:`transform plugins ` に紐づけられているどんなバッ" +"ファーも含みます。" + +#: ../../admin/http-proxy-caching.en.rst:764 +msgid "" +"Transaction buffering control can be enabled globally by using " +"configuration variables or by :c:func:`TSHttpTxnConfigIntSet` in a plugin." +msgstr "" +"トランザクションバッファーコントロールは設定変数を使ってグローバルに有効化す" +"ることもできます。また :c:func:`TSHttpTxnConfigIntSet` を使用してプラグイン" +"の中で有効化することもできます。" + +#: ../../admin/http-proxy-caching.en.rst:767 +msgid "Value" +msgstr "値" + +#: ../../admin/http-proxy-caching.en.rst:767 +msgid "Variable" +msgstr "変数" + +#: ../../admin/http-proxy-caching.en.rst:767 +msgid "`TSHttpTxnConfigIntSet` key" +msgstr "`TSHttpTxnConfigIntSet` キー" + +#: ../../admin/http-proxy-caching.en.rst:769 +msgid "Enable buffering" +msgstr "バッファーの有効化" + +#: ../../admin/http-proxy-caching.en.rst:769 +msgid ":ts:cv:`proxy.config.http.flow_control.enabled`" +msgstr ":ts:cv:`proxy.config.http.flow_control.enabled`" + +#: ../../admin/http-proxy-caching.en.rst:769 +msgid "`TS_CONFIG_HTTP_FLOW_CONTROL_ENABLED`" +msgstr "`TS_CONFIG_HTTP_FLOW_CONTROL_ENABLED`" + +#: ../../admin/http-proxy-caching.en.rst:770 +msgid "Set high water" +msgstr "high water の設定" + +#: ../../admin/http-proxy-caching.en.rst:770 +msgid ":ts:cv:`proxy.config.http.flow_control.high_water`" +msgstr ":ts:cv:`proxy.config.http.flow_control.high_water`" + +#: ../../admin/http-proxy-caching.en.rst:770 +msgid "`TS_CONFIG_HTTP_FLOW_CONTROL_HIGH_WATER`" +msgstr "`TS_CONFIG_HTTP_FLOW_CONTROL_HIGH_WATER`" + +#: ../../admin/http-proxy-caching.en.rst:771 +msgid "Set low water" +msgstr "low water の設定" + +#: ../../admin/http-proxy-caching.en.rst:771 +msgid ":ts:cv:`proxy.config.http.flow_control.low_water`" +msgstr ":ts:cv:`proxy.config.http.flow_control.low_water`" + +#: ../../admin/http-proxy-caching.en.rst:771 +msgid "`TS_CONFIG_HTTP_FLOW_CONTROL_LOW_WATER`" +msgstr "`TS_CONFIG_HTTP_FLOW_CONTROL_LOW_WATER`" + +#: ../../admin/http-proxy-caching.en.rst:774 +msgid "" +"Be careful to always have the low water mark equal or less than the high " +"water mark. If you set only one, the other will be set to the same value." +msgstr "" +"low water マークは high water マークと常に同じか少ないことに注意してくださ" +"い。一方だけを設定すると、もう一方は同じ値に設定されます。" + +#: ../../admin/http-proxy-caching.en.rst:777 +msgid "" +"If using c:func:`TSHttpTxnConfigIntSet`, it must be called no later than " +"`TS_HTTP_READ_RESPONSE_HDR_HOOK`." +msgstr "" +"c:func:`TSHttpTxnConfigIntSet` を使う場合、`TS_HTTP_READ_RESPONSE_HDR_HOOK` " +"のすぐ後ろで呼ばれなければなりません。" + +#: ../../admin/http-proxy-caching.en.rst:782 +msgid "Reducing Origin Server Requests (Avoiding the Thundering Herd)" +msgstr "オリジンサーバーへのリクエストの削減(Thundering Herd 問題を避ける)" + +#: ../../admin/http-proxy-caching.en.rst:784 +msgid "" +"When an object can not be served from cache, the request will be proxied to " +"the origin server. For a popular object, this can result in many near " +"simultaneous requests to the origin server, potentially overwhelming it or " +"associated resources. There are several features in Traffic Server that can " +"be used to avoid this scenario." +msgstr "" +"オブジェクトがキャッシュから配信されない場合、リクエストはオリジンサーバーに" +"プロキシーされます。ポピュラーなオブジェクトにとって、これはオリジンサーバー" +"へ多くの同じ様なリクエストを送り、可能性としては計り知れない程の関連したリ" +"ソースを使うかもしれません。Traffic Server にはこのシナリオを避けられるいく" +"つかの機能があります。" + +#: ../../admin/http-proxy-caching.en.rst:789 +msgid "Read While Writer" +msgstr "Read While Writer" + +#: ../../admin/http-proxy-caching.en.rst:790 +msgid "" +"When Traffic Server goes to fetch something from origin, and upon receiving " +"the response, any number of clients can be allowed to start serving the " +"partially filled cache object once background_fill_completed_threshold % of " +"the object has been received. The difference is that Squid allows this as " +"soon as it goes to origin, whereas ATS can not do it until we get the " +"complete response header. The reason for this is that we make no " +"distinction between cache refresh, and cold cache, so we have no way to " +"know if a response is going to be cacheable, and therefore allow read-while-" +"writer functionality." +msgstr "" +"Traffic Server がオリジンからオブジェクトをフェッチしに行くとき、そしてレス" +"ポンスを受け取るとき、受け取ったオブジェクトの " +"background_fill_completed_threshold % が満たされた部分的キャッシュオブジェク" +"トを配信することがどんな数のクライアントにも許されています。違いは Squid は" +"オリジンに行ったすぐ後で許可していますが、ATS は完全なレスポンスヘッダーを受" +"け取るまでできないことです。この理由はキャッシュリフレッシュとコールドキャッ" +"シュの間で差異を作りたくないからです。レスポンスがキャッシュ可能なものか知る" +"方法がないので、read-while-writer 機能を許可しています。" + +#: ../../admin/http-proxy-caching.en.rst:792 +msgid "The configurations necessary to enable this in ATS are:" +msgstr "ATS でこれを有効化する為に必要な設定は" + +#: ../../admin/http-proxy-caching.en.rst:794 +msgid "CONFIG :ts:cv:`proxy.config.cache.enable_read_while_writer` ``INT 1``" +msgstr "CONFIG :ts:cv:`proxy.config.cache.enable_read_while_writer` ``INT 1``" + +#: ../../admin/http-proxy-caching.en.rst:795 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.background_fill_active_timeout` ``INT 0``" +msgstr "" +"CONFIG :ts:cv:`proxy.config.http.background_fill_active_timeout` ``INT 0``" + +#: ../../admin/http-proxy-caching.en.rst:796 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.background_fill_completed_threshold` " +"``FLOAT 0.000000``" +msgstr "" +"CONFIG :ts:cv:`proxy.config.http.background_fill_completed_threshold` " +"``FLOAT 0.000000``" + +#: ../../admin/http-proxy-caching.en.rst:797 +msgid "CONFIG :ts:cv:`proxy.config.cache.max_doc_size` ``INT 0``" +msgstr "CONFIG :ts:cv:`proxy.config.cache.max_doc_size` ``INT 0``" + +#: ../../admin/http-proxy-caching.en.rst:799 +msgid "All four configurations are required, for the following reasons:" +msgstr "次の理由により、４つ全ての設定が必要です。" + +#: ../../admin/http-proxy-caching.en.rst:801 +msgid "enable_read_while_writer turns the feature on. It's off (0) by default" +msgstr "" +"enable_read_while_writer は機能を on にします。デフォルトでは off (0) です。" + +#: ../../admin/http-proxy-caching.en.rst:802 +msgid "" +"The background fill feature should be allowed to kick in for every possible " +"request. This is necessary, in case the writer (\"first client session\") " +"goes away, someone needs to take over the session. Hence, you should set " +"the background fill timeouts and threshold to zero; this assures they never " +"times out and always is allowed to kick in." +msgstr "" +"バックグラウンドフィル機能は全てのあり得るリクエストでキックされることが許可" +"されているべきです。これは重要で、writer (\"最初のクライアントセッション\") " +"が出て行った場合、誰かがセッションを引継ぐ必要があります。したがって、バック" +"グラウンドフィルタイムアウトを設定し、境界点をゼロにするべきです。これは彼ら" +"を安心させます。タイムアウトせずに、キックインすることを常に許可されていま" +"す。" + +#: ../../admin/http-proxy-caching.en.rst:803 +msgid "" +"The proxy.config.cache.max_doc_size should be unlimited (set to 0), since " +"the object size may be unknown, and going over this limit would cause a " +"disconnect on the objects being served." +msgstr "" +"proxy.config.cache.max_doc_size は無制限(0)に設定されているべきです。オブ" +"ジェクトサイズは分からないので。この制限は配信されているオブジェクトのコネク" +"ションの切断の原因になるかもしれません。" + +#: ../../admin/http-proxy-caching.en.rst:805 +msgid "" +"Once all this enabled, you have something that is very close, but not quite " +"the same, as Squid's Collapsed Forwarding." +msgstr "" +"一度これら全てが有効化されると、Squid の Collapesd Forwarding にとても近いが" +"異なるものができます。" + +#: ../../admin/http-proxy-caching.en.rst:812 +msgid "Fuzzy Revalidation" +msgstr "Fuzzy Revalidation" + +#: ../../admin/http-proxy-caching.en.rst:813 +msgid "" +"Traffic Server can be set to attempt to revalidate an object before it " +"becomes stale in cache. :file:`records.config` contains the settings:" +msgstr "" +"Traffic Server はキャッシュが新鮮でなくなる前に、オブジェクトの再検証を試み" +"るように設定することもできます。:file:`records.config` に次の設定がありま" +"す。" + +#: ../../admin/http-proxy-caching.en.rst:815 +msgid "CONFIG :ts:cv:`proxy.config.http.cache.fuzz.time` ``INT 240``" +msgstr "CONFIG :ts:cv:`proxy.config.http.cache.fuzz.time` ``INT 240``" + +#: ../../admin/http-proxy-caching.en.rst:816 +msgid "CONFIG :ts:cv:`proxy.config.http.cache.fuzz.min_time` ``INT 0``" +msgstr "CONFIG :ts:cv:`proxy.config.http.cache.fuzz.min_time` ``INT 0``" + +#: ../../admin/http-proxy-caching.en.rst:817 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.cache.fuzz.probability` ``FLOAT 0.005``" +msgstr "" +"CONFIG :ts:cv:`proxy.config.http.cache.fuzz.probability` ``FLOAT 0.005``" + +#: ../../admin/http-proxy-caching.en.rst:819 +msgid "" +"For every request for an object that occurs \"fuzz.time\" before (in the " +"example above, 240 seconds) the object is set to become stale, there is a " +"small chance (fuzz.probability == 0.5%) that the request will trigger a " +"revalidation request to the origin. For objects getting a few requests per " +"second, this would likely not trigger, but then this feature is not " +"necessary anyways since odds are only 1 or a small number of connections " +"would hit origin upon objects going stale. The defaults are a good " +"compromise, for objects getting roughly 4 requests / second or more, it's " +"virtually guaranteed to trigger a revalidate event within the 240s. These " +"configs are also overridable per remap rule or via a plugin, so can be " +"adjusted per request if necessary." +msgstr "" +"新鮮でないとセットされる前に \"fuzz.time\" (上の例では 240 秒) を発生させる" +"すべてのオブジェクトへのリクエストには、オリジンへの再検証リクエストを引き起" +"こすわずかな可能性 ( fuzz.probability == 0.5% ) があります。秒間 2,3 リクエ" +"スト数しかないオブジェクトでは、これはまず引き起こされません。また、オッズが" +"たったの 1 やオブジェクトが新鮮ではなくなり、コネクションがオリジンをヒット" +"する数が少ないとき、この機能は必要ではありません。デフォルト値はいい妥協点で" +"あり、おおよそ秒間 4 リクエスト以上のオブジェクトにとって、240 秒以内に再検" +"証が引き起こされることが実質的に保証されます。これらの設定は remap ルール毎" +"やプラグインによって上書きすることもできるので、必要であればリクエスト毎に調" +"整することもできます。" + +#: ../../admin/http-proxy-caching.en.rst:822 +msgid "" +"Note that if the revalidation occurs, the requested object is no longer " +"available to be served from cache. Subsequent requests for that object " +"will be proxied to the origin." +msgstr "" +"再検証が起きた場合、リクエストされたオブジェクトはもはやキャッシュから配信す" +"ることはできないことに注意してください。続いて起きるオブジェクトへのリクエス" +"トはオリジンサーバーにプロキシーされます。" + +#: ../../admin/http-proxy-caching.en.rst:825 +msgid "" +"Finally, the fuzz.min_time is there to be able to handle requests with a " +"TTL less than fuzz.time – it allows for different times to evaluate the " +"probability of revalidation for small TTLs and big TTLs. Objects with small " +"TTLs will start \"rolling the revalidation dice\" near the fuzz.min_time, " +"while objects with large TTLs would start at fuzz.time. A logarithmic like " +"function between determines the revalidation evaluation start time (which " +"will be between fuzz.min_time and fuzz.time). As the object gets closer to " +"expiring, the window start becomes more likely. By default this setting is " +"not enabled, but should be enabled anytime you have objects with small " +"TTLs. Note that this option predates overridable configurations, so you can " +"achieve something similar with a plugin or remap.config conf_remap.so " +"configs." +msgstr "" +"最後に fuzz.min_time は fuzz.time より短い TTL のリクエストを制御することを" +"可能にするためにあります - それは小さい TTL と大きい TTL で再検証の確率を評" +"価する時間が異なることを許容します。TTL の小さなオブジェクトは fuzz." +"min_time 付近で \"再検証のサイコロを転がす\" ことを始めます。一方、大きな " +"TTL のオブジェクトは fuzz.time から始めます。対数のような関数が再検証査定を" +"始める時間を決定します。(その値は fuzz.min_time と fuzz.time の間でしょう) " +"期限切れに近いオブジェクトでは、期間の始まりはより可能性が高くなります。デ" +"フォルトではこの設定は有効化されていません。しかし、TTL の小さなオブジェクト" +"がある場合、いつでも有効化するべきです。このオプションは設定を上書きする前に" +"起きることに注意してください。よって、プラグインや remap.config conf_remap." +"so configs のようなものを作ることができます。" + +#: ../../admin/http-proxy-caching.en.rst:827 +msgid "" +"These configurations are similar to Squid's refresh_stale_hit configuration " +"option." +msgstr "" +"これらの設定は Squid の refresh_stale_hit 設定オプションに似ています。" + +#: ../../admin/http-proxy-caching.en.rst:831 +msgid "Open Read Retry Timeout" +msgstr "Open Read Retry Timeout" + +#: ../../admin/http-proxy-caching.en.rst:833 +msgid "" +"The open read retry configurations attempt to reduce the number of " +"concurrent requests to the origin for a given object. While an object is " +"being fetched from the origin server, subsequent requests would wait " +"open_read_retry_time milliseconds before checking if the object can be " +"served from cache. If the object is still being fetched, the subsequent " +"requests will retry max_open_read_retries times. Thus, subsequent requests " +"may wait a total of (max_open_read_retries x open_read_retry_time) " +"milliseconds before establishing an origin connection of its own. For " +"instance, if they are set to 5 and 10 respectively, connections will wait " +"up to 50ms for a response to come back from origin from a previous request, " +"until this request is allowed through." +msgstr "" +"オープンリードリトライ設定は与えられたオブジェクトに対してオリジンサーバーへ" +"の並列リクエストの数を減らすことを試みています。あるオブジェクトがオリジン" +"サーバーからフェッチされている間、次のリクエストはオブジェクトがキャッシュか" +"ら配信できるかどうかを確認する前に open_read_retry_time ミリ秒待ちます。オブ" +"ジェクトが依然としてフェッチされている場合、次のリクエストは " +"max_open_read_retries 回リトライします。すると、次のリクエストはオリジンサー" +"バーへのコネクションを自分自身で確立する前に合計で (max_open_read_retries x " +"open_read_retry_time) ミリ秒待ちます。例えばそれぞれ 5 や 10 にセットされた" +"場合、このリクエストが許可されるまでコネクションは前回のリクエストがオリジン" +"からレスポンスが帰ってくる間 50ms 待ちます。" + +#: ../../admin/http-proxy-caching.en.rst:835 +msgid "" +"These settings are inappropriate when objects are uncacheable. In those " +"cases, requests for an object effectively become serialized. The subsequent " +"requests would await at least open_read_retry_time milliseconds before " +"being proxies to the origin." +msgstr "" +"これらの設定はオブジェクトがキャッシュ不可能な場合、適切ではありません。これ" +"らの場合、オブジェクトへのリクエストは実際には直列になります。次のリクエスト" +"はオリジンにプロキシーされる前に少なくとも open_read_retry_time ミリ秒待たさ" +"れるでしょう。" + +#: ../../admin/http-proxy-caching.en.rst:837 +msgid "" +"Similarly, this setting should be used in conjunction with Read While " +"Writer for big (those that take longer than (max_open_read_retries x " +"open_read_retry_time) milliseconds to transfer) cacheable objects. Without " +"the read-while-writer settings enabled, while the initial fetch is ongoing, " +"not only would subsequent requests be delayed by the maximum time, but " +"also, those requests would result in another request to the origin server." +msgstr "" +"同様にこの設定は大きな (転送に (max_open_read_retries x " +"open_read_retry_time) ミリ秒以上かかる) キャッシュ可能なオブジェクトの Read " +"While Writer の続発の中では使われるべきです。 read-while-writer 設定を有効化" +"しないと、初回のフェッチが行われている間、次のリクエストが最大限遅れるだけで" +"はなく、結果としてオリジンサーバーへの他のリクエストを発生させます。" + +#: ../../admin/http-proxy-caching.en.rst:839 +msgid "" +"Since ATS now supports setting these settings per-request or remap rule, " +"you can configure this to be suitable for your setup much more easily." +msgstr "" +"ATS はリクエスト毎や remap ルールに設定することをサポートしているので、これ" +"はより簡単に適切に設定することができます。" + +#: ../../admin/http-proxy-caching.en.rst:841 +msgid "The configurations are (with defaults):" +msgstr "設定とそのデフォルト値は" + +#: ../../admin/http-proxy-caching.en.rst:843 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.cache.max_open_read_retries` ``INT -1``" +msgstr "" +"CONFIG :ts:cv:`proxy.config.http.cache.max_open_read_retries` ``INT -1``" + +#: ../../admin/http-proxy-caching.en.rst:844 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.cache.open_read_retry_time` ``INT 10``" +msgstr "" +"CONFIG :ts:cv:`proxy.config.http.cache.open_read_retry_time` ``INT 10``" + +#: ../../admin/http-proxy-caching.en.rst:846 +msgid "" +"The default means that the feature is disabled, and every connection is " +"allowed to go to origin instantly. When enabled, you will try " +"max_open_read_retries times, each with a open_read_retry_time timeout." +msgstr "" +"デフォルトはこの機能が無効化されていて、全てのコネクションはオリジンにすぐに" +"行くことを許可されていることを意味します。有効化した場合、" +"open_read_retry_time タイムアウト毎に max_open_read_retries 回試すでしょう。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/index.en.po b/doc/locale/ja/LC_MESSAGES/admin/index.en.po new file mode 100644 index 00000000000..d4c5aa59af1 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/index.en.po @@ -0,0 +1,628 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: 2013-11-23 00:20+0900\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/index.en.rst:4 +msgid "Administrators' Guide" +msgstr "管理者ガイド" + +#: ../../admin/index.en.rst:24 +msgid "" +"Apache Traffic Server™ speeds Internet access, enhances website " +"performance, and delivers unprecedented web hosting capabilities." +msgstr "" +"Apache Traffic Server™ はインターネットアクセスを加速させ、ウェブサイトのパ" +"フォーマンスを高め、かつて無いウェブホスティング性能を提供します。" + +#: ../../admin/index.en.rst:27 +msgid "This chapter discusses how:" +msgstr "この章は次のようなトピックについて書いてあります。" + +#: ../../admin/index.en.rst:29 +msgid "Contents:" +msgstr "内容:" + +#: ../../admin/index.en.rst:54 +msgid "What Is Apache Traffic Server?" +msgstr "Apache Traffic Server とは" + +#: ../../admin/index.en.rst:56 +msgid "" +"Global data networking has become part of everyday life: Internet users " +"request billions of documents and terabytes of data, on a daily basis, to " +"and from all parts of the world. Information is free, abundant, and " +"accessible. Unfortunately, global data networking can also be a nightmare " +"for IT professionals as they struggle with overloaded servers and congested " +"networks. It can be challenging to consistently and reliably accommodate " +"society’s growing data demands." +msgstr "" +"グローバルなデータネットワークの利用は日常生活の一部となりました。インター" +"ネットユーザーは日常生活の基盤の上で数１０億ものドキュメントやテラバイトの" +"データを世界の隅から隅へリクエストします。不幸なことに、グローバルデータネッ" +"トワーキングは過負荷なサーバーや混雑したネットワークと格闘している IT 専門家" +"にとっては悪夢です。増え続けるデータ需要を絶えず、期待通りに動くように対応す" +"ることはチャレンジングなことです。" + +#: ../../admin/index.en.rst:64 +msgid "" +"Traffic Server is a high-performance web proxy cache that improves network " +"efficiency and performance by caching frequently-accessed information at " +"the edge of the network. This brings content physically closer to end " +"users, while enabling faster delivery and reduced bandwidth use. Traffic " +"Server is designed to improve content delivery for enterprises, Internet " +"service providers (ISPs), backbone providers, and large intranets by " +"maximizing existing and available bandwidth." +msgstr "" +"Traffic Server は高性能なウェブプロキシーキャッシュです。頻繁にアクセスされ" +"る情報をネットワークの端でキャッシュすることによりネットワーク効率とパフォー" +"マンスを改善します。これは物理的にエンドユーザーに近いコンテンツを届け、高速" +"な配信と帯域使用量の削減を可能とします。Traffic Server は商用のコンテンツ配" +"信やインターネットサービスプロバイダー( ISP )やバックボーンプロバイダーや巨" +"大なイントラネットを現行の利用可能な帯域を最大化することで改善するようにデザ" +"インされています。" + +#: ../../admin/index.en.rst:73 +msgid "Traffic Server Deployment Options" +msgstr "Traffic Server デプロイメントオプション" + +#: ../../admin/index.en.rst:75 +msgid "" +"To best suit your needs, Traffic Server can be deployed in several ways:" +msgstr "" +"必要に応じて、Traffic Server はいくつかの方法で配置することができます。" + +#: ../../admin/index.en.rst:77 +msgid "As a web proxy cache" +msgstr "ウェブプロキシーキャッシュとして" + +#: ../../admin/index.en.rst:78 +msgid "As a reverse proxy" +msgstr "リバースプロキシーとして" + +#: ../../admin/index.en.rst:79 +msgid "In a cache hierarchy" +msgstr "キャッシュ階層の一部として" + +#: ../../admin/index.en.rst:81 +msgid "" +"The following sections provide a summary of these Traffic Server deployment " +"options. Please keep in mind that with every of these options Traffic " +"Server can be run as a *single instance*, or as a *multi-node cluster*." +msgstr "" +"次のセクションではこれらの Traffic Server のデプロイメントオプションの概要を" +"説明します。これらのすべてのプションで Traffic Server は *シングルインスタン" +"ス* としても *マルチノードクラスター* としても動作することを覚えておいて下さ" +"い。" + +#: ../../admin/index.en.rst:87 +msgid "Traffic Server as a Web Proxy Cache" +msgstr "ウェブプロキシーキャッシュとしての Traffic Server" + +#: ../../admin/index.en.rst:89 +msgid "" +"As a web proxy cache, Traffic Server receives user requests for web content " +"as those requests travel to the destined web server (origin server). If " +"Traffic Server contains the requested content, then it serves the content " +"directly. If the requested content is not available from cache, then " +"Traffic Server acts as a proxy: it obtains the content from the origin " +"server on the user’s behalf and also keeps a copy to satisfy future " +"requests." +msgstr "" +"ウェブプロキシーキャッシュとして Traffic Server はウェブコンテンツへのユー" +"ザーリクエストを受け取り、宛先のウェブサーバー(オリジンサーバー)へ届けます。" +"Traffic Server がリクエストされたコンテンツを持っている場合、そのコンテンツ" +"を直接配信します。リクエストされたコンテンツがキャッシュから使えない場合、" +"Traffic Server はプロキシーとして振る舞います。つまり、コンテンツをユーザー" +"に代わってコンテンツを取得し、また将来のリクエストを満たすためにコピーを保持" +"します。" + +#: ../../admin/index.en.rst:97 +msgid "" +"Traffic Server provides explicit proxy caching, in which the user’s client " +"software must be configured to send requests directly to Traffic Server. " +"Explicit proxy caching is described in the :ref:`explicit-proxy-caching` " +"chapter." +msgstr "" +"Traffic Server は明確なプロキシーキャッシュを提供します。この場合ユーザーの" +"クライアントソフトウェアは Traffic Server に直接リクエストを送るように設定さ" +"れていなければなりません。明確なプロキシーキャッシュについては :ref:" +"`explicit-proxy-caching` の章で述べています。" + +#: ../../admin/index.en.rst:104 +msgid "Traffic Server as a Reverse Proxy" +msgstr "リバースプロキシーとしての Traffic Server" + +#: ../../admin/index.en.rst:106 +msgid "" +"As a reverse proxy, Traffic Server is configured to be the origin server to " +"which the user is trying to connect (typically, the origin server’s " +"advertised hostname resolves to Traffic Server, which acts as the real " +"origin server). The reverse proxy feature is also called server " +"acceleration. Reverse proxy is described in more detail in :ref:`reverse-" +"proxy-and-http-redirects`." +msgstr "" +"リバースプロキシーとして Traffc Server はユーザーが接続しようとするオリジン" +"サーバーとして設定されています。(一般的に、オリジンサーバーとして公開された" +"ホスト名は Traffic Server に解決され、実際のオリジンサーバーのように振る舞い" +"ます。)リバースプロキシー機能はサーバーアクセラレーションとも呼ばれます。リ" +"バースプロキシーは :ref:`reverse-proxy-and-http-redirects` で詳しく述べられ" +"ています。" + +#: ../../admin/index.en.rst:113 +msgid "Traffic Server in a Cache Hierarchy" +msgstr "キャッシュ階層での Traffic Server" + +#: ../../admin/index.en.rst:115 +msgid "" +"Traffic Server can participate in flexible cache hierarchies, in which " +"Internet requests not fulfilled from one cache are routed to other regional " +"caches, thereby leveraging the contents and proximity of nearby caches. In " +"a hierarchy of proxy servers, Traffic Server can act either as a parent or " +"a child cache to other Traffic Server systems or to similar caching " +"products." +msgstr "" +"Traffic Server は柔軟にキャッシュヒエラルキーに参加することができます。その" +"中で１つのキャッシュからは満たされないインターネットリクエストは他の局地的な" +"キャッシュに送られます。プロキシーサーバーの階層の中で Traffic Server は他の" +"Traffic Server システムや似たキャッシングプロダクトの親や子として振る舞いま" +"す。" + +#: ../../admin/index.en.rst:122 +msgid "" +"Traffic Server supports ICP (Internet Cache Protocol) peering. Hierarchical " +"caching is described in more detail in :ref:`hierarchical-caching`." +msgstr "" +"Traffic Server は ICP(Internet Cache Protocol) のピアイングをサポートしてい" +"ます。階層的キャッシュは :ref:`hierarchical-caching` で詳しく述べられていま" +"す。" + +#: ../../admin/index.en.rst:126 +msgid "Deployment Limitations" +msgstr "Deployment Limitations" + +#: ../../admin/index.en.rst:128 +msgid "" +"There's a number of deployment options that Traffic Server does not support " +"right out of the box. Such funcionality may be implemented in a plugin, but " +"in some cases Traffic Server's internal APIs or architectural restrictions " +"won't make it easy:" +msgstr "" +"Traffic Server がサポートしていないデプロイメントオプションがいくつかありま" +"す。そのような機能はプラグインで実装されていることもあります。またいくつかの" +"場合 Traffic Server の内部的な API やアーキテクチャ的な制限が実装を難しくし" +"ていることもあります。" + +#: ../../admin/index.en.rst:132 +msgid "" +"Load Balancing - note that there is an experimental plugin for this: :ref:" +"`balancer-plugin`." +msgstr "" +"ロードバランシング - このための実験的なプラクインがあることに注意してくださ" +"い。 :ref:`balancer-plugin`" + +#: ../../admin/index.en.rst:135 +msgid "Traffic Server Components" +msgstr "Traffic Server Components" + +#: ../../admin/index.en.rst:137 +msgid "" +"Traffic Server consists of several components that work together to form a " +"web proxy cache you can easily monitor and configure. These main components " +"are described below." +msgstr "" +"Traffic Server は簡単に監視や設定が行えるウェブプロキシーキャッシュを構成す" +"るために協力するいくつかのコンポーネントから成り立っています。これらのコン" +"ポーネントについて次に述べます。" + +#: ../../admin/index.en.rst:142 +msgid "The Traffic Server Cache" +msgstr "The Traffic Server Cache" + +#: ../../admin/index.en.rst:144 +msgid "" +"The Traffic Server cache consists of a high-speed object database called " +"the object store. The object store indexes objects according to URLs and " +"associated headers. Using sophisticated object management, the object store " +"can cache alternate versions of the same object (perhaps in a different " +"language or encoding type). It can also efficiently store very small and " +"very large objects, thereby minimizing wasted space. When the cache is " +"full, Traffic Server removes stale data to ensure that the most requested " +"objects are readily available and fresh." +msgstr "" +"Traffic Server キャッシュはオブジェクトストアと呼ばれるハイスピードオブジェ" +"クトデータベースによって構成されます。オブジェクトは URL と関連するヘッダー" +"に基づいたインデックスオブジェクトを保存します。洗練されたオブジェクト管理に" +"より、オブジェクトストアは同じオブジェクトの（言語やエンコーディングタイプな" +"どが）異なるバージョンをキャッシュすることができます。これは無駄なスペースを" +"最小化することによって、とても小さかったり、大きかったりするオブジェクトを効" +"率的に保存することもできます。キャッシュがいっぱいになった場合、Traffic " +"Server は最もリクエストされるオブジェクトがすぐに利用可能で新しい状態である" +"ことを保証するために、古いデータを削除します。" + +#: ../../admin/index.en.rst:153 +msgid "" +"Traffic Server is designed to tolerate total disk failures on any of the " +"cache disks. If the disk fails completely, then Traffic Server marks the " +"entire disk as corrupt and continues to use remaining disks. If all of the " +"cache disks fail, then Traffic Server switches to proxy-only mode. You can " +"partition the cache to reserve a certain amount of disk space for storing " +"data for specific protocols and origin servers. For more information about " +"the cache, see :ref:`configuring-the-cache`." +msgstr "" +"Traffic Server はすべてのキャッシュディスクのあらゆるディスク不良を許容する" +"ようにデザインされています。完全にディスクが壊れてしまった場合、Traffic " +"Server はそのディスクを破損したと印をつけ、残りのディスクを使い続けます。す" +"べてのディスクが壊れた場合、Traffic Server は proxy-only モードに切り替わり" +"ます。特定のプロトコルやオリジンサーバーのデータを保存するための一定のディス" +"クスペースを予約するためにキャッシュを分割することができます。キャッシュに関" +"するより詳しい情報は :ref:`configuring-the-cache` を参照してください。" + +#: ../../admin/index.en.rst:162 +msgid "The RAM Cache" +msgstr "The RAM Cache" + +#: ../../admin/index.en.rst:164 +msgid "" +"Traffic Server maintains a small RAM cache that contains extremely popular " +"objects. This RAM cache serves the most popular objects as fast as possible " +"and reduces load on disks, especially during temporary traffic peaks. You " +"can configure the RAM cache size to suit your needs; for detailed " +"information, refer to :ref:`changing-the-size-of-the-ram-cache`." +msgstr "" +"Traffic Server はとても頻繁にアクセスされるオブジェクトを含む小さな RAM " +"キャッシュを持っています。特に一時的なトラフィックのピークの間に、この RAM " +"キャッシュは最もポピュラーなオブジェクトを可能な限り速く提供し、ディスクから" +"のロードを減らします。この RAM キャッシュのサイズは必要な量に設定することが" +"できます。より詳しい情報は :ref:`changing-the-size-of-the-ram-cache` を参照" +"してください。" + +#: ../../admin/index.en.rst:171 +msgid "The Host Database" +msgstr "The Host Database" + +#: ../../admin/index.en.rst:173 +msgid "" +"The Traffic Server host database stores the domain name server (DNS) " +"entries of origin servers to which Traffic Server connects to fulfill user " +"requests. This information is used to adapt future protocol interactions " +"and optimize performance. Along with other information, the host database " +"tracks:" +msgstr "" +"Traffic Server は Traffic Server がユーザーリクエストを満たすために接続する" +"オリジンサーバーのドメインネームサーバー(DNS) のエントリを保存するデーター" +"ベースをホストします。この情報は将来のプロトコルインタラクションへの対応とパ" +"フォーマンスの最適化のために使われます。加えて、ホストデータベースは次の情報" +"を保存します。" + +#: ../../admin/index.en.rst:179 +msgid "DNS information (for fast conversion of hostnames to IP addresses)" +msgstr "DNS 情報(ホストネームから IP アドレスを高速に引くため)" + +#: ../../admin/index.en.rst:180 +msgid "" +"The HTTP version of each host (so advanced protocol features can be used " +"with hosts running modern servers)" +msgstr "" +"各ホストの HTTP バージョン(最新のプロトコルの機能はモダンなサーバーで使われ" +"ているかもしれないため)" + +#: ../../admin/index.en.rst:182 +msgid "" +"Host reliability and availability information (so users will not wait for " +"servers that are not running)" +msgstr "" +"信頼性と可用性の情報(ユーザーが起動していないサーバーを待つことがないように)" + +#: ../../admin/index.en.rst:186 +msgid "The DNS Resolver" +msgstr "The DNS Resolver" + +#: ../../admin/index.en.rst:188 +msgid "" +"Traffic Server includes a fast, asynchronous DNS resolver to streamline " +"conversion of hostnames to IP addresses. Traffic Server implements the DNS " +"resolver natively by directly issuing DNS command packets rather than " +"relying on slower, conventional resolver libraries. Since many DNS queries " +"can be issued in parallel and a fast DNS cache maintains popular bindings " +"in memory, DNS traffic is reduced." +msgstr "" +"Traffic Server はホスト名から IP アドレスへの変換を統合するために、高速で非" +"同期な DNS リゾルバも含んでいます。Traffic Server は遅くて月並みなリゾルバラ" +"イブラリに渡すよりも、直接 DNS コマンドパケットを渡すことによって、DNS リゾ" +"ルバをネイティブに実行します。多くの DNS クエリが並列で渡され、高速な DNS " +"キャッシュがポピュラーなバインディングをメモリに保存することにより、DNS トラ" +"フィックは減ります。" + +#: ../../admin/index.en.rst:196 +msgid "Traffic Server Processes" +msgstr "Traffic Server Processes" + +#: ../../admin/index.en.rst:198 +msgid "" +"Traffic Server contains three processes that work together to serve " +"requests and manage/control/monitor the health of the system. The three " +"processes are described below:" +msgstr "" +"Traffic Server は 3 つのプロセスから構成されます。それらはリクエストを返し、" +"システムの状態を管理/制御/監視するために協調して動きます。この 3 つのプロセ" +"スは下に説明されています。" + +#: ../../admin/index.en.rst:202 +msgid "" +"The :program:`traffic_server` process is the transaction processing engine " +"of Traffic Server. It is responsible for accepting connections, processing " +"protocol requests, and serving documents from the cache or origin server." +msgstr "" +":program:`traffic_server` プロセスは Traffic Server のトランザクションプロ" +"セッシングエンジンです。コネクションをアクセプトしたり、プロトコルリクエスト" +"を処理したり、キャッシュやオリジンサーバーからドキュメントを提供することに責" +"任を持ちます。" + +#: ../../admin/index.en.rst:207 +msgid "" +"The :program:`traffic_manager` process is the command and control facility " +"of the Traffic Server, responsible for launching, monitoring, and " +"reconfiguring the :program:`traffic_server` process. The :program:" +"`traffic_manager` process is also responsible for the proxy " +"autoconfiguration port, the statistics interface, cluster administration, " +"and virtual IP failover." +msgstr "" +":program:`traffic_manager` プロセスは Traffic Server への命令と管理機能で" +"す。起動や監視と :program:`traffic_server` プロセスを再設定したりすることに" +"責任を持ちます。 :program:`traffic_manager` プロセスはプロキシオートコンフィ" +"ギュレーションポートや統計のインターフェイスやクラスター管理とバーチャル IP " +"フェイルオーバーについても責任を持ちます。" + +#: ../../admin/index.en.rst:214 +msgid "" +"If the :program:`traffic_manager` process detects a :program:" +"`traffic_server` process failure, it instantly restarts the process but " +"also maintains a connection queue of all incoming requests. All incoming " +"connections that arrive in the several seconds before full server restart " +"are saved in the connection queue and processed in first-come, first-served " +"order. This connection queueing shields users from any server restart " +"downtime." +msgstr "" +":program:`traffic_manager` プロセスが :program:`traffic_server` プロセスが失" +"敗していることを検知した場合、即座にプロセスを再起動するだけでなく、すべての" +"リクエストのコネクションキューをメンテナンスします。サーバーが完全に再起動す" +"る数秒前に到着したすべてのインカミングコネクションはコネクションキューに格納" +"され、最初に来たものから順に処理されます。このコネクションキューはすべての" +"サーバーの再起動の際のダウンタイムからユーザーを守ります。" + +#: ../../admin/index.en.rst:222 +msgid "" +"The :program:`traffic_cop` process monitors the health of both the :program:" +"`traffic_server` and :program:`traffic_manager` processes. The :program:" +"`traffic_cop` process periodically (several times each minute) queries the :" +"program:`traffic_server` and :program:`traffic_manager` process by issuing " +"heartbeat requests to fetch synthetic web pages. In the event of failure " +"(if no response is received within a timeout interval or if an incorrect " +"response is received), :program:`traffic_cop` restarts the :program:" +"`traffic_manager` and :program:`traffic_server` processes." +msgstr "" +":program:`traffic_cop` プロセスは :program:`traffic_server` と :program:" +"`traffic_manager` プロセスの両方の状態をモニターします。 :program:" +"`traffic_cop` プロセスは定期的(毎分数回)に静的なウェブページを取得するハート" +"ビートリクエストを渡すことで :program:`traffic_server` と :program:" +"`traffic_manager` に問い合わせます。失敗したとき(一定期間の間にレスポンスが" +"帰って来ないときや不正なレスポンスを受け取ったとき) :program:`traffic_cop` " +"は :program:`traffic_manager` と :program:`traffic_server` プロセスを再起動" +"します。" + +#: ../../admin/index.en.rst:231 +msgid "The figure below illustrates the three Traffic Server processes." +msgstr "次の図は Traffic Server の3つのイラストです。" + +#: ../../admin/index.en.rst:237 +msgid "Illustration of the three Traffic Server Processes" +msgstr "Illustration of the three Traffic Server Processes" + +#: ../../admin/index.en.rst:240 +msgid "Administration Tools" +msgstr "Administration Tools" + +#: ../../admin/index.en.rst:242 +msgid "Traffic Server offers the following administration options:" +msgstr "Traffic Server は次の管理オプションを提供しています。" + +#: ../../admin/index.en.rst:244 +msgid "" +"The Traffic Line command-line interface is a text-based interface from " +"which you can monitor Traffic Server performance and network traffic, as " +"well as configure the Traffic Server system. From Traffic Line, you can " +"execute individual commands or script a series of commands in a shell." +msgstr "" +"Traffic Line コマンドラインインターフェイスはテキストベースのインターフェー" +"スです。Traffic Server のパフォーマンスとネットワークトラフィックを監視でき" +"ます。また同じように、Traffic Server システムを設定することもできます。" +"Traffic Line によって独立したコマンドや一連のコマンドのスクリプトをシェルで" +"実行することができます。" + +#: ../../admin/index.en.rst:249 +msgid "" +"The Traffic Shell command-line interface is an additional command-line tool " +"that enables you to execute individual commands that monitor and configure " +"the Traffic Server system." +msgstr "" +"Traffic Shell コマンドラインインターフェイスは追加のコマンドラインツールで、" +"Traffic Server システムを監視したり設定したりする独立したコマンドを実行する" +"ことができます。Traffic Line や Traffic Shell を通じたどんな変更も自動的に設" +"定ファイルを作ります。" + +#: ../../admin/index.en.rst:252 +msgid "" +"Various configuration files enable you to configure Traffic Server through " +"a simple file-editing and signal-handling interface. Any changes you make " +"through Traffic Line or Traffic Shell are automatically made to the " +"configuration files as well." +msgstr "" +"様々な設定ファイルはシンプルなファイル編集とシグナルハンドリングインター" +"フェースを通して、Traffic Server を設定することを可能とします。Traffic Line " +"か Traffic Shell を通じたどのような変更でも自動的に設定ファイルに書き込まれ" +"ます。" + +#: ../../admin/index.en.rst:256 +msgid "" +"Finally there is a clean C API which can be put to good use from a " +"multitude of languages. The Traffic Server Admin Client demonstrates this " +"for Perl." +msgstr "" +"最後に、多くの言語から使うことのできるクリーンな C API があります。 Traffic " +"Server Admin Client は Perl でこのことを示しています。" + +#: ../../admin/index.en.rst:261 +msgid "Traffic Analysis Options" +msgstr "Traffic Analysis Options" + +#: ../../admin/index.en.rst:263 +msgid "" +"Traffic Server provides several options for network traffic analysis and " +"monitoring:" +msgstr "" +"Traffic Server はネットワークトラフィックの分析と監視のためのいくつかのオプ" +"ションを提供しています。" + +#: ../../admin/index.en.rst:266 +msgid "" +"Traffic Line and Traffic Shell enable you to collect and process statistics " +"obtained from network traffic information." +msgstr "" +"Traffic Line と Traffic Shell はネットワークトラフィック情報から入手した統計" +"情報を集めて処理することを可能にします。" + +#: ../../admin/index.en.rst:269 +msgid "" +"Transaction logging enables you to record information (in a log file) about " +"every request Traffic Server receives and every error it detects. By " +"analyzing the log files, you can determine how many clients used the " +"Traffic Server cache, how much information each of them requested, and what " +"pages were most popular. You can also see why a particular transaction was " +"in error and what state the Traffic Server was in at a particular time; for " +"example, you can see that Traffic Server was restarted or that cluster " +"communication timed out." +msgstr "" +"トランザクションロギングは Traffic Server が処理したへすべてのリクエストとす" +"べての検知したエラーの情報を (ログファイルの中に) 記録することを可能にしま" +"す。ログファイルを分析することによって、どれほどのクライアントが Traffic " +"Sever キャッシュを使用し、どれくらいの情報がリクエストされ、どのページがポ" +"ピュラーなのかを確認することができます。特定のトランザクションがなぜエラーに" +"なり、そのときの Traffic Server の状態がどうだったのかみることもできます。例" +"えば Traffic Server が再起動したときや、クラスターコミュニケーションがタイム" +"アウトしたときなどです。" + +#: ../../admin/index.en.rst:278 +msgid "" +"Traffic Server supports several standard log file formats, such as Squid " +"and Netscape, and its own custom format. You can analyze the standard " +"format log files with off-the-shelf analysis packages. To help with log " +"file analysis, you can separate log files so that they contain information " +"specific to protocol or hosts." +msgstr "" +"Traffic Server は Squid や Netscape などのいくつかの標準的なログフォーマット" +"や固有のフォーマットをサポートしています。off-the-shelf 分析パッケージによっ" +"て標準的なフォーマットのログを分析することができます。ログファイルの分析を助" +"けるために、特定のプロトコルやホストの情報を含むようにログファイルを分割する" +"ことができます。" + +#: ../../admin/index.en.rst:284 +msgid "" +"Traffic analysis options are described in more detail in :ref:`monitoring-" +"traffic`." +msgstr "" +"トラフィック分析オプションは :ref:`monitoring-traffic` により詳しく書かれて" +"います。" + +#: ../../admin/index.en.rst:286 +msgid "" +"Traffic Server logging options are described in :ref:`working-with-log-" +"files`." +msgstr "" +"Traffic Server ロギングオプションは :ref:`working-with-log-files` に書かれて" +"います。" + +#: ../../admin/index.en.rst:289 +msgid "Traffic Server Security Options" +msgstr "Traffic Server Security Options" + +#: ../../admin/index.en.rst:291 +msgid "" +"Traffic Server provides numerous options that enable you to establish " +"secure communication between the Traffic Server system and other computers " +"on the network. Using the security options, you can do the following:" +msgstr "" +"Traffic Server は Traffic Server システムと他のコンピュータネットワーク間の" +"セキュアな通信を確立することを可能にする多数のオプションを提供しています。セ" +"キュリティオプションを使うことによって、次のことが可能です。" + +#: ../../admin/index.en.rst:296 +msgid "Control client access to the Traffic Server proxy cache." +msgstr "Traffic Server プロキシーキャッシュにアクセスするクライアントの管理" + +#: ../../admin/index.en.rst:297 +msgid "" +"Configure Traffic Server to use multiple DNS servers to match your site's " +"security configuration. For example, Traffic Server can use different DNS " +"servers, depending on whether it needs to resolve hostnames located inside " +"or outside a firewall. This enables you to keep your internal network " +"configuration secure while continuing to provide transparent access to " +"external sites on the Internet." +msgstr "" +"あなたのサイトのセキュリティ設定に合わせて複数の DNS サーバーを使うような " +"Traffic Server の設定。例えば Traffic Server はホストネームを解決する必要が" +"あるのがファイアーウォールの内側か外側かによって異なる DNS サーバーを使うこ" +"とができます。これは透過的にインターネット上の外部サイトにアクセスすることを" +"提供しつつ、インターナルネットワーク設定をセキュアに保つことを可能にします。" + +#: ../../admin/index.en.rst:303 +msgid "" +"Configure Traffic Server to verify that clients are authenticated before " +"they can access content from the Traffic Server cache." +msgstr "" +"クライアントが Traffic Server キャッシュからコンテンツにアクセスできるように" +"なる前に、クライアントが認証されていることを検証する Traffic Server 設定" + +#: ../../admin/index.en.rst:305 +msgid "" +"Secure connections in reverse proxy mode between a client and Traffic " +"Server, and Traffic Server and the origin server, using the SSL termination " +"option." +msgstr "" +"SSL ターミネーションオプションを使うことによる、リバースプロキシーモードでの" +"クライアントと Traffic Server 間と Traffic Server とオリジンサーバー間の安全" +"な接続" + +#: ../../admin/index.en.rst:308 +msgid "Control access via SSL (Secure Sockets Layer)." +msgstr "SSL (Secure Socket Layer) によるアクセスの管理" + +#: ../../admin/index.en.rst:310 +msgid "" +"Traffic Server security options are described in more detail in :ref:" +"`security-options`." +msgstr "" +"Traffic Server セキュリティオプションは :ref:`security-options` に詳しく述べ" +"られています。" + +#: ../../admin/index.en.rst:314 +msgid "Tuning Traffic Server" +msgstr "Traffic Server のチューニング" + +#: ../../admin/index.en.rst:316 +msgid "" +"Finally this last chapter on :ref:`performance-tuning` discusses the vast " +"number of options that allow to optimally tune Apache Traffic Server for " +"maximum performance." +msgstr "" +"最後にこの最終章 :ref:`performance-tuning` で Apache Traffic Server が最大限" +"のパフォーマンスを発揮するように最適なチューニングをするための膨大な数のオプ" +"ションについて論じます。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/monitoring-traffic.en.po b/doc/locale/ja/LC_MESSAGES/admin/monitoring-traffic.en.po new file mode 100644 index 00000000000..7f744945c25 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/monitoring-traffic.en.po @@ -0,0 +1,142 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/monitoring-traffic.en.rst:5 +msgid "Monitoring Traffic" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:24 +msgid "" +"Traffic Server provides several options for monitoring system performance " +"and analyzing network traffic." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:31 +msgid "Traffic Server Monitoring Tools" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:33 +msgid "" +"Traffic Server provides the following tools to monitor system performance " +"and analyze network traffic:" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:36 +msgid "" +"Traffic Server can send email that's triggered by alarms that signal any " +"detected failure conditions; refer to `Working with Traffic Manager " +"Alarms`_." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:38 +msgid "" +"The Traffic Line command-line interface provides an alternative method of " +"viewing Traffic Server performance and network traffic information; refer " +"to `Viewing Statistics from Traffic Line`_." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:41 +msgid "" +"The Traffic Shell command-line tool provides yet another alternative method " +"of viewing Traffic Server performance and network traffic information; " +"refer to `Starting Traffic Shell <../getting-started#StartTrafficShell>`_." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:48 +msgid "Working with Traffic Manager Alarms" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:50 +msgid "" +"Traffic Server signals an alarm when it detects a problem. For example, the " +"space allocated to event logs could be full or Traffic Server may not be " +"able to write to a configuration file." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:55 +msgid "Configuring Traffic Server to Email Alarms" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:57 +msgid "" +"To configure Traffic Server to send an email to a specific address whenever " +"an alarm occurs, follow the steps below:" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:60 +msgid "In the :file:`records.config` file" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:61 +msgid "" +"Set the :ts:cv:`proxy.config.alarm_email` variable to the email address " +"alarms will be routed to." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:62 +msgid "" +"Run the command :option:`traffic_line -x` to apply the configuration " +"changes." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:66 +msgid "Using a Script File for Alarms" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:68 +msgid "" +"Alarm messages are built into Traffic Server - you cannot change them. " +"However, you can write a script file to execute certain actions when an " +"alarm is signaled. Traffic Server provides a sample script file named " +"``example_alarm_bin.sh`` in the ``bin`` directory; simply modify the file " +"to suit your needs." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:75 +msgid "Viewing Statistics from Traffic Line" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:77 +msgid "" +"You can use the Traffic Line command-line interface to view statistics " +"about Traffic Server performance and web traffic. In addition to viewing " +"statistics, you can also configure, stop, and restart the Traffic Server " +"system. For additional information, refer to :ref:`configure-using-traffic-" +"line` and :ref:`traffic-line-commands`. You can view specific information " +"about a Traffic Server node or cluster by specifying the variable that " +"corresponds to the statistic you want to see." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:86 +msgid "**To view a statistic**, enter the following command:::" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:90 +msgid "" +"where ``variable`` is the variable representing the information you want to " +"view. For a list of variables you can specify, refer to :ref:`Traffic Line " +"Variables `." +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:94 +msgid "" +"For example, the following command displays the document hit rate for the " +"Traffic Server node:::" +msgstr "" + +#: ../../admin/monitoring-traffic.en.rst:99 +msgid "" +"If the Traffic Server ``bin`` directory is not in your path, then prepend " +"the Traffic Line command with ``./`` (for example: :option:`traffic_line -" +"r` ``variable``)." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/admin/performance-tuning.en.po b/doc/locale/ja/LC_MESSAGES/admin/performance-tuning.en.po new file mode 100644 index 00000000000..dbc2b9aaaca --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/performance-tuning.en.po @@ -0,0 +1,57 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-15 22:31+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/performance-tuning.en.rst:5 +msgid "Performance Tuning" +msgstr "" + +#: ../../admin/performance-tuning.en.rst:29 +msgid "Before you start" +msgstr "" + +#: ../../admin/performance-tuning.en.rst:31 +msgid "" +"There is no single option to that will guarantee maximum performance of " +"Apache Traffic Server in every use-case. There are however numerous options " +"that help tune its performance under different loads and in its - often " +"vastly different - use-cases." +msgstr "" + +#: ../../admin/performance-tuning.en.rst:37 +msgid "Building Traffic Server" +msgstr "" + +#: ../../admin/performance-tuning.en.rst:39 +msgid "" +"A lot of speed can be gained or lost depending on the way ATS is built." +msgstr "" + +#: ../../admin/performance-tuning.en.rst:42 +msgid "Tuning the Machine" +msgstr "" + +#: ../../admin/performance-tuning.en.rst:45 +msgid "Operating Systems Options" +msgstr "" + +#: ../../admin/performance-tuning.en.rst:48 +msgid "Optimal Use of Memory" +msgstr "" + +#: ../../admin/performance-tuning.en.rst:51 +msgid "Tuning different Thread types" +msgstr "" + +#: ../../admin/performance-tuning.en.rst:54 +msgid "Tuning Plugin Execution" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/admin/reverse-proxy-http-redirects.en.po b/doc/locale/ja/LC_MESSAGES/admin/reverse-proxy-http-redirects.en.po new file mode 100644 index 00000000000..bfaa1d89378 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/reverse-proxy-http-redirects.en.po @@ -0,0 +1,611 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:5 +#: ../../admin/reverse-proxy-http-redirects.en.rst:26 +msgid "Reverse Proxy and HTTP Redirects" +msgstr "リバースプロキシーと HTTP リダイレクト" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:28 +msgid "" +"As a reverse proxy cache, Traffic Server serves requests on behalf of " +"origin servers. Traffic Server is configured in such a way that it appears " +"to clients like a normal origin server." +msgstr "" +"リバースプロキシーキャッシュとして、Traffic Server はオリジンサーバーの代わ" +"りにリクエストに応えます。Traffic Server はクライアントには通常のオリジン" +"サーバーに見えるように設定されます。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:37 +msgid "Understanding Reverse Proxy Caching" +msgstr "リバースプロキシーキャッシュを理解する" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:39 +msgid "" +"With **forward proxy caching**, Traffic Server handles web requests to " +"distant origin servers on behalf of the clients requesting the content. " +"**Reverse proxy caching** (also known as **server acceleration** or " +"**virtual web hosting**) is different because Traffic Server acts as a " +"proxy cache on behalf of the origin servers that store the content. Traffic " +"Server is configured to be *the* origin server which the client is trying " +"to connect to. In a typical scenario the advertised hostname of the origin " +"server resolves to Traffic Server, which acts as the real origin server." +msgstr "" +"\\ **フォワードプロキシーキャッシュ**\\ の場合、Traffic Server はコンテンツ" +"をリクエストしたクライアントに代わって遠くはなれたオリジンサーバーへのリクエ" +"ストを取り扱います。\\ **リバースプロキシーキャッシュ**\\ (\\ **サーバーアク" +"セラレーション**\\ や\\ **バーチャルウェブホスティング**\\ としても知られて" +"います)では Traffic Server がコンテンツを持っているオリジンサーバーに代わっ" +"てプロキシーキャッシュとして振る舞う点が異なります。Traffic Server はクライ" +"アントが接続しようとしている\\ *その*\\ オリジンサーバーとなるように設定され" +"ます。典型的なシナリオとしては、オリジンサーバーの広告されたホスト名が本当の" +"オリジンサーバーのように振る舞う Traffic Server へ解決されます。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:50 +msgid "Reverse Proxy Solutions" +msgstr "リバースプロキシーによる対応策" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:52 +msgid "" +"There are many ways to use Traffic Server as a reverse proxy. Below are a " +"few example scenarios." +msgstr "" +"Traffic Server をリバースプロキシーとして使う方法はたくさんあります。以下は" +"いくつかの例です。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:55 +msgid "You can use Traffic Server in reverse proxy mode to:" +msgstr "Traffic Server をリバースプロキシーモードとして使うことでできること" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:57 +msgid "Offload heavily-used origin servers" +msgstr "使用頻度の高いオリジンサーバーの負荷を軽減する" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:58 +msgid "Deliver content efficiently in geographically distant areas" +msgstr "地理的に離れた地域に効率的にコンテントを配信する" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:59 +msgid "Provide security for origin servers that contain sensitive information" +msgstr "センシティブな情報を含むオリジンサーバーにセキュリティを提供する" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:63 +msgid "Offloading Heavily-Used Origin Servers" +msgstr "使用頻度の高いオリジンサーバーの負荷の軽減" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:65 +msgid "" +"Traffic Server can absorb requests to the main origin server and improve " +"the speed & quality of web serving by reducing load and hot spots on backup " +"origin servers. For example, a web hoster can maintain a scalable Traffic " +"Server serving engine with a set of low-cost, low-performance, less-" +"reliable PC origin servers as backup servers. In fact, a single Traffic " +"Server can act as the virtual origin server for multiple backup origin " +"servers, as shown in the figure below." +msgstr "" +"Traffic Server は主となるオリジンサーバーへのリクエストを吸収できるほか、" +"バックアップオリジンサーバーの負荷とホットスポットを低減することでWeb の提供" +"スピードと品質を向上させます。例えば、Web をホストする人は低コストで低パ" +"フォーマンスで信頼性の低い PC によるオリジンサーバーをバックアップサーバーと" +"したエンジンを提供するスケーラブルな Traffic Server を維持することができま" +"す。実際、下記の図に示すように、1台の Traffic Server は複数のバックアップオ" +"リジンサーバーのために仮想的なオリジンサーバーとして振る舞うことが可能です。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:77 +msgid "Traffic Server as reverse proxy for a pair of origin servers" +msgstr "1組のオリジンサーバーのリバースプロキシーとして動く Traffic Server" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:80 +msgid "Delivering Content in Geographically-Dispersed Areas" +msgstr "分散した地域でのコンテンツの配信" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:82 +msgid "" +"Traffic Server can be used in reverse proxy mode to accelerate origin " +"servers that provide content to areas not located within close geographical " +"proximity. Caches are typically easier to manage and are more cost-" +"effective than replicating data. For example, Traffic Server can be used as " +"a mirror site on the far side of a trans-Atlantic link to serve users " +"without having to fetch the request and content across expensive " +"international connections. Unlike replication, for which hardware must be " +"configured to replicate all data and to handle peak capacity, Traffic " +"Server dynamically adjusts to optimally use the serving and storing " +"capacity of the hardware. Traffic Server is also designed to keep content " +"fresh automatically, thereby eliminating the complexity of updating remote " +"origin servers." +msgstr "" +"Traffic Server は地理的に近接していないエリアにコンテンツを提供するオリジン" +"サーバーを加速するためにリバースプロキシーモードで使用できます。キャッシュは" +"レプリケーションよりもコストパフォーマンスが高く、一般的により簡単です。例え" +"ば、高価な国をまたぐコネクションを使ってリクエストやコンテンツを取得すること" +"なく大西洋の向こう側のミラーサイトとして Traffic Server を利用することができ" +"ます。全データを複製しピークキャパシティも扱うレプリケーションとは異なり、" +"Traffic Server はハードウェアのキャパシティを最適に利用するよう動的に順応し" +"ます。Traffic Server は自動的にコンテンツを新鮮に保つようにも設計されている" +"ので、リモートオリジンサーバーをアップデートする複雑さも除去できます。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:96 +msgid "Providing Security for an Origin Server" +msgstr "オリジンサーバーへのセキュリティの提供" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:98 +msgid "" +"Traffic Server can be used in reverse proxy mode to provide security for an " +"origin server. If an origin server contains sensitive information that you " +"want to keep secure inside your firewall, then you can use a Traffic Server " +"outside the firewall as a reverse proxy for that origin server. When " +"outside clients try to access the origin server, the requests instead go to " +"Traffic Server. If the desired content is *not* sensitive, then it can be " +"served from the cache. If the content is sensitive and not cacheable, then " +"Traffic Server obtains the content from the origin server (the firewall " +"allows only Traffic Server access to the origin server). The sensitive " +"content resides on the origin server, safely inside the firewall." +msgstr "" +"Traffic Server はオリジンサーバーにセキュリティを提供するためにリバースプロ" +"キシーモードで使用できます。もしファイアーウォールの内側にあるオリジンサー" +"バーが安全にしておきたいセンシティブな情報を持っている場合、Traffic Server " +"をファイアーウォールの外側におき、そのオリジンサーバーのためのリバースプロキ" +"シーとして使用できます。外部のクライアントがそのオリジンサーバーにアクセスを" +"試みるとリクエストは Traffic Server に向かいます。もし求められたコンテンツが" +"センシティブでは\\ *ない*\\ 場合、それはキャッシュから提供されます。もしコン" +"テンツがセンシティブでありキャッシュ不可能な場合、Traffic Server はオリジン" +"サーバーからコンテンツを取得します(ファイアーウォールはオリジンサーバーへの" +"アクセスを Traffic Server にのみ許します)。センシティブなコンテンツは安全な" +"ファイアーウォールの内側のオリジンサーバー上にあります。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:111 +msgid "How Does Reverse Proxy Work?" +msgstr "リバースプロキシーの動作" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:113 +msgid "" +"When a browser makes a request, it normally sends that request directly to " +"the origin server. When Traffic Server is in reverse proxy mode, it " +"intercepts the request before it reaches the origin server. Typically, this " +"is done by setting up the DNS entry for the origin server (i.e., the origin " +"server's 'advertised' hostname) so it resolves to the Traffic Server IP " +"address. When Traffic Server is configured as the origin server, the " +"browser connects to Traffic Server rather than the origin server. For " +"additional information, see `HTTP Reverse Proxy`_." +msgstr "" +"ブラウザーがリクエストを行うとき、通常はリクエストを直接オリジンサーバーに送" +"信します。Traffic Server がリバースプロキシーモードになっているときはリクエ" +"ストがオリジンサーバーに届く前に Traffic Server が横取りします。通常これはオ" +"リジンサーバーの DNS エントリー(オリジンサーバーの'広告された'ホスト名)を " +"Traffic Server の IP アドレスに解決されるように設定すれば完了です。Traffic " +"Server がオリジンサーバーとして設定されている場合、ブラウザーはオリジンサー" +"バーではなく Traffic Server に接続します。より詳しくは `HTTP リバースプロキ" +"シー`_\\ を見てください。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:122 +msgid "" +"To avoid a DNS conflict, the origin server’s hostname and its advertised " +"hostname must not be the same." +msgstr "" +"DNS の衝突を避けるため、オリジンサーバーのホスト名とその広告されたホスト名は" +"同じであってはなりません。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:125 +msgid "HTTP Reverse Proxy" +msgstr "HTTP リバースプロキシー" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:127 +msgid "" +"In reverse proxy mode, Traffic Server serves HTTP requests on behalf of a " +"web server. The figure below illustrates how Traffic Server in reverse " +"proxy mode serves an HTTP request from a client browser." +msgstr "" +"リバースプロキシーモードでは、Traffic Server は HTTP リクエストをウェブサー" +"バーの代わりに受け取ります。下の図は リバースプロキシーモードの Traffic " +"Server がどのようにクライアントからの HTTP リクエストを受け取るのかを説明し" +"ています。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:135 +msgid "HTTP reverse proxy" +msgstr "HTTP リバースプロキシー" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:137 +msgid "The figure above demonstrates the following steps:" +msgstr "上の図は次のステップを説明しています。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:139 +msgid "" +"A client browser sends an HTTP request addressed to a host called ``www." +"host.com`` on port 80. Traffic Server receives the request because it is " +"acting as the origin server (the origin server’s advertised hostname " +"resolves to Traffic Server)." +msgstr "" +"クライアントブラウザが ``www.host.com`` の 80 番ポートに HTTP リクエストを送" +"信します。Traffic Server はオリジンサーバーとして振る舞っているのでこのリク" +"エストを受け取ります(オリジンサーバーの広告されたホスト名は Traffic Server " +"へ解決されるように広告されています)。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:143 +msgid "" +"Traffic Server locates a map rule in the ``remap.config`` file and remaps " +"the request to the specified origin server (``realhost.com``)." +msgstr "" +"Traffic Server は ``remap.config`` ファイル内にあるマップルールを見つけ、リ" +"クエストを指定されたオリジンサーバー(``realhost.com``)にリマップします。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:145 +msgid "" +"Traffic Server opens an HTTP connection to the origin server. (If the " +"request is not able to be served from cache)" +msgstr "" +"Traffic Server は オリジンサーバーへの HTTP コネクションを開きます。(もしリ" +"クエストにキャッシュから応えられなかった場合)" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:146 +msgid "" +"If the request is a cache hit and the content is fresh, then Traffic Server " +"sends the requested object to the client from the cache. Otherwise, Traffic " +"Server obtains the requested object from the origin server, sends the " +"object to the client, and saves a copy in its cache." +msgstr "" +"もしリクエストがキャッシュにヒットしコンテンツが新鮮であれば、Traffic " +"Server はリクエストされたオブジェクトをキャッシュからクライアントに送信しま" +"す。そうではなく、Traffic Server がオリジンサーバーからリクエストされたオブ" +"ジェクトを取得した場合は、そのオブジェクトをクライアントに送信し、コピーを" +"キャッシュに保存します。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:152 +msgid "To configure HTTP reverse proxy, you must perform the following tasks:" +msgstr "" +"HTTP リバースプロキシーを設定するためには、次のタスクを行う必要があります" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:154 +msgid "" +"Create mapping rules in the :file:`remap.config` file (refer to `Creating " +"Mapping Rules for HTTP Requests`_). ::" +msgstr "" +":file:`remap.config` ファイルにマッピングルールを作成する (`HTTP リクエスト" +"用マッピングルールの作成`_\\ を参照してください) 。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:160 +msgid "" +"Enable the reverse proxy option (refer to `Enabling HTTP Reverse Proxy`_)." +msgstr "" +"リバースプロキシーオプションを有効にする(`HTTP リバースプロキシーの有効化`_" +"\\ を参照してください)。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:162 +msgid "" +"In addition to the tasks above, you can also `Setting Optional HTTP Reverse " +"Proxy Options`_." +msgstr "" +"上のタスクに加え、\\ `省略可能な HTTP リバースプロキシーオプションの設定`_" +"\\ を行うこともできます。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:165 +msgid "Handling Origin Server Redirect Responses" +msgstr "オリジンサーバーのリダイレクトレスポンスを扱う" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:167 +msgid "" +"Origin servers often send redirect responses back to browsers redirecting " +"them to different pages. For example, if an origin server is overloaded, " +"then it might redirect browsers to a less loaded server. Origin servers " +"also redirect when web pages that have moved to different locations. When " +"Traffic Server is configured as a reverse proxy, it must readdress " +"redirects from origin servers so that browsers are redirected to Traffic " +"Server and *not* to another origin server." +msgstr "" +"オリジンサーバーはしばしばブラウザーを他のページにリダイレクトするためにリダ" +"イレクトレスポンスを返します。例えば、オリジンサーバーが過負荷になった場合に" +"は負荷の少ないサーバーへブラウザーをリダイレクトするかもしれません。オリジン" +"サーバーはウェブページが異なる場所に移動された場合にもリダイレクトを行いま" +"す。Traffic Server がリバースプロキシーとして設定されている場合、ブラウザー" +"が他のオリジンサーバー\\ *ではなく* Traffic Server にリダイレクトされるよう" +"に、リダイレクト先をオリジンサーバーから書き換えなければなりません。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:175 +msgid "" +"To readdress redirects, Traffic Server uses reverse-map rules. Unless you " +"have :ts:cv:`proxy.config.url_remap.pristine_host_hdr` enabled (the " +"default) you should generally set up a reverse-map rule for each map rule. " +"To create reverse-map rules, refer to `Using Mapping Rules for HTTP " +"Requests`_." +msgstr "" +"リダイレクト先を書き直すために、Traffic Server はリバースマップルールを使用" +"します。 :ts:cv:`proxy.config.url_remap.pristine_host_hdr` を有効にしていな" +"い限り(それがデフォルトです)、一般的には各マップルールに対してリバースマップ" +"ルールを用意すべきです。リバースマップルールを作成するには `HTTP リクエスト" +"用マッピングルールの使用`_\\ を参照してください。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:182 +msgid "Using Mapping Rules for HTTP Requests" +msgstr "HTTP リクエスト用マッピングルールの使用" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:184 +msgid "Traffic Server uses two types of mapping rules for HTTP reverse proxy." +msgstr "" +"Traffic Server は HTTP リバースプロキシー用に2タイプのマッピングルールを使用" +"します。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:187 +msgid "map rule" +msgstr "マップルール" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:189 +msgid "" +"A **map rule** translates the URL in client requests into the URL where the " +"content is located. When Traffic Server is in reverse proxy mode and " +"receives an HTTP client request, it first constructs a complete request URL " +"from the relative URL and its headers. Traffic Server then looks for a " +"match by comparing the complete request URL with its list of target URLs in " +"the :file:`remap.config` file. For the request URL to match a target URL, " +"the following conditions must be true:" +msgstr "" +"\\ **マップルール**\\ はクライアントのリクエストに含まれる URL をコンテンツ" +"が存在する場所に変換します。Traffic Server がリバースプロキシーモードで " +"HTTP クライアントリクエストを受け取ると、相対 URL とヘッダーから完全な URL " +"を組み立てます。そしてその完全な URL と :file:`remap.config` ファイル内の" +"ターゲット URL とを比較し、マッチするものを探します。ターゲット URL にマッチ" +"するリクエスト URL は次の条件を満たさなければなりません" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:198 +msgid "The scheme of both URLs must be the same" +msgstr "URL のスキームが同じであること" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:199 +msgid "" +"The host in both URLs must be the same. If the request URL contains an " +"unqualified hostname, then it will never match a target URL with a fully-" +"qualified hostname." +msgstr "" +"URL のホストが同じであること。もしリクエスト URL が修飾されていないホスト名" +"を含んでいる場合、完全修飾されたホスト名を含むターゲット URL にはマッチしま" +"せん。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:202 +msgid "" +"The ports in both URLs must be the same. If no port is specified in a URL, " +"then the default port for the scheme of the URL is used." +msgstr "" +"ポートが同じであること。もし URL にポートが指定されていない場合、その URL ス" +"キームのデフォルトのポートが使用されます。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:204 +msgid "" +"The path portion of the target URL must match a prefix of the request URL " +"path" +msgstr "" +"ターゲット URL のパス部分がリクエスト URL のパスの先頭と一致すること。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:207 +msgid "" +"If Traffic Server finds a match, then it translates the request URL into " +"the replacement URL listed in the map rule: it sets the host and path of " +"the request URL to match the replacement URL. If the URL contains path " +"prefixes, then Traffic Server removes the prefix of the path that matches " +"the target URL path and substitutes it with the path from the replacement " +"URL. If two mappings match a request URL, then Traffic Server applies the " +"first mapping listed in the :file:`remap.config` file." +msgstr "" +"Traffic Server がマッチするものを見つけた場合、リクエスト URL をマップルール" +"の置換 URL に変換します。リクエスト URL のホストとパスを置換 URL に一致する" +"ようにセットします。もし URL がパスのプレフィックスを持っている場合、" +"Traffic Server はターゲット URL のパスからプレフィックスを取り除き、置換 " +"URL のパス部分と置き換えます。もしリクエスト URL にマッチするものが2つあった" +"場合、Traffic Server は :file:`remap.config` ファイル内で先にマッチするほう" +"を適用します。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:216 +msgid "reverse-map rule" +msgstr "リバースマップルール" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:218 +msgid "" +"A **reverse-map rule** translates the URL in origin server redirect " +"responses to point to Traffic Server so that clients are **redirected** to " +"Traffic Server instead of accessing an origin server directly. For example, " +"if there is a directory ``/pub`` on an origin server at ``www.molasses." +"com`` and a client sends a request to that origin server for ``/pub``, then " +"the origin server might reply with a redirect by sending the Header " +"``Location: http://www.test.com/pub/`` to let the client know that it was a " +"directory it had requested, not a document (a common use of redirects is to " +"normalize URLs so that clients can bookmark documents properly)." +msgstr "" +"\\ **リバースマップルール**\\ はクライアントがオリジンサーバーに直接アクセス" +"する代わりに Traffic Server に\\ **リダイレクト**\\ されるようにするために、" +"オリジンサーバーのリダイレクトレスポンス内の URL を Traffic Server に向かう" +"ように変換します。例えば、``www.molasses.com`` というオリジンサーバーに ``/" +"pub`` というディレクトリがあり、クライアントがそのオリジンサーバーに ``/" +"pub`` のリクエストを送信すると、オリジンサーバーはリクエストされたものがド" +"キュメントではなくディレクトリであることを知らせるために ``Loacation http://" +"www.test.com/pub/`` ヘッダーによるリダイレクトで応答するかもしれません。(リ" +"ダイレクトの一般的な使われ方はクライアントがドキュメントを正しくブックマーク" +"できるようにする URL の正規化です。) 。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:229 +msgid "" +"Traffic Server uses ``reverse_map`` rules to prevent clients (that receive " +"redirects from origin servers) from bypassing Traffic Server and directly " +"accessing the origin servers. In many cases the client would be hitting a " +"wall because ``realhost.com`` actually does not resolve for the client. (E." +"g.: Because it's running on a port shielded by a firewall, or because it's " +"running on a non-routable LAN IP)" +msgstr "" +"Traffic Server は (オリジンサーバーからリダイレクト指示を受けた) クライアン" +"トが Traffic Server をバイパスしてオリジンサーバーに直接アクセスすることを防" +"ぐために ``reverse_map`` ルールを使用します。クライアントが壁にぶつかる多く" +"のケースは ``realhost.com`` が実際にはクライアントには解決できない場合です。" +"(例: ファイアーウォールでポートが塞がれている、到達不可能な LAN の IP で動い" +"ている)" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:236 +msgid "" +"Both map and reverse-map rules consist of a **target** (origin) URL and a " +"**replacement** (destination) URL. In a **map rule**, the target URL points " +"to Traffic Server and the replacement URL specifies where the original " +"content is located. In a **reverse-map rule**, the target URL specifies " +"where the original content is located and the replacement URL points to " +"Traffic Server. Traffic Server stores mapping rules in the ``remap.config`` " +"file located in the Traffic Server ``config`` directory." +msgstr "" +"マップルールとリバースマップルールはどちらも\\ **ターゲット** (オリジン) " +"URL と\\ **置換**\\ (宛先) URL で構成されます。\\ **マップルール**\\ では、" +"ターゲット URL は Traffic Server を指し、置換 URL オリジナルコンテントがある" +"場所を指しています。\\ **リバースマップルール**\\ では、ターゲット URL はオ" +"リジナルコンテントがある場所を指し、置換 URL は Traffic Server を指していま" +"す。 Traffic Server はマッピングルールを Traffic Server の ``config`` ディレ" +"クトリにある ``remap.config`` に保存します。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:246 +msgid "Creating Mapping Rules for HTTP Requests" +msgstr "HTTP リクエスト用マッピングルールの作成" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:248 +msgid "To create mapping rules" +msgstr "マッピングルールを作成するには" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:250 +msgid "Enter the map and reverse-map rules into the :file:`remap.config` file" +msgstr "" +":file:`remap.config` ファイルにマップルールとリバースマップルールを入力して" +"ください。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:251 +#: ../../admin/reverse-proxy-http-redirects.en.rst:263 +#: ../../admin/reverse-proxy-http-redirects.en.rst:306 +msgid "" +"Run the command :option:`traffic_line -x` to apply the configuration " +"changes." +msgstr "" +"設定の変更を適用するために :option:`traffic_line -x` コマンドを実行してくだ" +"さい。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:255 +msgid "Enabling HTTP Reverse Proxy" +msgstr "HTTP リバースプロキシーの有効化" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:257 +msgid "To enable HTTP reverse proxy, follow the steps below." +msgstr "HTTP リバースプロキシーを有効にするには次のステップに従ってください。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:259 +msgid "Edit the following variable in :file:`records.config`" +msgstr ":file:`records.config` にある次の変数を編集してください。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:261 +msgid ":ts:cv:`proxy.config.reverse_proxy.enabled`" +msgstr ":ts:cv:`proxy.config.reverse_proxy.enabled`" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:267 +msgid "Setting Optional HTTP Reverse Proxy Options" +msgstr "省略可能な HTTP リバースプロキシーオプションの設定" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:269 +msgid "" +"Traffic Server provides several reverse proxy configuration options in :" +"file:`records.config` that enable you to:" +msgstr "" +"Traffic Server は :file:`records.config` でいくつかのリバースプロキシー設定" +"オプションを提供し次のことを可能にします。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:272 +msgid "" +"Configure Traffic Server to retain the client host header information in a " +"request during translation (:ts:cv:`proxy.config.url_remap." +"pristine_host_hdr`)" +msgstr "" +"Traffic Server がリクエストを変換する際にホストヘッダーの情報を維持するよう" +"に設定する (:ts:cv:`proxy.config.url_remap.pristine_host_hdr`)" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:275 +msgid "" +"Configure Traffic Server to serve requests only to the origin servers " +"listed in the mapping rules. As a result, requests to origin servers not " +"listed in the mapping rules are not served. (:ts:cv:`proxy.config.url_remap." +"remap_required`)" +msgstr "" +"Traffic Server がマッピングルールのリストに存在するオリジンサーバーへのリク" +"エストのみに応えるように設定する。結果として、リストに存在しないオリジンサー" +"バーへのリクエストは処理されません。(:ts:cv:`proxy.config.url_remap." +"remap_required`)" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:278 +msgid "" +"Specify an alternate URL to which incoming requests from older clients (i." +"e., ones that do not provide ``Host`` headers) are directed (:ts:cv:`proxy." +"config.header.parse.no_host_url_redirect`)" +msgstr "" +"古めのクライアントから届くリクエスト (例 ``Host`` ヘッダーを含まないもの) の" +"リダイレクト先となる代替 URL を指定する(:ts:cv:`proxy.config.header.parse." +"no_host_url_redirect`)" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:282 +msgid "" +"Don't forget to run the command :option:`traffic_line -x` to apply the " +"configuration changes." +msgstr "" +"設定の変更を適用するために :option:`traffic_line -x` コマンドを実行するのを" +"忘れないでください。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:286 +msgid "Redirecting HTTP Requests" +msgstr "HTTP リクエストのリダイレクト" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:288 +msgid "" +"You can configure Traffic Server to redirect HTTP requests without having " +"to contact any origin servers. For example, if you redirect all requests " +"for ``http://www.ultraseek.com`` to ``http://www.server1.com/products/" +"portal/search/``, then all HTTP requests for ``www.ultraseek.com`` go " +"directly to ``www.server1.com/products/portal/search``." +msgstr "" +"Traffic Server をどのオリジンサーバーにもコンタクトさせることなく HTTP リク" +"エストをリダイレクトするように設定できます。例えば、``http://www.ultraseek." +"com`` へのすべてのリクエストを```http://www.server1.com/products/portal/" +"search/`` にリダイレクトする場合はすべての ``www.ultraseek.com`` への HTTP " +"リクエストは直接 ``www.server1.com/products/portal/search`` に向かいます。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:295 +msgid "" +"You can configure Traffic Server to perform permanent or temporary " +"redirects. **Permanent redirects** notify the browser of the URL change (by " +"returning the HTTP status code **``301``**) so that the browser can update " +"bookmarks. **Temporary redirects** notify the browser of the URL change for " +"the current request only (by returning the HTTP status code **``307``** )." +msgstr "" +"Traffic Server を恒久的または一時的なリダイレクトを行うように設定できま" +"す。\\ **恒久的なリダイレクト**\\ はブラウザーがブックマークを更新できるよう" +"にURL の変更を(HTTP ステータスコード **``301``** を返すことで) ブラウザーに" +"通知します。\\ **一時的なリダイレクト**\\ は今回のリクエストに限った URL の" +"変更を(HTTP ステータスコード **``307``** を返すことで)ブラウザーに通知しま" +"す。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:302 +msgid "To set redirect rules" +msgstr "リダイレクトルールをセットするには" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:304 +msgid "" +"For each redirect you want to set enter a mapping rule in the :file:`remap." +"config` file" +msgstr "" +"各リダイレクトごとに :file:`remap.config` ファイルにマッピングルールを入力し" +"てください。" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:310 +msgid "Example" +msgstr "例" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:312 +msgid "" +"The following permanently redirects all HTTP requests for ``www.server1." +"com`` to ``www.server2.com``: ::" +msgstr "" +"次の設定は ``www.server1.com`` へのすべての HTTP リクエストを恒久的に ``www." +"server2.com`` へリダイレクトします。 ::" diff --git a/doc/locale/ja/LC_MESSAGES/admin/security-options.en.po b/doc/locale/ja/LC_MESSAGES/admin/security-options.en.po new file mode 100644 index 00000000000..9aa80c307a9 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/security-options.en.po @@ -0,0 +1,482 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/security-options.en.rst:4 +msgid "Security Options" +msgstr "セキュリティオプション" + +#: ../../admin/security-options.en.rst:23 +msgid "Traffic Server provides a number of security features." +msgstr "Traffic Server はいくつものセキュリティ機能を提供します。" + +#: ../../admin/security-options.en.rst:28 +msgid "Controlling Client Access to the Proxy Cache" +msgstr "クライアントからプロキシーキャッシュへのアクセスの制御" + +#: ../../admin/security-options.en.rst:30 +msgid "" +"You can configure Traffic Server to allow only certain clients to use the " +"proxy cache by editing a configuration file." +msgstr "" +"設定ファイルを編集することで、信頼できるクライアントのみにプロキシーキャッ" +"シュの使用を許すように Traffic Server を設定することができます。" + +#: ../../admin/security-options.en.rst:33 +msgid "" +"Add a line in :file:`ip_allow.config` for each IP address or range of IP " +"addresses allowed to access Traffic Server." +msgstr "" +":file:`ip_allow.config` に Traffic Server へのアクセスを許す個々の IP アドレ" +"スもしくは IP アドレスの範囲を 1 行書き足してください。" + +#: ../../admin/security-options.en.rst:35 +#: ../../admin/security-options.en.rst:63 +msgid "" +"Run the command :option:`traffic_line -x` to apply the configuration " +"changes." +msgstr ":option:`traffic_line -x` を実行して設定の変更を適用してください。" + +#: ../../admin/security-options.en.rst:41 +msgid "Configuring DNS Server Selection (Split DNS)" +msgstr "DNS サーバー選択 (Split DNS) の設定" + +#: ../../admin/security-options.en.rst:43 +msgid "" +"The **Split DNS** option enables you to configure Traffic Server to use " +"multiple DNS servers, as dictated by your security requirements. For " +"example, you might configure Traffic Server to use one set of DNS servers " +"to resolve hostnames on your internal network, while allowing DNS servers " +"outside the firewall to resolve hosts on the Internet. This maintains the " +"security of your intranet, while continuing to provide direct access to " +"sites outside your organization." +msgstr "" +"**Split DNS** オプションはセキュリティ要件に規定されたとおりに Traffic " +"Server が複数の DNS サーバーを使用するように設定することを可能にします。例え" +"ば、Traffic Server が内部ネットワークのホスト名を解決するために 1 組の DNS " +"サーバーを使用する一方で、ファイアーウォールの外にある DNS サーバーにはイン" +"ターネット上のホストの解決を許すように設定してもよいでしょう。これはイントラ" +"ネットのセキュリティを維持すると同時に、組織外のサイトへの直接アクセスも提供" +"し続けます。" + +#: ../../admin/security-options.en.rst:51 +msgid "To configure Split DNS, you must do the following:" +msgstr "Split DNS を設定するには次のことをしなければなりません" + +#: ../../admin/security-options.en.rst:53 +msgid "" +"Specify the rules for performing DNS server selection based on the " +"destination domain, the destination host, or a URL regular expression." +msgstr "" +"DNS サーバーが宛先ドメイン、宛先ホストもしくは URL の正規表現をもとに動作す" +"るためのルールを指定する" + +#: ../../admin/security-options.en.rst:56 +msgid "Enable the **Split DNS** option." +msgstr "**Split DNS** オプションを有効化する" + +#: ../../admin/security-options.en.rst:58 +msgid "To do this, we" +msgstr "これを行うためには" + +#: ../../admin/security-options.en.rst:60 +msgid "Add rules to :file:`splitdns.config`." +msgstr ":file:`splitdns.config` にルールを追加してください。" + +#: ../../admin/security-options.en.rst:61 +msgid "" +"In :file:`records.config` set the variable :ts:cv:`proxy.config.dns." +"splitDNS.enabled` to ``1`` to enable split DNS." +msgstr "" +"Split DNS を有効にするために :file:`records.config` の:ts:cv:`proxy.config." +"dns.splitDNS.enabled` 変数を ``1`` に設定してください。" + +#: ../../admin/security-options.en.rst:69 +msgid "Using SSL Termination" +msgstr "SSL ターミネーションの使用" + +#: ../../admin/security-options.en.rst:71 +msgid "" +"The Traffic Server **SSL termination** option enables you to secure " +"connections in reverse proxy mode between a client and a Traffic Server and/" +"or Traffic Server and an origin server." +msgstr "" +"Traffic Server の **SSL ターミネーション**\\ オプションはリバースプロキシー" +"モードでクライアントと Traffic Server の間および/もしくは Traffic Server と" +"オリジンサーバーの間の接続を安全にすることを可能にします。" + +#: ../../admin/security-options.en.rst:75 +msgid "" +"The following sections describe how to enable and configure the SSL " +"termination option." +msgstr "" +"次の章では SSL ターミネーションをどうのように設定し有効化するかを説明しま" +"す。" + +#: ../../admin/security-options.en.rst:78 +msgid "" +"Enable and configure SSL termination for client/Traffic Server " +"connections: :ref:`client-and-traffic-server-connections`" +msgstr "" +"クライアントと Traffic Server 間の接続で SSL ターミネーションを設定し有効化" +"するには :ref:`client-and-traffic-server-connections` を参照してください。" + +#: ../../admin/security-options.en.rst:80 +msgid "" +"Enable and configure SSL termination for Traffic Server/origin server " +"connections: :ref:`traffic-server-and-origin-server-connections`" +msgstr "" +"Traffic Server とオリジンサーバー間の接続で SSL ターミネーションを設定し有効" +"化するには :ref:`traffic-server-and-origin-server-connections` を参照してく" +"ださい。" + +#: ../../admin/security-options.en.rst:82 +msgid "" +"Enable and configure SSL termination for both client/Traffic Server and " +"Traffic Server/origin server connections: :ref:`client-and-traffic-server-" +"connections` :ref:`traffic-server-and-origin-server-connections`, " +"respectively." +msgstr "" +"クライアントと Traffic Server 間の接続、Traffic Server とオリジンサーバー間" +"の接続の両方で SSL ターミネーションを設定し有効化するには :ref:`client-and-" +"traffic-server-connections` と :ref:`traffic-server-and-origin-server-" +"connections` をそれぞれ参照してください。" + +#: ../../admin/security-options.en.rst:89 +msgid "Client and Traffic Server Connections" +msgstr "クライアントと Traffic Server の接続" + +#: ../../admin/security-options.en.rst:91 +msgid "" +"The figure below illustrates communication between a client and Traffic " +"Server (and between Traffic Server and an origin server) when the SSL " +"termination option is enabled & configured for **client/Traffic Server " +"connections only**." +msgstr "" +"以下の図は\\ **クライアントと Traffic Server の間の接続だけ**\\ で SSL ター" +"ミネーションオプションを有効化し、設定した際のクライアントと Traffic Server " +"の通信 (Traffic Server とオリジンサーバー間も含む) を説明します。" + +#: ../../admin/security-options.en.rst:100 +msgid "Client and Traffic Server communication using SSL termination" +msgstr "SSL ターミネーションを使用したクライアントと Traffic Server の通信" + +#: ../../admin/security-options.en.rst:102 +#: ../../admin/security-options.en.rst:167 +msgid "The figure above depicts the following:" +msgstr "上の図は次のことを説明しています" + +#: ../../admin/security-options.en.rst:104 +msgid "" +"The client sends an HTTPS request for content. Traffic Server receives the " +"request and performs the SSL 'handshake' to authenticate the client " +"(depending on the authentication options configured) and determine the " +"encryption method that will be used. If the client is allowed access, then " +"Traffic Server checks its cache for the requested content." +msgstr "" +"クライアントがコンテンツのために HTTPS リクエストを送信します。Traffic " +"Server はリクエストを受け取り、クライアントの認証 (認証オプションの設定によ" +"ります) と使用される暗号化方式の決定をするために SSL 'ハンドシェイク' を行い" +"ます。クライアントがアクセスを許されると、Traffic Server はリクエストされた" +"コンテンツのキャッシュを確認します。" + +#: ../../admin/security-options.en.rst:106 +msgid "" +"If the request is a cache hit and the content is fresh, then Traffic Server " +"encrypts the content and sends it to the client. The client decrypts the " +"content (using the method determined during the handshake) and displays it." +msgstr "" +"リクエストがキャッシュヒットかつコンテンツが新鮮な場合、Traffic Server はコ" +"ンテンツを暗号化しクライアントに送信します。クライアントはコンテンツを (ハン" +"ドシェイクの間に決定した方式で) 復号化し表示します。" + +#: ../../admin/security-options.en.rst:108 +msgid "" +"If the request is a cache miss or cached content is stale, then Traffic " +"Server communicates with the origin server via HTTP and obtains a plain " +"text version of the content. Traffic Server saves the plain text version of " +"the content in its cache, encrypts the content, and sends it to the client. " +"The client decrypts and displays the content." +msgstr "" +"リクエストがキャッシュミスもしくはキャッシュされたコンテンツが新鮮でない場" +"合、Traffic Server はオリジンサーバーと HTTP で通信し平文のコンテンツを取得" +"します。Traffic Server は平文のコンテンツをキャッシュに保存し、コンテンツを" +"暗号化し、クライアントに送信します。クライアントはコンテンツを復号化し表示し" +"ます。" + +#: ../../admin/security-options.en.rst:110 +msgid "" +"To configure Traffic Server to use the SSL termination option for client/" +"Traffic Server connections, you must do the following:" +msgstr "" +"Traffic Server がクライアントと Traffic Server の間の接続で SSL ターミネー" +"ションオプションを使用するように設定するには、次のことを行わなければなりませ" +"ん" + +#: ../../admin/security-options.en.rst:113 +msgid "" +"Obtain and install an SSL server certificate from a recognized certificate " +"authority. The SSL server certificate contains information that enables the " +"client to authenticate Traffic Server and exchange encryption keys." +msgstr "" +"SSL サーバー証明書を認められた認証局から取得しインストールする。SSL サーバー" +"証明書はクライアントが Traffic Server を認証し暗号化鍵を交換することを可能に" +"する情報を含んでいます。" + +#: ../../admin/security-options.en.rst:117 +#: ../../admin/security-options.en.rst:194 +msgid "Configure SSL termination options:" +msgstr "SSL ターミネーションオプションを設定する" + +#: ../../admin/security-options.en.rst:119 +msgid "" +"Set the port number used for SSL communication using :ts:cv:`proxy.config." +"http.server_ports`." +msgstr "" +":ts:cv:`proxy.config.http.server_ports` で SSL 通信に使用されるポート番号を" +"設定する" + +#: ../../admin/security-options.en.rst:122 +msgid "" +"(Optional) Configure the use of client certificates: Client certificates " +"are located on the client. If you configure Traffic Server to require " +"client certificates, then Traffic Server verifies the client certificate " +"during the SSL handshake that authenticates the client. If you configure " +"Traffic Server to *not* require client certificates, then access to Traffic " +"Server is managed through other Traffic Server options that have been set " +"(such as rules in :file:`ip_allow.config`)." +msgstr "" +"(任意) クライアント証明書の使用を設定する。クライアント証明書はクライアント" +"上に置かれます。Traffic Server がクライアント証明書を必要とするように設定す" +"ると Traffic Server は クライアントを認証する SSL ハンドシェイクの中でクライ" +"アント証明書を検証します。Traffic Server がクライアント証明書を必要と\\ *し" +"ない*\\ ように設定すると、Traffic Server へのアクセスは (:file:`ip_allow." +"config` のルールなどの) 他に設定されている Traffic Server オプションによって" +"管理されます。" + +#: ../../admin/security-options.en.rst:130 +msgid "" +"(Optional) Configure the use of Certification Authorities (CAs). CAs add " +"security by verifying the identity of the person requesting a certificate." +msgstr "" +"(任意) 認証局 (CA) の使用を設定する。認証局は証明を要求した人の同一性を検証" +"することでセキュリティを追加します。" + +#: ../../admin/security-options.en.rst:134 +msgid "In order to accomplish this, we" +msgstr "これを実現するためには" + +#: ../../admin/security-options.en.rst:136 +msgid "" +"Edit the following variables in the :ref:`records-config-ssl-termination` " +"section of :file:`records.config`" +msgstr "" +":file:`records.config` の :ref:`records-config-ssl-termination` の章にある次" +"の変数を編集してください。" + +#: ../../admin/security-options.en.rst:139 +#: ../../admin/security-options.en.rst:217 +msgid ":ts:cv:`proxy.config.http.server_ports`" +msgstr ":ts:cv:`proxy.config.http.server_ports`" + +#: ../../admin/security-options.en.rst:140 +msgid ":ts:cv:`proxy.config.ssl.client.certification_level`" +msgstr ":ts:cv:`proxy.config.ssl.client.certification_level`" + +#: ../../admin/security-options.en.rst:141 +msgid ":ts:cv:`proxy.config.ssl.server.cert.path`" +msgstr ":ts:cv:`proxy.config.ssl.server.cert.path`" + +#: ../../admin/security-options.en.rst:142 +msgid ":ts:cv:`proxy.config.ssl.server.private_key.path`" +msgstr ":ts:cv:`proxy.config.ssl.server.private_key.path`" + +#: ../../admin/security-options.en.rst:143 +msgid ":ts:cv:`proxy.config.ssl.CA.cert.path`" +msgstr ":ts:cv:`proxy.config.ssl.CA.cert.path`" + +#: ../../admin/security-options.en.rst:145 +#: ../../admin/security-options.en.rst:226 +msgid "" +"Run the command :option:`traffic_line -L` to restart Traffic Server on the " +"local node or :option:`traffic_line -M` to restart Traffic Server on all " +"the nodes in a cluster." +msgstr "" +"ローカルノード上の Traffic Server をリスタートするために :option:" +"`traffic_line -L` を、もしくはクラスター内のすべての Traffic Server をリス" +"タートするためには :option:`traffic_line -M` を実行してください。" + +#: ../../admin/security-options.en.rst:155 +msgid "Traffic Server and Origin Server Connections" +msgstr "Traffic Server とオリジンサーバーの接続" + +#: ../../admin/security-options.en.rst:157 +msgid "" +"The figure below illustrates communication between Traffic Server and an " +"origin server when the SSL termination option is enabled for **Traffic " +"Server/origin server connections**." +msgstr "" +"以下の図は SSL ターミネーションオプションを \\ **Traffic Server とオリジン" +"サーバーの間の接続**\\ で有効化した際の Traffic Server とオリジンサーバーの" +"通信を説明します。" + +#: ../../admin/security-options.en.rst:165 +msgid "Traffic Server and origin server communication using SSL termination" +msgstr "SSL ターミネーションを使用したTraffic Server とオリジンサーバーの通信" + +#: ../../admin/security-options.en.rst:169 +msgid "" +"**Step 1:** If a client request is a cache miss or is stale, then Traffic " +"Server sends an HTTPS request for the content to the origin server. The " +"origin server receives the request and performs the SSL handshake to " +"authenticate Traffic Server and determine the encryption method to be used." +msgstr "" +"**ステップ 1:** クライアントのリクエストがキャッシュミスもしくは新鮮でない場" +"合、Traffic Server は コンテンツのための HTTPS リクエストをオリジンサーバー" +"に送信します。オリジンサーバーはリクエストを受け取り、Traffic Server の認証" +"と使用される暗号化方式の決定をするために SSL ハンドシェイク を行います。" + +#: ../../admin/security-options.en.rst:175 +msgid "" +"**Step 2:** If Traffic Server is allowed access, then the origin server " +"encrypts the content and sends it to Traffic Server, where it is decrypted " +"(using the method determined during the handshake). A plain text version of " +"the content is saved in the cache." +msgstr "" +"**ステップ 2:** Traffic Server がアクセスを許されると、オリジンサーバーはコ" +"ンテンツを暗号化して Traffic Server に送信し、そこで (ハンドシェイクの中で決" +"定した方式を使用して) 復号化されます。平文のコンテンツはキャッシュに保存され" +"ます。" + +#: ../../admin/security-options.en.rst:180 +msgid "" +"**Step 3:** If SSL termination is enabled for client /Traffic Server " +"connections, then Traffic Server re-encrypts the content and sends it to " +"the client via HTTPS, where it is decrypted and displayed. If SSL " +"termination is not enabled for client/Traffic Server connections, then " +"Traffic Server sends the plain text version of the content to the client " +"via HTTP." +msgstr "" +"**ステップ 3:** SSL ターミネーションがクライアントと Traffic Server の間で有" +"効化されている場合、Traffic Server はコンテンツを再暗号化して HTTPS でクライ" +"アントに送信し、そこで復号化され表示されます。SSL ターミネーションがクライア" +"ントと Traffic Server の間で有効化されていない場合、Traffic Server は平文の" +"コンテンツを HTTP でクライアントに送信します。" + +#: ../../admin/security-options.en.rst:187 +msgid "" +"To configure Traffic Server to use the SSL termination option for Traffic " +"Server and origin server connections, you must do the following:" +msgstr "" +"Traffic Server が Traffic Server とオリジンサーバーの間で SSL ターミネーショ" +"ンを使用するように設定するには、次のことを行わなければなりません" + +#: ../../admin/security-options.en.rst:190 +msgid "" +"Obtain and install an SSL client certificate from a recognized certificate " +"authority. The SSL client certificate contains information that allows the " +"origin server to authenticate Traffic Server (the client certificate is " +"optional)." +msgstr "" +"SSL クライアント証明書を認められた認証局から取得しインストールする。SSL クラ" +"イアント証明書はオリジンサーバーが Traffic Server を認証することを可能にする" +"情報を含んでいます (クライアント証明書は任意です) 。" + +#: ../../admin/security-options.en.rst:195 +msgid "Enable the SSL termination option." +msgstr "SSL ターミネーションオプションを有効化する" + +#: ../../admin/security-options.en.rst:197 +msgid "Set the port number used for SSL communication." +msgstr "SSL 通信に使用されるポート番号を設定する。" + +#: ../../admin/security-options.en.rst:198 +msgid "" +"Specify the filename and location of the SSL client certificate (if you " +"choose to use a client certificate)." +msgstr "" +"SSL クライアント証明書のファイル名と場所を指定する (クライアント証明書を使用" +"することを選択する場合) 。" + +#: ../../admin/security-options.en.rst:200 +msgid "" +"Specify the filename and location of the Traffic Server private key (if the " +"private key is not located in the client certificate file). Traffic Server " +"uses its private key during the SSL handshake to decrypt the session " +"encryption keys. The private key must be stored and protected against theft." +msgstr "" +"Traffic Server の秘密鍵のファイル名と場所を指定する (秘密鍵がクライアント証" +"明書ファイル内に無い場合) 。Traffic Server はセッション暗号化鍵を復号化する" +"ために SSL ハンドシェイクの中で自身の秘密鍵を使用します。秘密鍵は盗難から保" +"護されて置かれていなければなりません。" + +#: ../../admin/security-options.en.rst:205 +msgid "" +"Configure the use of CAs. CAs allow the Traffic Server that's acting as a " +"client to verify the identity of the server with which it is communicating, " +"thereby enabling exchange of encryption keys." +msgstr "" +"CA の使用を設定する。CA は 通信しているサーバーの同一性を検証するために " +"Traffic Server がクライアントとして振る舞うことを許し、それによって暗号化鍵" +"の交換を可能にしています。" + +#: ../../admin/security-options.en.rst:209 +msgid "In order to accomplish this, we:" +msgstr "これを実現するためには" + +#: ../../admin/security-options.en.rst:213 +msgid "" +"Edit the following variables in the :ref:`records-config-ssl-termination` " +"section of :file:`records.config`:" +msgstr "" +":file:`records.config`: の :ref:`records-config-ssl-termination` の章にある" +"次の変数を編集してください。" + +#: ../../admin/security-options.en.rst:216 +msgid ":ts:cv:`proxy.config.ssl.auth.enabled`" +msgstr ":ts:cv:`proxy.config.ssl.auth.enabled`" + +#: ../../admin/security-options.en.rst:218 +msgid ":ts:cv:`proxy.config.ssl.client.verify.server`" +msgstr ":ts:cv:`proxy.config.ssl.client.verify.server`" + +#: ../../admin/security-options.en.rst:219 +msgid ":ts:cv:`proxy.config.ssl.client.cert.filename`" +msgstr ":ts:cv:`proxy.config.ssl.client.cert.filename`" + +#: ../../admin/security-options.en.rst:220 +msgid ":ts:cv:`proxy.config.ssl.client.cert.path`" +msgstr ":ts:cv:`proxy.config.ssl.client.cert.path`" + +#: ../../admin/security-options.en.rst:221 +msgid ":ts:cv:`proxy.config.ssl.client.private_key.filename`" +msgstr ":ts:cv:`proxy.config.ssl.client.private_key.filename`" + +#: ../../admin/security-options.en.rst:222 +msgid ":ts:cv:`proxy.config.ssl.client.private_key.path`" +msgstr ":ts:cv:`proxy.config.ssl.client.private_key.path`" + +#: ../../admin/security-options.en.rst:223 +msgid ":ts:cv:`proxy.config.ssl.client.CA.cert.filename`" +msgstr ":ts:cv:`proxy.config.ssl.client.CA.cert.filename`" + +#: ../../admin/security-options.en.rst:224 +msgid ":ts:cv:`proxy.config.ssl.client.CA.cert.path`" +msgstr ":ts:cv:`proxy.config.ssl.client.CA.cert.path`" + +#: ../../admin/security-options.en.rst:120 +msgid "" +"Edit :file:`ssl_multicert.config` to specify the filename and location of " +"the SSL certificates and private keys." +msgstr "" +"SSL 証明書と秘密鍵のファイル名と場所を指定するために :file:`ssl_multicert." +"config` を編集する" diff --git a/doc/locale/ja/LC_MESSAGES/admin/traffic-server-error-messages.en.po b/doc/locale/ja/LC_MESSAGES/admin/traffic-server-error-messages.en.po new file mode 100644 index 00000000000..9180990b782 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/traffic-server-error-messages.en.po @@ -0,0 +1,857 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/traffic-server-error-messages.en.rst:4 +msgid "Error Messages" +msgstr "エラーメッセージ" + +#: ../../admin/traffic-server-error-messages.en.rst:27 +msgid "Traffic Server Error Messages" +msgstr "Traffic Server のエラーメッセージ" + +#: ../../admin/traffic-server-error-messages.en.rst:29 +msgid "" +"The following table lists messages that can appear in system log files. " +"This list is not exhaustive; it simply describes common warning messages " +"that can occur and which might require your attention." +msgstr "" +"次の表はシステムログファイルに出てくるメッセージを一覧表示しています。この一" +"覧は網羅的なものではなく、単に一般的な発生しうる注目を要するであろう警告メッ" +"セージを説明しているだけです。" + +#: ../../admin/traffic-server-error-messages.en.rst:34 +msgid "Traffic Server Process Fatal" +msgstr "Traffic Server プロセスの致命的状況" + +#: ../../admin/traffic-server-error-messages.en.rst:38 +msgid "``Accept port is not between 1 and 65535. Please check configuration``" +msgstr "" +"``Accept port is not between 1 and 65535. Please check configuration``" + +#: ../../admin/traffic-server-error-messages.en.rst:37 +msgid "" +"The port specified in the :file:`records.config` file that accepts incoming " +"HTTP requests is not valid." +msgstr "" +":file:`records.config` ファイルに指定されている入ってきた HTTP リクエストを" +"受け入れるポートが妥当ではありません。" + +#: ../../admin/traffic-server-error-messages.en.rst:43 +msgid "``Self loop is detected in parent proxy configuration``" +msgstr "``Self loop is detected in parent proxy configuration``" + +#: ../../admin/traffic-server-error-messages.en.rst:41 +msgid "" +"The name and port of the parent proxy match that of Traffic Server. This " +"creates a loop when Traffic Server attempts to send the request to the " +"parent proxy." +msgstr "" +"親プロキシーの名前とポートが Traffic Server のものと一致しています。これは " +"Traffic Server が親プロキシーにリクエストを送信しようとする際にループを引き" +"起こします。" + +#: ../../admin/traffic-server-error-messages.en.rst:46 +msgid "Traffic Server Warnings" +msgstr "Traffic Server の警告" + +#: ../../admin/traffic-server-error-messages.en.rst:49 +msgid "`` error: error_number``" +msgstr "`` error: error_number``" + +#: ../../admin/traffic-server-error-messages.en.rst:49 +msgid "Generic logging error." +msgstr "一般的なロギングエラーです。" + +#: ../../admin/traffic-server-error-messages.en.rst:52 +msgid "" +"``Bad cluster major version range for node " +"connect failed``" +msgstr "" +"``Bad cluster major version range for node " +"connect failed``" + +#: ../../admin/traffic-server-error-messages.en.rst:52 +msgid "Incompatible software versions causing a problem." +msgstr "互換性の無いソフトウェアのバージョンが問題を引き起こしています。" + +#: ../../admin/traffic-server-error-messages.en.rst:56 +msgid "``Connect by disallowed client , closing``" +msgstr "``Connect by disallowed client , closing``" + +#: ../../admin/traffic-server-error-messages.en.rst:55 +msgid "" +"The specified client is not allowed to connect to Traffic Server; the " +"client IP address is not listed in the ``ip_allow.config`` file." +msgstr "" +"指定されたクライアントは Traffic Server へのアクセスを許可されていません。ク" +"ライアントの IP アドレスが ``ip_allow.config`` ファイル内に記載されていませ" +"ん。" + +#: ../../admin/traffic-server-error-messages.en.rst:59 +msgid "``Could not rename log to ``" +msgstr "``Could not rename log to ``" + +#: ../../admin/traffic-server-error-messages.en.rst:59 +msgid "System error when renaming log file during roll." +msgstr "ロール中にログファイルをリネームしようとした際のシステムエラーです。" + +#: ../../admin/traffic-server-error-messages.en.rst:62 +msgid "``Did of backup; still to do ``" +msgstr "``Did of backup; still to do ``" + +#: ../../admin/traffic-server-error-messages.en.rst:62 +msgid "Congestion is approaching." +msgstr "輻輳が発生しそうです。" + +#: ../../admin/traffic-server-error-messages.en.rst:65 +msgid "" +"``Different clustering minor versions for node continuing``" +msgstr "" +"``Different clustering minor versions for node continuing``" + +#: ../../admin/traffic-server-error-messages.en.rst:65 +msgid "Incompatible software versions are causing a problem." +msgstr "互換性の無いソフトウェアのバージョンが問題を引き起こしています。" + +#: ../../admin/traffic-server-error-messages.en.rst:69 +msgid "``Log format symbol not found``" +msgstr "``Log format symbol not found``" + +#: ../../admin/traffic-server-error-messages.en.rst:68 +msgid "" +"Custom log format references a field symbol that does not exist. Refer to :" +"ref:`event-logging-formats`." +msgstr "" +"カスタムログのフォーマットが存在しないフィールドを参照しています。 :ref:" +"`event-logging-formats` を参照してください。" + +#: ../../admin/traffic-server-error-messages.en.rst:72 +msgid "``Missing field for field marker``" +msgstr "``Missing field for field marker``" + +#: ../../admin/traffic-server-error-messages.en.rst:72 +msgid "Error reading a log buffer." +msgstr "ログバッファーを読み込み中のエラーです。" + +#: ../../admin/traffic-server-error-messages.en.rst:75 +msgid "``Unable to open log file , errno=``" +msgstr "``Unable to open log file , errno=``" + +#: ../../admin/traffic-server-error-messages.en.rst:75 +msgid "Cannot open the log file." +msgstr "ログファイルが開けません。" + +#: ../../admin/traffic-server-error-messages.en.rst:79 +msgid "``Error accessing disk ``" +msgstr "``Error accessing disk ``" + +#: ../../admin/traffic-server-error-messages.en.rst:78 +msgid "" +"Traffic Server might have a cache read problem. You might need to replace " +"the disk." +msgstr "" +"Traffic Server がキャッシュの読み込みに問題を抱えているかもしれません。ディ" +"スクを交換する必要があるかもしれません。" + +#: ../../admin/traffic-server-error-messages.en.rst:84 +msgid "``Too many errors accessing disk : declaring disk bad``" +msgstr "``Too many errors accessing disk : declaring disk bad``" + +#: ../../admin/traffic-server-error-messages.en.rst:82 +msgid "" +"Traffic Server is not using the cache disk because it encountered too many " +"errors. The disk might be corrupt and might have to be replaced." +msgstr "" +"Traffic Server は過度なエラーに遭遇したためキャッシュディスクを使用していま" +"せん。ディスクが壊れているかもしれないので交換する必要があるかもしれません。" + +#: ../../admin/traffic-server-error-messages.en.rst:89 +msgid "``No cache disks specified in storage.config file: cache disabled``" +msgstr "``No cache disks specified in storage.config file: cache disabled``" + +#: ../../admin/traffic-server-error-messages.en.rst:87 +msgid "" +"The Traffic Server ``storage.config`` file does not list any cache disks; " +"Traffic Server is running in proxy-only mode. You must add the disks you " +"want to use for the cache to :file:`storage.config`." +msgstr "" +"Traffic Server の ``storage.config`` ファイルにキャッシュディスクが記載され" +"ていません。Traffic Server はプロキシーモードで動作しています。キャッシュに" +"使用したいディスクを :file:`storage.config` に記載しなくてななりません。" + +#: ../../admin/traffic-server-error-messages.en.rst:92 +msgid "Traffic Server Alarm Messages" +msgstr "Traffic Server の警報メッセージ" + +#: ../../admin/traffic-server-error-messages.en.rst:96 +msgid "``[Rollback::Rollback] Config file is read-only: ``" +msgstr "``[Rollback::Rollback] Config file is read-only: ``" + +#: ../../admin/traffic-server-error-messages.en.rst:95 +#: ../../admin/traffic-server-error-messages.en.rst:103 +msgid "" +"Go to the Traffic Server ``config`` directory and check the indicated file " +"permissions; change if necessary." +msgstr "" +"Traffic Server の ``config`` ディレクトリで指示されたファイルのパーミッショ" +"ンを確認し、必要であれば変更してください。" + +#: ../../admin/traffic-server-error-messages.en.rst:100 +msgid "" +"``[Rollback::Rollback] Unable to read or write config file ``" +msgstr "" +"``[Rollback::Rollback] Unable to read or write config file ``" + +#: ../../admin/traffic-server-error-messages.en.rst:99 +msgid "" +"Go to the Traffic Server ``config`` directory and make sure the indicated " +"file exists. Check permissions and modify if necessary." +msgstr "" +"Traffic Server の ``config`` ディレクトリで指示されたファイルが存在すること" +"を確認してください。パーミッションを確認し、必要であれば変更してください" + +#: ../../admin/traffic-server-error-messages.en.rst:104 +msgid "``[Traffic Manager] Configuration File Update Failed: ``" +msgstr "" +"``[Traffic Manager] Configuration File Update Failed: ``" + +#: ../../admin/traffic-server-error-messages.en.rst:108 +msgid "``[Traffic Manager] Mgmt <==>Proxy conn. closed``" +msgstr "``[Traffic Manager] Mgmt <==>Proxy conn. closed``" + +#: ../../admin/traffic-server-error-messages.en.rst:107 +msgid "" +"An informational message to inform you that the :program:`traffic_server` " +"process is down." +msgstr "" +":program:`traffic_server` プロセスが落ちていることを知らせるための情報提供" +"メッセージです。" + +#: ../../admin/traffic-server-error-messages.en.rst:114 +msgid "``Access logging suspended - configured space allocation exhausted.``" +msgstr "``Access logging suspended - configured space allocation exhausted.``" + +#: ../../admin/traffic-server-error-messages.en.rst:111 +msgid "" +"The space allocated to the event log files is full; you must either " +"increase the space or delete some log files so that access logging to " +"continue. To prevent this error, consider rolling log files more frequently " +"and enabling the autodelete feature." +msgstr "" +"イベントログファイルに割り当てられた領域が満杯です。アクセスのロギングを続け" +"るために領域を増やすかいくつかのログファイルを削除しなければなりません。この" +"エラーを防ぐためには、ログファイルをより頻繁にロールし、自動削除機能を有効化" +"することを検討してください。" + +#: ../../admin/traffic-server-error-messages.en.rst:120 +msgid "``Access logging suspended - no more space on the logging partition.``" +msgstr "" +"``Access logging suspended - no more space on the logging partition.``" + +#: ../../admin/traffic-server-error-messages.en.rst:117 +msgid "" +"The entire partition containing the event logs is full; you must delete or " +"move some log files to enable access logging to continue. To prevent this " +"error, consider rolling log files more frequently and enabling the " +"autodelete feature." +msgstr "" +"イベントログを含むパーティション全体が満杯です。アクセスのロギングを続けるた" +"めにいくつかのログファイルを削除もしくは移動しなければなりません。このエラー" +"を防ぐためには、ログファイルをより頻繁にロールし、自動削除機能を有効化するこ" +"とを検討してください。" + +#: ../../admin/traffic-server-error-messages.en.rst:125 +msgid "``Created zero length place holder for config file ``" +msgstr "``Created zero length place holder for config file ``" + +#: ../../admin/traffic-server-error-messages.en.rst:123 +msgid "" +"Go to the Traffic Server ``config`` directory and check the indicated file. " +"If it is indeed zero in length, then use a backup copy of the configuration " +"file." +msgstr "" +"Traffic Server の ``config`` ディレクトリで指示されたファイルを確認してくだ" +"さい。もしたしかに長さがゼロの場合、設定ファイルのバックアップコピーを使用し" +"てください。" + +#: ../../admin/traffic-server-error-messages.en.rst:128 +msgid "``Traffic Server could not open logfile ``" +msgstr "``Traffic Server could not open logfile ``" + +#: ../../admin/traffic-server-error-messages.en.rst:128 +msgid "Check permissions for the indicated file and the logging directory." +msgstr "" +"指示されたファイルとロギングディレクトリのパーミッションを確認してください。" + +#: ../../admin/traffic-server-error-messages.en.rst:132 +msgid "" +"``Traffic Server failed to parse line of the logging config " +"file ``" +msgstr "" +"``Traffic Server failed to parse line of the logging config " +"file ``" + +#: ../../admin/traffic-server-error-messages.en.rst:131 +msgid "" +"Check your custom log configuration file; there could be syntax errors. " +"Refer to :ref:`custom-logging-fields` for correct custom log format fields." +msgstr "" +"カスタムログ設定ファイルを確認してください。シンタックスエラーがあるかもしれ" +"ません。正しいカスタムログのフォーマットフィールドについては :ref:`custom-" +"logging-fields` を参照してください。" + +#: ../../admin/traffic-server-error-messages.en.rst:137 +msgid "" +"``vip_config binary is not setuid root, manager will be unable to enable " +"virtual ip addresses``" +msgstr "" +"``vip_config binary is not setuid root, manager will be unable to enable " +"virtual ip addresses``" + +#: ../../admin/traffic-server-error-messages.en.rst:135 +msgid "" +"The :program:`traffic_manager` process is not able to set virtual IP " +"addresses. You must ``setuid root`` for the ``vip_config`` file in the " +"Traffic Server ``bin`` directory." +msgstr "" +":program:`traffic_manager` プロセスがバーチャル IP アドレス を設定できませ" +"ん。Traffic Server の ``bin`` ディレクトリにある ``vip_config`` ファイルに対" +"して ``setuid root`` しなければなりません。" + +#: ../../admin/traffic-server-error-messages.en.rst:140 +msgid "HTML Messages Sent to Clients" +msgstr "クライアントに送信される HTML メッセージ" + +#: ../../admin/traffic-server-error-messages.en.rst:142 +msgid "" +"Traffic Server returns detailed error messages to browser clients when " +"there are problems with the HTTP transactions requested by the browser. " +"These Traffic Server response messages correspond to standard HTTP response " +"codes, but provide more information. A list of the more frequently-" +"encountered HTTP response codes is provided in :ref:`standard-http-response-" +"messages`. You can customize the Traffic Server response messages, if " +"desired." +msgstr "" +"Traffic Server は ブラウザからリクエストされた HTTP トランザクションに問題が" +"ある場合に、クライアントに詳細なエラーメッセージを返します。これらの " +"Traffice Server のレスポンスメッセージは標準的な HTTP レスポンスコードに対応" +"しますが、より多くの情報を提供します。より頻繁に遭遇する HTTP レスポンスコー" +"ドの一覧は :ref:`standard-http-response-messages` で提供されています。もし望" +"むなら Traffic Server のレスポンスメッセージをカスタマイズすることができま" +"す。" + +#: ../../admin/traffic-server-error-messages.en.rst:149 +msgid "" +"The following table lists the hard-coded Traffic Server HTTP messages, with " +"corresponding HTTP response codes and customizable files." +msgstr "" +"次の表はハードコードされた Traffic Server の HTTP メッセージを、対応する " +"HTTP レスポンスコードとカスタマイズ可能なファイルとともに一覧表示していま" +"す。" + +#: ../../admin/traffic-server-error-messages.en.rst:155 +msgid "``Access Denied``" +msgstr "``Access Denied``" + +#: ../../admin/traffic-server-error-messages.en.rst:153 +msgid "" +"``403`` You are not allowed to access the document at location ``URL``. " +"``access#denied``" +msgstr "" +"``403`` You are not allowed to access the document at location ``URL``. (あ" +"なたは ``URL`` にあるドキュメントへのアクセスが許されていません。) " +"``access#denied``" + +#: ../../admin/traffic-server-error-messages.en.rst:160 +msgid "``Cache Read Error``" +msgstr "``Cache Read Error``" + +#: ../../admin/traffic-server-error-messages.en.rst:158 +msgid "" +"``500`` Error reading from cache; please retry request. ``cache#read_error``" +msgstr "" +"``500`` Error reading from cache; please retry request. (キャッシュ読み込み" +"中のエラーです。リクエストをリトライしてください。) ``cache#read_error``" + +#: ../../admin/traffic-server-error-messages.en.rst:165 +msgid "``Connection Timed Out``" +msgstr "``Connection Timed Out``" + +#: ../../admin/traffic-server-error-messages.en.rst:163 +msgid "" +"``504`` Too much time has elapsed since the server has sent data. " +"``timeout#inactivity``" +msgstr "" +"``504`` Too much time has elapsed since the server has sent data. (サーバー" +"がデータを送信してから時間が経過しすぎました。) ``timeout#inactivity``" + +#: ../../admin/traffic-server-error-messages.en.rst:170 +msgid "``Content Length Required``" +msgstr "``Content Length Required``" + +#: ../../admin/traffic-server-error-messages.en.rst:168 +msgid "" +"``400`` Could not process this request because ``Content-Length`` was not " +"specified. ``request#no_content_length``" +msgstr "" +"``400`` Could not process this request because ``Content-Length`` was not " +"specified. (``Content-Length`` が指定されなかったためリクエストを処理できま" +"せんでした。) ``request#no_content_length``" + +#: ../../admin/traffic-server-error-messages.en.rst:175 +msgid "``Cycle Detected``" +msgstr "``Cycle Detected``" + +#: ../../admin/traffic-server-error-messages.en.rst:173 +msgid "" +"``400`` Your request is prohibited because it would cause an HTTP proxy " +"cycle. ``request#cycle_detected``" +msgstr "" +"``400`` Your request is prohibited because it would cause an HTTP proxy " +"cycle. (リクエストが HTTP プロキシー循環を引き起こすのでリクエストは禁止され" +"ました。) ``request#cycle_detected``" + +#: ../../admin/traffic-server-error-messages.en.rst:180 +msgid "``Forbidden``" +msgstr "``Forbidden``" + +#: ../../admin/traffic-server-error-messages.en.rst:178 +msgid "" +"``403`` ```` is not an allowed port for SSL connections (you " +"have made a request for a secure SSL connection to a forbidden port " +"number). ``access#ssl_forbidden``" +msgstr "" +"``403`` ```` is not an allowed port for SSL connections (you " +"have made a request for a secure SSL connection to a forbidden port " +"number). ``<ポート番号>`` が SSL 接続で許可されていないポートです (禁じられ" +"たポートに SSL 接続のリクエストを行いました) 。``access#ssl_forbidden``" + +#: ../../admin/traffic-server-error-messages.en.rst:190 +#: ../../admin/traffic-server-error-messages.en.rst:198 +msgid "``Host Header Required``" +msgstr "``Host Header Required``" + +#: ../../admin/traffic-server-error-messages.en.rst:183 +msgid "" +"``400`` An attempt was made to transparently proxy your request, but this " +"attempt failed because your browser did not send an HTTP ``Host`` header. " +"Manually configure your browser to use ``http://:`` " +"as the HTTP proxy. Alternatively, end users can upgrade to a browser that " +"supports the HTTP ``Host`` header field. ``interception#no_host``" +msgstr "" +"``400`` An attempt was made to transparently proxy your request, but this " +"attempt failed because your browser did not send an HTTP ``Host`` header. " +"Manually configure your browser to use ``http://:`` " +"as the HTTP proxy. Alternatively, end users can upgrade to a browser that " +"supports the HTTP ``Host`` header field. (リクエストを透過的にプロキシーする" +"よう試みましたが、ブラウザが HTTP ``Host`` ヘッダーを送信しなかったため失敗" +"しました。ブラウザが ``http://<プロキシー名>:<プロキシーポート>`` を HTTP プ" +"ロキシーとして使うように手動で設定していください。もしくは、エンドユーザー" +"が ``Host`` ヘッダーをサポートするブラウザーにアップグレードすることもできま" +"す。) ``interception#no_host``" + +#: ../../admin/traffic-server-error-messages.en.rst:193 +msgid "" +"``400`` Because your browser did not send a ``Host`` HTTP header field, the " +"virtual host being requested could not be determined. To access the website " +"correctly, you must upgrade to a browser that supports the HTTP ``Host`` " +"header field. ``request#no_host``" +msgstr "" +"``400`` Because your browser did not send a ``Host`` HTTP header field, the " +"virtual host being requested could not be determined. To access the website " +"correctly, you must upgrade to a browser that supports the HTTP ``Host`` " +"header field. (ブラウザーが ``Host`` HTTP ヘッダーを送信しなかったので、リク" +"エストされているバーチャルホストを決定できませんでした。Webサイトに正しくア" +"クセスするためには HTTP ``Host`` ヘッダーをサポートしているブラウザーにアッ" +"プグレードしなくてはなりません。) ``request#no_host``" + +#: ../../admin/traffic-server-error-messages.en.rst:204 +msgid "``HTTP Version Not Supported``" +msgstr "``HTTP Version Not Supported``" + +#: ../../admin/traffic-server-error-messages.en.rst:201 +msgid "" +"``505`` The origin server ```` is using an unsupported version " +"of the HTTP protocol. ``response#bad_version``" +msgstr "" +"``505`` The origin server ```` is using an unsupported version " +"of the HTTP protocol. (オリジンサーバー ``<サーバー名>`` はサポートされてい" +"ないバージョンの HTTP プロトコルを使用しています。) ``response#bad_version``" + +#: ../../admin/traffic-server-error-messages.en.rst:209 +msgid "``Invalid HTTP Request``" +msgstr "``Invalid HTTP Request``" + +#: ../../admin/traffic-server-error-messages.en.rst:207 +msgid "" +"``400`` Could not process this ```` HTTP method request for " +"``URL``. ``request#syntax_error``" +msgstr "" +"``400`` Could not process this ```` HTTP method request for " +"``URL``. (``URL`` への ``クライアントがリクエストしたメソッド`` HTTP メソッ" +"ドを処理できませんでした。) ``request#syntax_error``" + +#: ../../admin/traffic-server-error-messages.en.rst:214 +msgid "``Invalid HTTP Response``" +msgstr "``Invalid HTTP Response``" + +#: ../../admin/traffic-server-error-messages.en.rst:212 +#: ../../admin/traffic-server-error-messages.en.rst:217 +#: ../../admin/traffic-server-error-messages.en.rst:222 +#: ../../admin/traffic-server-error-messages.en.rst:232 +msgid "" +"``502`` The host ```` did not return the document ``URL`` " +"correctly. ``response#bad_response``" +msgstr "" +"``502`` The host ```` did not return the document ``URL`` " +"correctly. (``<サーバー名>`` というホストは ``URL`` のドキュメントを正しく返" +"しませんでした。) ``response#bad_response``" + +#: ../../admin/traffic-server-error-messages.en.rst:219 +msgid "``Malformed Server Response``" +msgstr "``Malformed Server Response``" + +#: ../../admin/traffic-server-error-messages.en.rst:224 +msgid "``Malformed Server Response Status``" +msgstr "``Malformed Server Response Status``" + +#: ../../admin/traffic-server-error-messages.en.rst:229 +msgid "``Maximum Transaction Time exceeded``" +msgstr "``Maximum Transaction Time exceeded``" + +#: ../../admin/traffic-server-error-messages.en.rst:227 +msgid "" +"``504`` Too much time has elapsed while transmitting document ``URL``. " +"``timeout#activity``" +msgstr "" +"``504`` Too much time has elapsed while transmitting document ``URL``. " +"(``URL`` のドキュメントの転送に時間が経過し過ぎました。) " +"``timeout#activity``" + +#: ../../admin/traffic-server-error-messages.en.rst:234 +msgid "``No Response Header From Server``" +msgstr "``No Response Header From Server``" + +#: ../../admin/traffic-server-error-messages.en.rst:240 +msgid "``Not Cached``" +msgstr "``Not Cached``" + +#: ../../admin/traffic-server-error-messages.en.rst:237 +msgid "" +"``504`` This document was not available in the cache, and you (the client) " +"only accept cached copies. ``cache#not_in_cache``" +msgstr "" +"``504`` This document was not available in the cache, and you (the client) " +"only accept cached copies. (このドキュメントはキャッシュ内で有効ではなく、あ" +"なた (クライアント) はキャッシュのコピーのみを受け入れます。) " +"``cache#not_in_cache``" + +#: ../../admin/traffic-server-error-messages.en.rst:246 +msgid "``Not Found on Accelerator``" +msgstr "``Not Found on Accelerator``" + +#: ../../admin/traffic-server-error-messages.en.rst:243 +msgid "" +"``404`` The request for ``URL`` on host ```` was not found. " +"Check the location and try again. ``urlrouting#no_mapping``" +msgstr "" +"``404`` The request for ``URL`` on host ```` was not found. " +"Check the location and try again. (``<サーバ名>`` 上の ``URL`` へのリクエス" +"トは見つかりませんでした。位置を確認してもう一度試してください。) " +"``urlrouting#no_mapping``" + +#: ../../admin/traffic-server-error-messages.en.rst:251 +msgid "``NULL``" +msgstr "``NULL``" + +#: ../../admin/traffic-server-error-messages.en.rst:249 +#: ../../admin/traffic-server-error-messages.en.rst:279 +msgid "" +"``502`` The host ```` did not return the document ``URL`` " +"correctly. ``response#bad_response``" +msgstr "" +"``502`` The host ```` did not return the document ``URL`` " +"correctly. (``<ホスト名>`` は ``URL`` のドキュメントを正しく返しませんでし" +"た。) ``response#bad_response``" + +#: ../../admin/traffic-server-error-messages.en.rst:256 +msgid "``Proxy Authentication Required``" +msgstr "``Proxy Authentication Required``" + +#: ../../admin/traffic-server-error-messages.en.rst:254 +msgid "" +"``407`` Please log in with username and password. " +"``access#proxy_auth_required``" +msgstr "" +"``407`` Please log in with username and password. (ユーザー名とパスワードで" +"ログインしてください。) ``access#proxy_auth_required``" + +#: ../../admin/traffic-server-error-messages.en.rst:261 +msgid "``Server Hangup``" +msgstr "``Server Hangup``" + +#: ../../admin/traffic-server-error-messages.en.rst:259 +msgid "" +"``502`` The server ```` closed the connection before the " +"transaction was completed. ``connect#hangup``" +msgstr "" +"``502`` The server ```` closed the connection before the " +"transaction was completed. (サーバー ``<ホスト名>`` はトランザクションが完了" +"する前に接続を閉じました。) ``connect#hangup``" + +#: ../../admin/traffic-server-error-messages.en.rst:266 +msgid "``Temporarily Moved``" +msgstr "``Temporarily Moved``" + +#: ../../admin/traffic-server-error-messages.en.rst:264 +msgid "" +"``302`` The document you requested, ``URL``, has moved to a new location. " +"The new location is ````. ``redirect#moved_temporarily``" +msgstr "" +"``302`` The document you requested, ``URL``, has moved to a new location. " +"The new location is ````. (リクエストしたドキュメント ``URL`` は新" +"しい場所に移動しました。新しい場所は ``<新しいURL>`` です。) " +"``redirect#moved_temporarily``" + +#: ../../admin/traffic-server-error-messages.en.rst:271 +msgid "``Transcoding Not Available``" +msgstr "``Transcoding Not Available``" + +#: ../../admin/traffic-server-error-messages.en.rst:269 +msgid "" +"``406`` Unable to provide the document ``URL`` in the format requested by " +"your browser. ``transcoding#unsupported``" +msgstr "" +"``406`` Unable to provide the document ``URL`` in the format requested by " +"your browser. (``URL`` のドキュメントをブラウザーが要求した形式で提供するこ" +"とができませんでした。) ``transcoding#unsupported``" + +#: ../../admin/traffic-server-error-messages.en.rst:276 +msgid "``Tunnel Connection Failed``" +msgstr "``Tunnel Connection Failed``" + +#: ../../admin/traffic-server-error-messages.en.rst:274 +msgid "" +"``502`` Could not connect to the server ````. " +"``connect#failed_connect``" +msgstr "" +"``502`` Could not connect to the server ````. (サーバー ``<ホスト" +"名>`` に接続できませんでした。) ``connect#failed_connect``" + +#: ../../admin/traffic-server-error-messages.en.rst:281 +msgid "``Unknown Error``" +msgstr "``Unknown Error``" + +#: ../../admin/traffic-server-error-messages.en.rst:289 +msgid "``Unknown Host``" +msgstr "``Unknown Host``" + +#: ../../admin/traffic-server-error-messages.en.rst:284 +msgid "" +"``500`` Unable to locate the server named ````; the server does " +"not have a DNS entry. Perhaps there is a misspelling in the server name or " +"the server no longer exists; double-check the name and try again. " +"``connect#dns_failed``" +msgstr "" +"``500`` Unable to locate the server named ````; the server does " +"not have a DNS entry. Perhaps there is a misspelling in the server name or " +"the server no longer exists; double-check the name and try again. (``<ホスト" +"名>`` と名付けられたサーバーを見つけられませんでした。サーバーは DNS エント" +"リーを持っていません。おそらくサーバー名のスペルミスもしくはサーバーがもう存" +"在していません。名前をダブルチェックしてもう一度試してください。) " +"``connect#dns_failed``" + +#: ../../admin/traffic-server-error-messages.en.rst:296 +msgid "``Unsupported URL Scheme``" +msgstr "``Unsupported URL Scheme``" + +#: ../../admin/traffic-server-error-messages.en.rst:292 +msgid "" +"``400`` Cannot perform your request for the document ``URL`` because the " +"protocol scheme is unknown. ``request#scheme_unsupported``" +msgstr "" +"``400`` Cannot perform your request for the document ``URL`` because the " +"protocol scheme is unknown. (プロトコルスキームが不明なため、ドキュメント " +"``URL`` へのリクエストを行えません。) ``request#scheme_unsupported``" + +#: ../../admin/traffic-server-error-messages.en.rst:301 +msgid "Standard HTTP Response Messages" +msgstr "標準的な HTTP レスポンスメッセージ" + +#: ../../admin/traffic-server-error-messages.en.rst:303 +msgid "" +"The following standard HTTP response messages are provided for your " +"information." +msgstr "次の標準的な HTTP レスポンスメッセージが参考情報として提供されます。" + +#: ../../admin/traffic-server-error-messages.en.rst:307 +msgid "``200``" +msgstr "``200``" + +#: ../../admin/traffic-server-error-messages.en.rst:307 +msgid "OK" +msgstr "OK" + +#: ../../admin/traffic-server-error-messages.en.rst:310 +msgid "``202``" +msgstr "``202``" + +#: ../../admin/traffic-server-error-messages.en.rst:310 +msgid "Accepted" +msgstr "Accepted" + +#: ../../admin/traffic-server-error-messages.en.rst:313 +msgid "``204``" +msgstr "``204``" + +#: ../../admin/traffic-server-error-messages.en.rst:313 +msgid "No Content" +msgstr "No Content" + +#: ../../admin/traffic-server-error-messages.en.rst:316 +msgid "``206``" +msgstr "``206``" + +#: ../../admin/traffic-server-error-messages.en.rst:316 +msgid "Partial Content" +msgstr "Partial Content" + +#: ../../admin/traffic-server-error-messages.en.rst:319 +msgid "``300``" +msgstr "``300``" + +#: ../../admin/traffic-server-error-messages.en.rst:319 +msgid "Multiple Choices" +msgstr "Multiple Choices" + +#: ../../admin/traffic-server-error-messages.en.rst:322 +msgid "``301``" +msgstr "``301``" + +#: ../../admin/traffic-server-error-messages.en.rst:322 +msgid "Moved Permanently" +msgstr "Moved Permanently" + +#: ../../admin/traffic-server-error-messages.en.rst:325 +msgid "``302``" +msgstr "``302``" + +#: ../../admin/traffic-server-error-messages.en.rst:325 +msgid "Found" +msgstr "Found" + +#: ../../admin/traffic-server-error-messages.en.rst:328 +msgid "``303``" +msgstr "``303``" + +#: ../../admin/traffic-server-error-messages.en.rst:328 +msgid "See Other" +msgstr "See Other" + +#: ../../admin/traffic-server-error-messages.en.rst:331 +msgid "``304``" +msgstr "``304``" + +#: ../../admin/traffic-server-error-messages.en.rst:331 +msgid "Not Modified" +msgstr "Not Modified" + +#: ../../admin/traffic-server-error-messages.en.rst:334 +msgid "``400``" +msgstr "``400``" + +#: ../../admin/traffic-server-error-messages.en.rst:334 +msgid "Bad Request" +msgstr "Bad Request" + +#: ../../admin/traffic-server-error-messages.en.rst:337 +msgid "``401``" +msgstr "``401``" + +#: ../../admin/traffic-server-error-messages.en.rst:337 +msgid "Unauthorized; retry" +msgstr "Unauthorized; retry" + +#: ../../admin/traffic-server-error-messages.en.rst:340 +msgid "``403``" +msgstr "``403``" + +#: ../../admin/traffic-server-error-messages.en.rst:340 +msgid "Forbidden" +msgstr "Forbidden" + +#: ../../admin/traffic-server-error-messages.en.rst:343 +msgid "``404``" +msgstr "``404``" + +#: ../../admin/traffic-server-error-messages.en.rst:343 +msgid "Not Found" +msgstr "Not Found" + +#: ../../admin/traffic-server-error-messages.en.rst:346 +msgid "``405``" +msgstr "``405``" + +#: ../../admin/traffic-server-error-messages.en.rst:346 +msgid "Method Not Allowed" +msgstr "Method Not Allowed" + +#: ../../admin/traffic-server-error-messages.en.rst:349 +msgid "``406``" +msgstr "``406``" + +#: ../../admin/traffic-server-error-messages.en.rst:349 +msgid "Not acceptable" +msgstr "Not acceptable" + +#: ../../admin/traffic-server-error-messages.en.rst:352 +msgid "``408``" +msgstr "``408``" + +#: ../../admin/traffic-server-error-messages.en.rst:352 +msgid "Request Timeout" +msgstr "Request Timeout" + +#: ../../admin/traffic-server-error-messages.en.rst:355 +msgid "``500``" +msgstr "``500``" + +#: ../../admin/traffic-server-error-messages.en.rst:355 +msgid "Internal server error" +msgstr "Internal server error" + +#: ../../admin/traffic-server-error-messages.en.rst:358 +msgid "``501``" +msgstr "``501``" + +#: ../../admin/traffic-server-error-messages.en.rst:358 +msgid "Not Implemented" +msgstr "Not Implemented" + +#: ../../admin/traffic-server-error-messages.en.rst:361 +msgid "``502``" +msgstr "``502``" + +#: ../../admin/traffic-server-error-messages.en.rst:361 +msgid "Bad Gateway" +msgstr "Bad Gateway" + +#: ../../admin/traffic-server-error-messages.en.rst:364 +msgid "``504``" +msgstr "``504``" + +#: ../../admin/traffic-server-error-messages.en.rst:364 +msgid "Gateway Timeout" +msgstr "Gateway Timeout" diff --git a/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy.en.po b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy.en.po new file mode 100644 index 00000000000..19a66eea6a6 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy.en.po @@ -0,0 +1,203 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/transparent-proxy.en.rst:4 +msgid "Transparent Proxying" +msgstr "透過プロキシー" + +#: ../../admin/transparent-proxy.en.rst:32 +msgid "" +"Transparent Proxying is the ability of a proxy (such as ATS) to intercept " +"connections between clients and servers without being visible." +msgstr "" +"透過プロキシーは (ATS などの ) プロキシーがクライアントとサーバーの間の接続" +"を見えないように横取りする能力です。" + +#: ../../admin/transparent-proxy.en.rst:35 +msgid "" +"The general network structure that will be used in this documentation looks " +"like this --" +msgstr "" +"このドキュメント内で使用される全体的なネットワーク構成はこのようになっていま" +"す。" + +#: ../../admin/transparent-proxy.en.rst:42 +msgid "ATS basic traffic flow of Transparent Proxy" +msgstr "透過プロキシーの ATS での基本的なトラッフィクの流れ" + +#: ../../admin/transparent-proxy.en.rst:44 +msgid "" +"There must be a gateway device through which passes all network traffic " +"from the client to the Internet (or external cloud). The gateway is " +"responsible for effectively splicing ATS in to selected streams of that " +"traffic. Each traffic stream is split in to two, with ATS terminating both " +"sides. That is, stream green-1, red-2, is split in to the green connection " +"and the red connection. Note that ATS may or may not be on the gateway " +"system, the redirected traffic can flow over other network infrastructure." +msgstr "" +"クライアントからインターネット ( もしくは外部のクラウド ) へのすべてのネット" +"ワークトラフィックを通すゲートウェイデバイスがなくてはなりません。このゲート" +"ウェイは効率的に ATS をそのトラフィックの選択されたストリームに継ぐことに責" +"任をもちます。各トラフィックストリームは二つに分割され、ATS は両側を終端しま" +"す。これは、ストリーム緑-1、赤-2 は緑の接続と赤の接続に分割されるということ" +"です。ATS はゲートウェイ上にあることもそうでないこともあることに注意してくだ" +"さい。向き先の変わったトラフィックは他のネットワーク基盤に流れ出ることがあり" +"ます。" + +#: ../../admin/transparent-proxy.en.rst:53 +msgid "" +"Because ATS uses two connections transparency can be set independently on " +"the client and origin server (Internet / external cloud) side. We will " +"define what is generally called \"transparent proxy\" as two aspects, " +"*inbound transparency* and *outbound transparency*." +msgstr "" +"なぜなら ATS はクライアント側とオリジンサーバー ( インターネット / 外部クラ" +"ウド ) の側とで独立して設定される可能性のある二つの接続透過性を使用するから" +"です。二つの面、\\ *内向き透過性*\\ と\\ *外向き透過性*\\ で何が一般的に\"透" +"過プロキシー\"と呼ばれるのかを定義していきます。" + +#: ../../admin/transparent-proxy.en.rst:58 +msgid "" +"Inbound transparency is a proxy that is transparent to connections that are " +"inbound to the proxy, i.e. a connection initiated by a client which " +"connects to the proxy (green-1). Similarly, outbound transparency is a " +"proxy that is transparent to connections that are outbound from the proxy, " +"i.e. a connection initiated by the proxy to an origin server (red-2)." +msgstr "" +"内向き透過性はプロキシーに入ってくる接続に対して透過なプロキシーです。例えば" +"プロキシーに接続するクライアントによって開始される接続 ( 緑-1 ) です。同様" +"に、外向き透過性はプロキシーから出ていく接続に対して透過なプロキシーです。例" +"えば、オリジンサーバーに接続するプロキシーによって開始される接続 ( 赤-2 ) で" +"す。" + +#: ../../admin/transparent-proxy.en.rst:65 +msgid "" +"In most treatments these two types of transparency are treated as unitarily " +"but that is not required. This implementation supports transparency " +"independently on the two (client, origin server) sides (`use cases `_." +msgstr "" +"これら二つのタイプの透過性のほとんどの扱いは一元的なものとして扱われますが、" +"それは必須ではありません。この実装は透過性を二つのサイド ( クライアント、オ" +"リジンサーバー ) で独立してサポートします。( `ユースケース `_)" + +#: ../../admin/transparent-proxy.en.rst:70 +msgid "" +"It is critical to note that any transparency requires specialized routing " +"and cannot be done solely by configuring ATS. ATS transparency also " +"requires support from the Linux kernel and therefore currently only works " +"on sufficiently recent Linux kernels that support the following features --" +msgstr "" +"どの透過性も特別なルーティングを必要とし、単に ATS を設定するだけでは完了で" +"きないことに十分に注意してください。ATS の透過性は Linux カーネルのサポート" +"も必要とするので、現在は次の機能をサポートした最近の Linux カーネルでしか十" +"分に動作しません。" + +#: ../../admin/transparent-proxy.en.rst:76 +msgid "TPROXY" +msgstr "TPROXY" + +#: ../../admin/transparent-proxy.en.rst:77 +msgid "POSIX capabilities" +msgstr "POSIX ケーパビリティ" + +#: ../../admin/transparent-proxy.en.rst:79 +msgid "" +"In addition the specialized routing will require using ``iptables`` and in " +"some cases ``ebtables``." +msgstr "" +"また特殊なルーティングは ``iptables`` を必要とし、いくつかのケースでは " +"``ebtables`` を必要とします。" + +#: ../../admin/transparent-proxy.en.rst:82 +msgid "" +"Standard build procedures should work for transparency support but if not " +"consult these :ref:`more detailed instructions `" +msgstr "" +"標準のビルド手順は透過プロキシーの対応でも使えるはずですが、うまくいかない場" +"合は\\ :ref:`より詳細な手順 `\\ を参考にして" +"ください。" + +#: ../../admin/transparent-proxy.en.rst:85 +msgid "" +"Transparency is configured per server port not globally. This is done via " +"the configuration values :ts:cv:`proxy.config.http.server_ports`. In " +"addition, :ts:cv:`proxy.config.reverse_proxy.enabled` must be enabled if " +"the client side is transparent. That should be fixed in a future patch." +msgstr "" +"透過性はグローバルにではなくサーバーのポート毎に設定されます。これは :ts:cv:" +"`proxy.config.http.server_ports` の設定値によって行われます。また、クライア" +"ント側が透過の場合は :ts:cv:`proxy.config.reverse_proxy.enabled` が有効化さ" +"れていなければなりません。これは将来のパッチで修正されます。" + +#: ../../admin/transparent-proxy.en.rst:90 +msgid "" +"In the first case use the attribute character (replacing the default 'X')" +msgstr "" +"最初のケースは ( デフォルトの 'X' を置き換えている) 属性文字を使用します" + +#: ../../admin/transparent-proxy.en.rst:93 +msgid "**Attribute** **Transparency Style** **Reverse Proxy**" +msgstr "**属性** **透過性スタイル** **リバースプロキシー**" + +#: ../../admin/transparent-proxy.en.rst:96 +msgid "``=``" +msgstr "``=``" + +#: ../../admin/transparent-proxy.en.rst:96 +msgid "Full transparency: either" +msgstr "完全透過性: どちらか" + +#: ../../admin/transparent-proxy.en.rst:99 +msgid "``>``" +msgstr "``>``" + +#: ../../admin/transparent-proxy.en.rst:99 +msgid "Inbound (client) transparency: enabled" +msgstr "内向き ( クライアント ) 透過性: 有効" + +#: ../../admin/transparent-proxy.en.rst:102 +msgid "``<``" +msgstr "``<``" + +#: ../../admin/transparent-proxy.en.rst:102 +msgid "Outbound (origin server) transparency: either" +msgstr "外向き ( オリジンサーバー ) 透過性: どちらか" + +#: ../../admin/transparent-proxy.en.rst:104 +msgid "" +"In the outbound transparent case clients must connect directly to ATS " +"either through an explicit proxy mechanism or by advertising the IP address " +"of the ATS server via DNS as the origin server address." +msgstr "" +"外向き透過性のケースではクライアントは明示的プロキシーの仕組みを通してか " +"ATS サーバーの IP アドレスをオリジンサーバーのアドレスとして DNS で広告する" +"かのどちらかで ATS に直接接続しなくてはなりません。" + +#: ../../admin/transparent-proxy.en.rst:108 +msgid "Some tested scenarios --" +msgstr "いくつかの実験済みのシナリオ" + +#: ../../admin/transparent-proxy.en.rst:110 +msgid ":doc:`transparent-proxy/bridge.en`" +msgstr ":doc:`transparent-proxy/bridge.en`" + +#: ../../admin/transparent-proxy.en.rst:111 +msgid ":doc:`transparent-proxy/router-inline.en`" +msgstr ":doc:`transparent-proxy/router-inline.en`" + +#: ../../admin/transparent-proxy.en.rst:112 +msgid ":doc:`transparent-proxy/wccp-configuration.en`" +msgstr ":doc:`transparent-proxy/wccp-configuration.en`" diff --git a/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/bridge.en.po b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/bridge.en.po new file mode 100644 index 00000000000..7db889054e3 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/bridge.en.po @@ -0,0 +1,283 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/transparent-proxy/bridge.en.rst:2 +msgid "Inline on a Linux Bridge" +msgstr "Linux ブリッジ上でのインライン" + +#: ../../admin/transparent-proxy/bridge.en.rst:23 +msgid "" +"A Linux can be configured to operate in `bridge mode `_. Two or " +"more physical interfaces are assigned to the bridge. A single IP address is " +"shared across the interfaces. By default any packet that arrives on one " +"interface is immediately routed out another bridge interface." +msgstr "" +"Linux は\\ `ブリッジモード `_\\ で動作するように設定できます。二つ以上の物" +"理インターフェースがブリッジに割り当てられます。一つの IP アドレスはそれらの" +"インターフェース間で共有されます。デフォルトでは一つのインターフェースに到着" +"したあらゆるパケットは直ちにもう一つのブリッジインターフェースに送り出されま" +"す。" + +#: ../../admin/transparent-proxy/bridge.en.rst:29 +msgid "Linux packages required:" +msgstr "必要な Linux のパッケージ" + +#: ../../admin/transparent-proxy/bridge.en.rst:31 +msgid "bridge-utils" +msgstr "bridge-utils" + +#: ../../admin/transparent-proxy/bridge.en.rst:32 +msgid "ebtables" +msgstr "ebtables" + +#: ../../admin/transparent-proxy/bridge.en.rst:34 +msgid "" +"In our example of setting up bridge mode we will use a local address of " +"192.168.1.11/24 and interfaces ``eth0`` and ``eth1`` as the bridge " +"interfaces (more detailed documentation is available `here `_). You may omit the " +"'#' character and everything after it. ::" +msgstr "" +"ブリッジモードの設定例では 192.168.1.11/24 のローカルアドレスとインター" +"フェース ``eth0`` と ``eth1`` をブリッジインターフェースとして使用します " +"( より詳細なドキュメントは `ここ `_ にあります) 。'#' とその後ろのものはすべ" +"て省略できます。 ::" + +#: ../../admin/transparent-proxy/bridge.en.rst:49 +msgid "" +"If you have not already done so, remember to add a default route, such as " +"this one for a gateway of 192.168.1.1. ::" +msgstr "" +"もしまだ済ませていない場合は、これが 192.168.1.1 のゲートウェイのためのもの" +"であると、デフォルト経路を追加することを覚えておいてください。" + +#: ../../admin/transparent-proxy/bridge.en.rst:54 +msgid "" +"At this point it is a good idea to test connectivity to verify the basic " +"bridge is functional." +msgstr "" +"この時点で基本的なブリッジが動作することを確認するために接続性をテストしてお" +"くと良いです。" + +#: ../../admin/transparent-proxy/bridge.en.rst:57 +msgid "" +"Once the bridge is verified to work, this is the basic traffic pattern of " +"interest." +msgstr "" +"ブリッジが動作することを確認できたなら、これがお望みの基本的なトラフィックパ" +"ターンです。" + +#: ../../admin/transparent-proxy/bridge.en.rst:64 +msgid "Picture of traffic flow through a bridge with ATS" +msgstr "ATS を使ったブリッジを通るトラフィックの流れ" + +#: ../../admin/transparent-proxy/bridge.en.rst:66 +msgid "" +"The green arrows are packets originating from the client and the red arrows " +"are packets originating from the origin server. All traffic not directed to " +"the local address will pass through the bridge. We need to break into some " +"of the traffic and subject it to routing so that it can be routed to ATS. " +"This requires ``ebtables``. The flows we want to intercept are green 1 " +"(from client to bridge) and red 1 (origin server to bridge)." +msgstr "" +"緑の矢印はクライアントからのパケットで、赤の矢印はオリジンサーバーからのパ" +"ケットです。ローカルアドレス宛てではないすべてのトラフィックはブリッジを通り" +"ます。トラフィックに割って入り ATS に向かうようにする必要があります。これに" +"は ``ebtables`` が必要となります。横取りしたい流れは緑 1 ( クライアントから" +"ブリッジ ) と赤 1 ( オリジンサーバーからブリッジ ) です。" + +#: ../../admin/transparent-proxy/bridge.en.rst:94 +msgid "" +"Traffic Server operates at layer 3 so we need to use ``iptables`` to handle " +"IP packets appropriately.::" +msgstr "" +"Traffic Server はレイヤー 3 で動作するので IP パケットを適切に扱うために " +"``iptables`` を使用する必要があります。 ::" + +#: ../../admin/transparent-proxy/bridge.en.rst:102 +msgid "" +"At this point the directionality of the interfaces matters. For the example " +"``eth1`` is the inbound (client side) interface, while ``eth0`` is the " +"outbound (origin server side) interface. We mark both flows of packets so " +"that we can use policy routing on them. For inbound packets we need to use " +"``TPROXY`` to force acceptance of packets to foreign IP addresses. For " +"returning outbound packets there will be a socket open bound to the foreign " +"address, we need only force it to be delivered locally. The value for ``--" +"on-ip`` is 0 because the target port is listening and not bound to a " +"specific address. The value for ``--on-port`` must match the Traffic Server " +"server port. Otherwise its value is arbitrary. ``--dport`` and ``--sport`` " +"specify the port from the point of view of the clients and origin servers." +msgstr "" +"ここでインターフェースの方向性が問題となります。例では ``eth1`` は内向き " +"( クライアント側 ) インターフェース、``eth0`` は外向き ( オリジンサーバー" +"側 ) インターフェースです。両方のパケットの流れでポリシーに沿ったルーティン" +"グができるように印を付けます。内向きのパケットでは外部の IP アドレスへのパ" +"ケットの受け付けを強制するために ``TPROXY`` を使う必要があります。外向きのパ" +"ケットを返すためには外部のアドレスに結びつけられているソケットが開かれてお" +"り、それを内部的に配達されることのみを強制する必要があります。ターゲットポー" +"トは listen 中で特定のアドレスには bind されていないので ``--on-ip`` の値は " +"0 です。``--on-port`` の値は Traffic Server のサーバーポートと一致しなければ" +"なりません。そうでなければその値は任意です。``--dport`` と ``--sport`` はク" +"ライアントとオリジンサーバーの視点でのポートを指定します。" + +#: ../../admin/transparent-proxy/bridge.en.rst:115 +msgid "" +"Once the flows are marked we can force them to be delivered locally via the " +"loopback interface via a policy routing table.::" +msgstr "" +"流れに印が付けられたのでそれらがポリシーに沿ったルーティングテーブルにより" +"ループバックインターフェースで内部的に配達されることを強制できます。" + +#: ../../admin/transparent-proxy/bridge.en.rst:121 +msgid "" +"The marking used is arbitrary but it must be consistent between " +"``iptables`` and the routing rule. The table number must be in the range " +"1..253." +msgstr "" +"使用済みと印を付けることは任意ですが、``iptables`` とルーティングルールとの" +"間で矛盾がないようにしなければなりません。テーブル番号は 1 から 253 の間でな" +"ければなりません。" + +#: ../../admin/transparent-proxy/bridge.en.rst:125 +msgid "" +"To configure Traffic Server set the following values in :file:`records." +"config`" +msgstr "" +"Traffic Server を設定するために次の :file:`records.config` の値を設定しま" +"す。" + +#: ../../admin/transparent-proxy/bridge.en.rst:128 +msgid "" +":ts:cv:`proxy.config.http.server_ports` *value from* ``--on-port`` (see " +"below)" +msgstr "" +":ts:cv:`proxy.config.http.server_ports` *の値は* ``--on-port`` (以下を参照)" + +#: ../../admin/transparent-proxy/bridge.en.rst:130 +msgid ":ts:cv:`proxy.config.reverse_proxy.enabled` ``1``" +msgstr ":ts:cv:`proxy.config.reverse_proxy.enabled` ``1``" + +#: ../../admin/transparent-proxy/bridge.en.rst:132 +msgid ":ts:cv:`proxy.config.url_remap.remap_required` ``0``" +msgstr ":ts:cv:`proxy.config.url_remap.remap_required` ``0``" + +#: ../../admin/transparent-proxy/bridge.en.rst:134 +msgid "" +"You may also need to set :ts:cv:`proxy.config.cluster.ethernet_interface` " +"to \"br0\" (the name of the bridge interface from the ``_)." +msgstr "" +":ts:cv:`proxy.config.cluster.ethernet_interface` を \"br0\" に設定する必要も" +"あります。( ブリッジインターフェースの名前は ``_ からとって" +"ください。)" + +#: ../../admin/transparent-proxy/bridge.en.rst:138 +msgid "Additional troubleshooting" +msgstr "追加のトラブルシューティング" + +#: ../../admin/transparent-proxy/bridge.en.rst:143 +msgid "" +"It is frequently the case that the default tables prevent incoming HTTP. " +"You can clear all filters with the commands::" +msgstr "" +"デフォルトテーブルが入ってくる HTTP を妨害するケースがよくあります。次のコマ" +"ンドですべてのフィルターを消去することができます。" + +#: ../../admin/transparent-proxy/bridge.en.rst:149 +msgid "" +"That is a bit drastic and should only be used for testing / debugging. A " +"live system will likely need some filters in place but that is beyond the " +"scope of this document. If this fixes the problem, then your filter set is " +"too restrictive." +msgstr "" +"これは劇的でテスト / デバッグのためだけに使用すべきです。稼働中のシステムは" +"ここにいくつかのフィルターを必要としますが、それはこのドキュメントの範囲外で" +"す。もしこれが問題を解決するのであれば、フィルターの制限が厳しすぎます。" + +#: ../../admin/transparent-proxy/bridge.en.rst:154 +msgid "" +"Note that this problem will prevent the basic bridge (without ATS) from " +"allowing HTTP traffic through." +msgstr "" +"この問題は HTTP のトラフィックを通過させる ( ATS を使わない ) 基本的なブリッ" +"ジ動作を妨げていることに注意してください。" + +#: ../../admin/transparent-proxy/bridge.en.rst:173 +msgid "Footnotes" +msgstr "脚注" + +#: ../../admin/transparent-proxy/bridge.en.rst:175 +msgid "" +"The ``--redirect-target`` can be omitted, but then the ``iptables`` rules " +"would need to use ``--physdev`` instead of just ``-i``. The actual packet " +"processing is identical." +msgstr "" +"``--redirect-target`` は省略可能ですが、``iptables`` のルールで単に ``-i`` " +"とする代わりに ``--physdev`` を使う必要があるでしょう。実際のパケット処理は" +"まったく同じです。" + +#: ../../admin/transparent-proxy/bridge.en.rst:74 +msgid "" +"In this example we will intercept port 80 (HTTP) traffic. We will use the " +"``BROUTING`` chain because it is traversed only for packets that originated " +"externally and arrived on a (forwarding enabled) interface. Although it " +"looks like this will intercept all port 80 traffic it will only affect the " +"two flows described above. ``-j redirect`` marks the packet as being " +"diverted to the bridge and not forwarded, and the ``DROP`` target puts the " +"packets in the normal ``iptables`` routing so that we can use standard " +"device tests on them [1]_. Although this example handles only port 80, " +"other ports are the same except for the port value. Note also the port here " +"is the port from the point of view of the clients and origin servers, not " +"the Traffic Server server port. ::" +msgstr "" +"この例ではポート 80 (HTTP) のトラフィックを横取りします。外部から発信され " +"( 転送が有効化された ) インターフェースに到着したパケットのみを扱いたいので " +"``BROUTING`` チェーンを使用します。ポート 80 のすべてのトラフィックを横取り" +"するように見えますが、上記の流れのみに影響を与えます。``-j redirect`` はパ" +"ケットがブリッジに流れ、転送はされないように印を付け、``DROP`` ターゲットは" +"パケットを標準的なデバイスのテストができるように通常の ``iptables`` のルー" +"ティングに置きます。 [1]_ この例はポート 80 のみを扱いますが、他のポートも" +"ポート番号が違うことを除いて同じです。ここでのポートはクライアントとオリジン" +"サーバーの視点でのものであり、Traffic Server のサーバーポートではないことに" +"注意してください。" + +#: ../../admin/transparent-proxy/bridge.en.rst:140 +msgid "" +"Check to make sure that ``iptables`` is not filtering (blocking) incoming " +"HTTP connections." +msgstr "" +"``iptables`` が入ってくる HTTP 接続をフィルタ ( ブロック ) していないことを" +"確認してください。" + +#: ../../admin/transparent-proxy/bridge.en.rst:157 +msgid "Verify that IP packet forwarding is enabled." +msgstr "IP パケット転送が有効化されていることを確認してください。" + +#: ../../admin/transparent-proxy/bridge.en.rst:159 +msgid "You can check this with::" +msgstr "これは次のように確認できます。 ::" + +#: ../../admin/transparent-proxy/bridge.en.rst:163 +msgid "" +"The output should be a non-zero value (usually '1'). If it is zero, you can " +"set it with::" +msgstr "" +"出力は非ゼロ値 ( たいてい '1' ) のはずです。もしゼロの場合は次のように設定可" +"能です。" + +#: ../../admin/transparent-proxy/bridge.en.rst:168 +msgid "" +"This can setting can be persisted by putting it in ``/etc/sysctl.conf``: ::" +msgstr "この設定は ``/etc/sysctl.conf`` に書くことで恒久的にできます。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/build.en.po b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/build.en.po new file mode 100644 index 00000000000..83f99f414fa --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/build.en.po @@ -0,0 +1,96 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/transparent-proxy/build.en.rst:4 +msgid "Building ATS for transparency" +msgstr "透過用 ATS のビルド" + +#: ../../admin/transparent-proxy/build.en.rst:24 +msgid "" +"In most cases, if your environment supports transparency then ``configure`` " +"will automatically enable it. For other environments you may need to " +"twiddle the ``configure`` options." +msgstr "" +"ほとんどのケースでは、環境が透過性をサポートしていれば ``configure`` が自動" +"的にそれを有効化します。そうでない環境では ``configure`` のオプションをいじ" +"る必要があるでしょう。" + +#: ../../admin/transparent-proxy/build.en.rst:34 +msgid "``--enable-posix-cap``" +msgstr "``--enable-posix-cap``" + +#: ../../admin/transparent-proxy/build.en.rst:29 +msgid "" +"This enables POSIX capabilities, which are required for transparency. These " +"are compiled in by default. To check your system, look for the header file " +"``sys/capability.h`` and the system library ``libcap``. These are in the " +"packages ``libcap`` and ``libcap-devel`` or ``libcap-dev`` (depending on " +"the Distribution) contra-respectively." +msgstr "" +"これは透過性で必要とされる POSIX ケーパビリティを有効化します。これらはデ" +"フォルトで自動的にコンパイルされます。システムを確認するために、ヘッダーファ" +"イル ``sys/capability.h`` とシステムライブラリ ``libcap`` を探します。これら" +"はそれぞれ ``libcap`` と ``libcap-devel`` または ``libcap-dev`` ( ディストリ" +"ビューションに依ります ) パッケージ内にあります。" + +#: ../../admin/transparent-proxy/build.en.rst:52 +msgid "``--enable-tproxy[=value]``" +msgstr "``--enable-tproxy[=value]``" + +#: ../../admin/transparent-proxy/build.en.rst:37 +msgid "" +"Enable TPROXY support, which is the Linux kernel feature used for " +"transparency. This should be present in the base installation, there is no " +"package associated with it. \\* ``auto`` Do automatic checks for the the " +"TPROXY header file (``linux/in.h``) and enable TPROXY support if the " +"``IP_TRANSPARENT`` definition is present. This is the default if this " +"option is not specified or ``value`` is omitted. \\* ``no`` Do not check " +"for TPROXY support, disable support for it. \\* ``force`` Do not check for " +"TPROXY support, enable it using the $ats@ built in value for " +"``IP_TRANSPARENT``. This is useful for systems that have it in the kernel " +"for but some reason do not have the appropriate system header file. \\* " +"*number* Do not check for TPROXY support, use *number* as the " +"``IP_TRANSPARENT`` value. There are, at present, no known standard " +"distributions of Linux that support TPROXY but use a value different from " +"the built in ATS default. However, a custom built kernel may do so and in " +"that case the specific value can be specified." +msgstr "" +"透過で使用される Linux カーネルの機能である TPROXY サポートを有効化します。" +"これは基本的なインストールに含まれているはずであり、これに紐付くパッケージは" +"ありません。\\* ``auto`` TPROXY ヘッダーファイル (``linux/in.h``) を自動的" +"に確認し、``IP_TRANSPARENT`` の定義が存在する場合は TPROXY サポートを有効化" +"します。これはこのオプションが指定されていないか ``value`` が省略された場合" +"のデフォルトです。\\* ``no`` TPROXY サポートを確認せず、そのサポートを無効化" +"します。\\* ``force`` TPROXY サポートを確認せず、``IP_TRANSPARENT`` のため" +"の $ats@ 組み込みの値を使用して有効化します。これはカーネルにはあるものの何" +"らかの理由で適切なシステムヘッダーファイルを持っていないシステムの場合に便利" +"です。\\* *number* TPROXY サポートを確認せず、 *number* を " +"``IP_TRANSPARENT`` の値として使用します。いまのところ、TPROXY をサポートして" +"いて ATS 組み込みのデフォルトと異なる値を使用することが知られている標準的な" +"ディストリビューションはありません。しかし、カスタムビルドのカーネルはそうし" +"ているかも知れず、その場合には特定の値が指定できます。" + +#: ../../admin/transparent-proxy/build.en.rst:54 +msgid "" +"In the default case, ATS configuration will automatically check for TPROXY " +"support via the presence of the ``linux/in.h`` header file and compile in " +"TPROXY support if it is available. If that fails, you may be able to " +"recover by using one of the options above. Note that transparency may be " +"built in by default but it is not active unless explicitly enabled in the " +"ATS configuration files." +msgstr "" +"デフォルトでは、ATS の設定はヘッダーファイル ``linux/in.h`` の存在により " +"TPROXY の対応を自動的に確認し、それが有効なら TPROXY 対応でコンパイルしま" +"す。これが失敗した場合は、たぶん上記のオプションのどれか一つを使うことで回復" +"可能です。透過性はデフォルトでビルドされることがありますが、ATS の設定ファイ" +"ルで明示的に有効化しない限り動作しないことに注意してください。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/router-inline.en.po b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/router-inline.en.po new file mode 100644 index 00000000000..d38cc9e0948 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/router-inline.en.po @@ -0,0 +1,147 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/transparent-proxy/router-inline.en.rst:2 +msgid "Inline on a Linux router" +msgstr "Linux ルーター上でのインライン" + +#: ../../admin/transparent-proxy/router-inline.en.rst:21 +msgid "" +"The routed set up presumes the set of clients are on distinct networks " +"behind a single physical interface. For the purposes of this example will " +"we presume" +msgstr "" +"経路セットアップはクライアントは一つの物理インターフェースの後ろにある別々の" +"ネットワーク上に存在すると仮定します。この例の目的を次のように仮定します。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:25 +msgid "The clients are on network 172.28.56.0/24" +msgstr "クライアントは 172.28.56.0/24 のネットワーク上にあります" + +#: ../../admin/transparent-proxy/router-inline.en.rst:26 +msgid "The router connects the networks 172.28.56.0/24 and 192.168.1.0/24" +msgstr "" +"ルーターは 172.28.56.0/24 と 192.168.1.0/24 のネットワークを接続しています。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:27 +msgid "Interface ``eth0`` is on the network 192.168.1.0/24" +msgstr "" +"インターフェース ``eth0`` は 192.168.1.0/24 のネットワーク上にあります。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:28 +msgid "Interface ``eth1`` is on the network 172.28.56.0/24" +msgstr "" +"インターフェース ``eth1`` は 172.28.56.0/24 のネットワーク上にあります。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:29 +msgid "" +"The router is already configured to route traffic correctly for the clients." +msgstr "" +"このルーターはクライアントのためにトラフィックを正しく転送するようにすでに設" +"定済みです。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:32 +msgid "" +"In this example we will intercept port 80 (HTTP) traffic that traverses the " +"router. The first step is to use ``iptables`` to handle IP packets " +"appropriately." +msgstr "" +"この例ではルーターを通るポート 80 (HTTP) のトラフィックを横取りします。最初" +"のステップは IP パケットを適切に扱うために ``iptables`` を使うことです。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:47 +msgid "" +"We mark packets so that we can use policy routing on them. For inbound " +"packets we use ``TPROXY`` to make it possible to accept packets sent to " +"foreign IP addresses. For returning outbound packets there will be a socket " +"open bound to the foreign address, we need only force it to be delivered " +"locally. The value for ``--on-ip`` is 0 because the target port is " +"listening and not bound to a specific address. The value for ``--on-port`` " +"must match the Traffic Server server port. Otherwise its value is " +"arbitrary. ``--dport`` and ``--sport`` specify the port from the point of " +"view of the clients and origin servers. The middle two lines exempt local " +"web traffic from being marked for Traffic Server -- these rules can be " +"tightened or loosened as needed. They server by matching traffic and " +"exiting the ``iptables`` processing via ``ACCEPT`` before the last line is " +"checked." +msgstr "" +"これらについてポリシールーティングができるようにパケットに印を付けます。内向" +"きのパケットでは外部の IP アドレスに送信されるパケットを受け付けるために " +"``TPROXY`` を使用します。外向きのパケットを返すために外部アドレスに bind さ" +"れたソケットがあり、内部的に配送されることのみを強制します。``--on-ip`` の値" +"は目的のポートは特定のアドレスに bind されておらず listen 状態なので 0 で" +"す。``--on-port`` の値は Traffic Server のサーバーポートと一致しなければ成り" +"ませんが、その他の点では任意の値を使用できます。 ``--dport`` と ``--sport`` " +"はクライアントとオリジンサーバーの視点でのポートを指定します。真ん中の二行は" +"印の付けられた Traffic Server へのローカルなウェブトラフィックを通します。こ" +"れらのルールは必要に応じて厳しくすることも緩めることも可能です。トラフィック" +"のマッチングと最後の行が確認される前の ``iptables`` での ``ACCEPT`` による処" +"理により提供されます。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:61 +msgid "" +"Once the flows are marked we can force them to be delivered locally via the " +"loopback interface via a policy routing table." +msgstr "" +"一度フローに印が付けられると、それらがポリシールーティングテーブルによりルー" +"プバックインターフェースで内部的に配送されることを強制できます。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:69 +msgid "" +"The marking used is arbitrary but it must be consistent between " +"``iptables`` and the routing rule. The table number must be in the range " +"1..253." +msgstr "" +"使用済みという印付けは独断的に行われますが、``iptables`` とルーティングルー" +"ルとの間で一貫していなければなりません。テーブル番号は 1 から 253 の間でなけ" +"ればなりません。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:73 +msgid "" +"To configure Traffic Server set the following values in :file:`records." +"config`" +msgstr "" +"Traffic Server を設定するために次の値を :file:`records.config` に設定してく" +"ださい。" + +#: ../../admin/transparent-proxy/router-inline.en.rst:78 +msgid "``proxy.config.http.server_port``" +msgstr "``proxy.config.http.server_port``" + +#: ../../admin/transparent-proxy/router-inline.en.rst:81 +msgid "``STRING`` Default: ``=``" +msgstr "``STRING`` デフォルト: ``=``" + +#: ../../admin/transparent-proxy/router-inline.en.rst:86 +msgid "``proxy.config.reverse_proxy.enabled``" +msgstr "``proxy.config.reverse_proxy.enabled``" + +#: ../../admin/transparent-proxy/router-inline.en.rst:85 +msgid "``INT`` Default: ``1``" +msgstr "``INT`` デフォルト: ``1``" + +#: ../../admin/transparent-proxy/router-inline.en.rst:90 +msgid "``proxy.config.url_remap.remap_required``" +msgstr "``proxy.config.url_remap.remap_required``" + +#: ../../admin/transparent-proxy/router-inline.en.rst:89 +msgid "``INT`` Default: ``0``" +msgstr "``INT`` デフォルト: ``0``" + +#: ../../admin/transparent-proxy/router-inline.en.rst:77 +msgid "``STRING`` Default: *value from* ``--on-port``" +msgstr "``STRING`` デフォルト: ``--on-port`` *の値*" + +#: ../../admin/transparent-proxy/router-inline.en.rst:82 +msgid "``proxy.config.http.server_port_attr``" +msgstr "``proxy.config.http.server_port_attr``" diff --git a/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/wccp-configuration.en.po b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/wccp-configuration.en.po new file mode 100644 index 00000000000..8b6b52029e7 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/wccp-configuration.en.po @@ -0,0 +1,285 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:2 +msgid "WCCP Configuration" +msgstr "WCCP 設定" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:25 +msgid "" +"`WCCP `_ is de-facto semi-standard used by routers to redirect network " +"traffic to caches. It is available on most Cisco™ routers although it does " +"not appear to be officially supported by Cisco. The primary benefits of " +"WCCP are" +msgstr "" +"`WCCP `_ はルーターがネットワークトラフィックをキャッシュに向ける準デファクト" +"スタンダードです。Cisco™ から公式にサポートされているようには見えないもの" +"の、多くの Cisco のルーターで利用可能です。WCCP の主な利益は次のとおりです。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:33 +msgid "" +"WCCP fails open so that if the Traffic Server machine fails, it is bypassed " +"and users continue to have Internet access." +msgstr "" +"Traffic Server マシンが失敗するように WCCP がオープンに失敗すると、それはバ" +"イパスされユーザーはインターネットへのアクセスを継続できます。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:42 +msgid "" +"Because the router serves as the inline network element, Traffic Server " +"must run on a separate host. This host can be located anywhere as long as " +"Traffic Server is either on the same network segment or a GRE tunnel can be " +"maintained between the Traffic Server host and the router." +msgstr "" +"ルーターはインラインのネットワーク要素として動くので、Traffic Server は別の" +"ホスト上で動作しなければ成りません。このホストは Traffic Server が同じネット" +"ワークセグメント上にあるか Traffic Server のホストとルーターとの間で GRE ト" +"ンネルが維持可能であればどこに置くこともできます。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:47 +msgid "" +"|important| This document presumes that the router is already properly " +"configured to handle traffic between the clients and the origin servers. If " +"you are not certain, verify it before attempting to configure Traffic " +"Server with WCCP. This is also a good state to which to revert should the " +"configuration go badly." +msgstr "" +"|important| このドキュメントはルータがクライアントとオリジンサーバーとの間の" +"トラッフィクを扱えるように正しく設定済みであることを仮定しています。もし確か" +"でない場合は、WCCP を使うよう Traffic Server を設定する前に確認してくださ" +"い。設定がおかしくなった際に元に戻すのも良い心がけです。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:54 +msgid "Configuration overview" +msgstr "設定の概要" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:56 +msgid "" +"Setting WCCP is a three step process, first configuring the router, the " +"Traffic Server host, and Traffic Server." +msgstr "" +"WCCP の設定は、ルーターの設定、Traffic Server ホスト、そして Traffic Server " +"の 3 ステップです。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:59 +msgid "" +"|image1| The router will **not** respond to WCCP protocol packets unless " +"explicitly configured to do so. Via WCCP, the router can be made to perform " +"packet interception and redirection needed by Traffic Server transparency. " +"The WCCP protocol in effect acts as means of controlling a rough form of " +"policy routing with positive heartbeat cutoff." +msgstr "" +"|image1| ルーターは明示的に設定をしない限り WCCP プロトコルのパケットに応答" +"\\ *しません*\\ 。WCCP では、ルーターがパケットの横取りと Traffic Server の" +"透過性に必要とされる向き先の変更を行うように設定されます。WCCP プロトコルは" +"事実上、positive heartbeat cutoff によりポリシールーティングのだいたいの形を" +"制御する方法として振る舞います。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:65 +msgid "" +"The Traffic Server host system must also be configured using ``iptables`` " +"to accept connections on foreign addresses. This is done roughly the same " +"way as the standard transparency use." +msgstr "" +"Traffic Server のホストシステムは外部アドレスの接続を受け付けるために " +"``iptables`` を使うようにも設定されなかれば成りません。これは標準的な透過性" +"の使用とだいたい同じ方法で行えます。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:69 +msgid "" +"Finally Traffic Server itself must be configured for transparency and use " +"of WCCP. The former is again very similar to the standard use, while WCCP " +"configuration is specific to WCCP and uses a separate configuration file, " +"referred to by the :file:`records.config` file." +msgstr "" +"最後に Traffic Server 自体が透過性と WCCP を使用するように設定されなければな" +"りません。構成方法もまた標準的な使用とよく似ており、WCCP の設定は WCCP に特" +"化していて分離された設定ファイルを使用しますが、:file:`records.config` ファ" +"イルにより参照されます。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:74 +msgid "" +"The primary concern for configuration in which of three basic topologies " +"are to be used." +msgstr "三種類のどの基本トポロジーが使用されるかによる設定における主な懸念。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:77 +msgid "" +"Dedicated -- Traffic Server traffic goes over an interface that is not used " +"for client nor origin server traffic." +msgstr "" +"専用 -- Traffic Server のトラフィックがクライアントにもオリジンサーバーのト" +"ラフィックにも使われていないインターフェースに渡ります。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:79 +msgid "" +"Shared -- Traffic Server traffic shares an interface with client or server " +"traffic." +msgstr "" +"共有 -- Traffic Server のトラッフィクがクライアントまたはサーバーのトラ" +"フィックとインターフェースを共有します。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:81 +msgid "Inside Shared -- Traffic Server and client traffic share an interface." +msgstr "" +"内部共有 -- Traffic Server とクライアントのトラフィックがインターフェースを" +"共有します。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:83 +msgid "" +"`Outside Shared `_ -- Traffic Server and origin " +"server traffic share an interface." +msgstr "" +"`外部共有 `_ -- Traffic Server とオリジンサーバー" +"のトラフィックがインターフェースを共有します。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:92 +msgid "Shared interface issues" +msgstr "共有インターフェースの課題" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:94 +msgid "" +"A shared interface topology has additional issues compared to a dedicated " +"topology that must be handled. Such a topology is required if the router " +"has only two interfaces, and because of these additional issues it is " +"normally only used in such cases, although nothing prevents it use even if " +"the router has three or more interfaces." +msgstr "" +"共有インターフェーストポロジーは専用トポロジーと比べると扱わなければならない" +"追加の課題があります。このようなトポロジーはルーターが二つのインターフェース" +"しか持っていない場合に必要となり、ルーターが三つ以上のインターフェースを持っ" +"ている場合でもその使用を妨げるものはありませんが、これらの追加の課題があるの" +"で通常はそのようなケースでしか使用されません。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:110 +msgid "Frequently encountered problems" +msgstr "よくぶつかる問題" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:113 +msgid "MTU and fragmentation" +msgstr "MTU と断片化" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:115 +msgid "" +"In most cases the basic configuration using a tunnel in any topology can " +"fail due to issues with fragmentation. The socket logic is unable to know " +"that its packets will eventually be put in to a tunnel which will by its " +"nature have a smaller `MTU `_ than the physical interface which it uses. " +"This can lead to pathological behavior or outright failure as the packets " +"sent are just a little too big. It is not possible to solve easily by " +"changing the MTU on the physical interface because the tunnel interface " +"uses that to compute its own MTU." +msgstr "" +"ほとんどのケースではどのトポロジーでもトンネルを使用する基本設定は断片化の課" +"題により失敗します。ソケットのロジックはパケットがいずれ物理インターフェース" +"が使用するものより小さい `MTU `_ をもったトンネルに入るということを知ることがで" +"きません。これは送信したパケットがほんの少し大きすぎるのと同様に異常な振る舞" +"いや完全な失敗を引き起こします。トンネルインターフェースは自身の MTU を計算" +"するために物理インターフェース上の MTU を使用するのでそれを変更することで簡" +"単に解決することはできません。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:126 +msgid "References" +msgstr "参考文献" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:128 +msgid "" +"`WCCP Router Configuration Commands - IOS 12.2 `_" +msgstr "" +"`WCCP Router Configuration Commands - IOS 12.2 `_" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:139 +msgid "" +"Server side transparency should also be used, but it is not as significant. " +"In its absence, however, origin servers may see the source address of " +"connections suddenly change from the Traffic Server address to client " +"addresses, which could cause problems. Further, the primary reason for not " +"having server side transparency is to hide client addresses which is " +"defeated if the Traffic Server host fails." +msgstr "" +"サーバー側の透過性も使用されるべきですが、重要なことではありません。それがな" +"い場合であっても、オリジンサーバーは問題を起こすであろう突然 Traffic Server " +"のアドレスからクライアントのアドレスへと変わる接続元のアドレスに遭遇するで" +"しょう。また、サーバー側の透過性を持たない主な理由は、Traffic Server ホスト" +"が動かなくなったときに使えなくなるクライアントのアドレスを隠すためです。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:147 +msgid "If your router has only one interface, it's hardly a *router*." +msgstr "" +"ルーターが一つのインターフェースしかもっていないなら、それはまったく\\ *ルー" +"ター*\\ ではありません。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:150 +msgid "" +"This is not fundamentally impossible, as the packets are distinct in layer" +msgstr "パケットはレイヤー内では別々なので、本質的には不可能ではありません。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:36 +msgid "" +"Use of WCCP only makes sense for client side transparency [1]_ because if " +"the clients are explicitly proxied by Traffic Server there's no benefit to " +"WCCP fail open, as the clients will continue to directly access the " +"unresponsive Traffic Server host. It would be better to adjust the routing " +"tables on the router for explicit proxying." +msgstr "" +"クライアントが Traffic Server によって明示的にプロキシーされている場合には " +"WCCP の fail open に対して利益がなく、クライアントは応答しない Traffic " +"Server ホストに直接アクセスできるので WCCP の使用はクライアント側の透過性で" +"のみ意味をなします [1]_ 。ルーター上のルーティングテーブルを明示的なプロキ" +"シーのために調整すると良いでしょう。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:86 +msgid "" +"In general the dedicated topology is preferred. However, if the router has " +"only two interfaces one of the shared topologies will be required [2]_ " +"Click the links above for more detailed configuration information on a " +"specific topology." +msgstr "" +"一般的には専用トポロジーが好まれます。しかしながら、ルーターが二つしかイン" +"ターフェースを持っていない場合は二つの共有トポロジーのうちの一つが必要となり" +"ます [2]_ 。特定のトポロジーでのより詳細な設定情報については上記のリンクをク" +"リックしてください。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:100 +msgid "" +"The basic concept for a shared interface is to use a tunnel to simulate the " +"dedicated interface case. This enables the packets to be distinguished at " +"layer 3. For this reason, layer 2 redirection cannot be used because the " +"WCCP configuration cannot distinguish between packets returning from the " +"origin server and packets returning from Traffic Server as they are " +"distinguished only by layer 2 addressing [3]_. Fortunately the GRE tunnel " +"used for packet forwarding and return can be used as the simulated " +"interface for Traffic Server." +msgstr "" +"共有インターフェースのための基本的なコンセプトは専用インターフェースのケース" +"をシミュレートするためにトンネルを使うことです。これはパケットがレイヤー 3 " +"で識別できるようにします。この理由のために、オリジンサーバーから帰ってくるパ" +"ケットと Traffic Server から帰ってくるパケットの識別はレイヤー 2 のアドレス" +"でのみでき [3]_ WCCP の設定ではできないので、レイヤー 2 での向き先の変更は使" +"うことができません。幸いパケットの転送と返送に使われる GRE トンネルが " +"Traffic Server のためにシミュレートされたインターフェースとして使用できま" +"す。" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:31 +msgid "" +"If already have a router that supports WCCP inline you do not have to " +"change your network topology." +msgstr "" +"もしすでに WCCP インラインに対応したルーターを持っているのならネットワー" +"クトポロジを変更する必要はありません。" diff --git a/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po b/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po new file mode 100644 index 00000000000..d1d39b84604 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po @@ -0,0 +1,1442 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/working-log-files.en.rst:4 +msgid "Working with Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:24 +msgid "" +"Traffic Server generates log files that contain information about every " +"request it receives and every error it detects." +msgstr "" + +#: ../../admin/working-log-files.en.rst:27 +msgid "This chapter discusses the following topics:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:37 +msgid "Understanding Traffic Server Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:39 +msgid "" +"Traffic Server records information about every transaction (or request) it " +"processes and every error it detects in log files. Traffic Server keeps " +"three types of log files:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:43 +msgid "" +"**Error log files** record information about why a particular transaction " +"was in error." +msgstr "" + +#: ../../admin/working-log-files.en.rst:46 +msgid "" +"**Event log files** (also called **access log files**) record information " +"about the state of each transaction Traffic Server processes." +msgstr "" + +#: ../../admin/working-log-files.en.rst:50 +msgid "" +"**System log files** record system information, including messages about " +"the state of Traffic Server and errors/warnings it produces. This kind of " +"information might include a note that event log files were rolled, a " +"warning that cluster communication timed out, or an error indicating that " +"Traffic Server was restarted." +msgstr "" + +#: ../../admin/working-log-files.en.rst:56 +msgid "" +"All system information messages are logged with the system-wide logging " +"facility :manpage:`syslog` under the daemon facility. The :manpage:`syslog." +"conf(5)` configuration file (stored in the ``/etc`` directory) specifies " +"where these messages are logged. A typical location is ``/var/log/" +"messages`` (Linux)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:62 +msgid "" +"The :manpage:`syslog(8)` process works on a system-wide basis, so it serves " +"as the single repository for messages from all Traffic Server processes " +"(including :program:`traffic_server`, :program:`traffic_manager`, and :" +"program:`traffic_cop`)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:67 +msgid "" +"System information logs observe a static format. Each log entry in the log " +"contains information about the date and time the error was logged, the " +"hostname of the Traffic Server that reported the error, and a description " +"of the error or warning." +msgstr "" + +#: ../../admin/working-log-files.en.rst:72 +msgid "" +"Refer to :ref:`traffic-server-error-messages` for a list of the messages " +"logged by Traffic Server." +msgstr "" + +#: ../../admin/working-log-files.en.rst:75 +msgid "" +"By default, Traffic Server creates both error and event log files and " +"records system information in system log files. You can disable event " +"logging and/or error logging by setting the configuration variable :ts:cv:" +"`proxy.config.log.logging_enabled` (in the :file:`records.config` file) to " +"one of the following values:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:81 +msgid "``0`` to disable both event and error logging" +msgstr "" + +#: ../../admin/working-log-files.en.rst:82 +msgid "``1`` to enable error logging only" +msgstr "" + +#: ../../admin/working-log-files.en.rst:83 +msgid "``2`` to enable transaction logging only" +msgstr "" + +#: ../../admin/working-log-files.en.rst:84 +msgid "``3`` to enable both transaction and error logging" +msgstr "" + +#: ../../admin/working-log-files.en.rst:87 +msgid "Understanding Event Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:89 +msgid "" +"Event log files record information about every request that Traffic Server " +"processes. By analyzing the log files, you can determine how many people " +"use the Traffic Server cache, how much information each person requested, " +"what pages are most popular, and so on. Traffic Server supports several " +"standard log file formats, such as Squid and Netscape, as well as user-" +"defined custom formats. You can analyze the standard format log files with " +"off-the-shelf analysis packages. To help with log file analysis, you can " +"separate log files so they contain information specific to protocol or " +"hosts. You can also configure Traffic Server to roll log files " +"automatically at specific intervals during the day or when they reach a " +"certain size." +msgstr "" + +#: ../../admin/working-log-files.en.rst:101 +msgid "" +"The following sections describe the Traffic Server logging system features " +"and discuss how to:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:104 +msgid "**Manage your event log files**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:106 +msgid "" +"You can choose a central location for storing log files, set how much disk " +"space to use for log files, and set how and when to roll log files. Refer " +"to `Managing Event Log Files`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:110 +msgid "**Choose different event log file formats**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:112 +msgid "" +"You can choose which standard log file formats you want to use for traffic " +"analysis, such as Squid or Netscape. Alternatively, you can use the Traffic " +"Server custom format, which is XML-based and enables you to institute more " +"control over the type of information recorded in log files. Refer to " +"`Choosing Event Log File Formats`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:118 +msgid "**Roll event log files automatically**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:120 +msgid "" +"Configure Traffic Server to roll event log files at specific intervals " +"during the day or when they reach a certain size; this enables you to " +"identify and manipulate log files that are no longer active. Refer to " +"`Rolling Event Log Files`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:125 +msgid "**Separate log files according to protocols and hosts**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:127 +msgid "" +"Configure Traffic Server to create separate log files for different " +"protocols. You can also configure Traffic Server to generate separate log " +"files for requests served by different hosts. Refer to `Splitting Event Log " +"Files`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:131 +msgid "**Collate log files from different Traffic Server nodes**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:133 +msgid "" +"Designate one or more nodes on the network to serve as log collation " +"servers. These servers, which might be standalone or part of Traffic " +"Server, enable you to keep all logged information in well-defined " +"locations. Refer to `Collating Event Log Files`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:138 +msgid "**View statistics about the logging system**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:140 +msgid "" +"Traffic Server provides statistics about the logging system; you can access " +"these statistics via Traffic Line. Refer to `Viewing Logging Statistics`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:143 +msgid "**Interpret log file entries for the log file formats**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:145 +msgid "Refer to `Example Event Log File Entries`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:148 +msgid "Managing Event Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:150 +msgid "" +"Traffic Server enables you to control where event log files are located and " +"how much space they can consume. Additionally you can specify how to handle " +"low disk space in the logging directory." +msgstr "" + +#: ../../admin/working-log-files.en.rst:155 +msgid "Choosing the Logging Directory" +msgstr "" + +#: ../../admin/working-log-files.en.rst:157 +msgid "" +"By default, Traffic Server writes all event log files in the ``logs`` " +"directory located in the directory where you installed Traffic Server. To " +"use a different directory, refer to `Setting Log File Management Options`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:162 +msgid "Controlling Logging Space" +msgstr "" + +#: ../../admin/working-log-files.en.rst:164 +msgid "" +"Traffic Server enables you to control the amount of disk space that the " +"logging directory can consume. This allows the system to operate smoothly " +"within a specified space window for a long period of time. After you " +"establish a space limit, Traffic Server continues to monitor the space in " +"the logging directory. When the free space dwindles to the headroom limit " +"(see `Setting Log File Management Options`_), it enters a low space state " +"and takes the following actions:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:172 +msgid "" +"If the autodelete option (discussed in `Rolling Event Log Files`_) is " +"*enabled*, then Traffic Server identifies previously-rolled log files (i." +"e., log files with the ``.old`` extension). It starts deleting files one by " +"one, beginning with the oldest file, until it emerges from the low state. " +"Traffic Server logs a record of all deleted files in the system error log." +msgstr "" + +#: ../../admin/working-log-files.en.rst:179 +msgid "" +"If the autodelete option is *disabled* or there are not enough old log " +"files to delete for the system to emerge from its low space state, then " +"Traffic Server issues a warning and continues logging until space is " +"exhausted. When available space is consumed, event logging stops. Traffic " +"Server resumes event logging when enough space becomes available for it to " +"exit the low space state. To make space available, either explicitly " +"increase the logging space limit or remove files from the logging directory " +"manually." +msgstr "" + +#: ../../admin/working-log-files.en.rst:188 +msgid "" +"You can run a :manpage:`cron(8)` script in conjunction with Traffic Server " +"to automatically remove old log files from the logging directory before " +"Traffic Server enters the low space state. Relocate the old log files to a " +"temporary partition, where you can run a variety of log analysis scripts. " +"Following analysis, either compress the logs and move to an archive " +"location, or simply delete them." +msgstr "" + +#: ../../admin/working-log-files.en.rst:199 +msgid "Setting Log File Management Options" +msgstr "" + +#: ../../admin/working-log-files.en.rst:201 +msgid "To set log management options, follow the steps below:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:203 +#: ../../admin/working-log-files.en.rst:238 +#: ../../admin/working-log-files.en.rst:576 +#: ../../admin/working-log-files.en.rst:660 +msgid "In the :file:`records.config` file, edit the following variables" +msgstr "" + +#: ../../admin/working-log-files.en.rst:205 +#: ../../admin/working-log-files.en.rst:808 +msgid ":ts:cv:`proxy.config.log.logfile_dir`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:206 +msgid ":ts:cv:`proxy.config.log.max_space_mb_for_logs`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:207 +msgid ":ts:cv:`proxy.config.log.max_space_mb_headroom`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:209 +#: ../../admin/working-log-files.en.rst:267 +#: ../../admin/working-log-files.en.rst:583 +#: ../../admin/working-log-files.en.rst:665 +#: ../../admin/working-log-files.en.rst:696 +#: ../../admin/working-log-files.en.rst:767 +#: ../../admin/working-log-files.en.rst:834 +msgid "" +"Run the command :option:`traffic_line -x` to apply the configuration " +"changes." +msgstr "" + +#: ../../admin/working-log-files.en.rst:213 +msgid "Choosing Event Log File Formats" +msgstr "" + +#: ../../admin/working-log-files.en.rst:215 +msgid "Traffic Server supports the following log file formats:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:217 +msgid "" +"Standard formats, such as Squid or Netscape; refer to `Using Standard " +"Formats`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:218 +msgid "The Traffic Server custom format; refer to `Using the Custom Format`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:220 +msgid "" +"In addition to the standard and custom log file format, you can choose " +"whether to save log files in binary or ASCII; refer to `Choosing Binary or " +"ASCII`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:223 +msgid "" +"Event log files consume substantial disk space. Creating log entries in " +"multiple formats at the same time can consume disk resources very quickly " +"and adversely impact Traffic Server performance." +msgstr "" + +#: ../../admin/working-log-files.en.rst:228 +msgid "Using Standard Formats" +msgstr "" + +#: ../../admin/working-log-files.en.rst:230 +msgid "" +"The standard log formats include Squid, Netscape Common, Netscape extended, " +"and Netscape Extended-2. The standard log file formats can be analyzed with " +"a wide variety of off-the-shelf log-analysis packages. You should use one " +"of the standard event log formats unless you need information that these " +"formats do not provide. Refer to `Using the Custom Format`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:236 +msgid "Set standard log file format options by following the steps below:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:239 +msgid "Edit the following variables to use the Squid format:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:241 +msgid ":ts:cv:`proxy.config.log.squid_log_enabled`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:242 +msgid ":ts:cv:`proxy.config.log.squid_log_is_ascii`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:243 +msgid ":ts:cv:`proxy.config.log.squid_log_name`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:244 +msgid ":ts:cv:`proxy.config.log.squid_log_header`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:246 +msgid "To use the Netscape Common format, edit the following variables:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:248 +msgid ":ts:cv:`proxy.config.log.common_log_enabled`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:249 +msgid ":ts:cv:`proxy.config.log.common_log_is_ascii`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:250 +msgid ":ts:cv:`proxy.config.log.common_log_name`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:251 +msgid ":ts:cv:`proxy.config.log.common_log_header`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:253 +msgid "To use the Netscape Extended format, edit the following variables:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:255 +msgid ":ts:cv:`proxy.config.log.extended_log_enabled`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:256 +msgid ":ts:cv:`proxy.config.log.extended_log_is_ascii`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:257 +msgid ":ts:cv:`proxy.config.log.extended_log_name`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:258 +msgid ":ts:cv:`proxy.config.log.extended_log_header`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:260 +msgid "To use the Netscape Extended-2 format, edit the following variables:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:262 +msgid ":ts:cv:`proxy.config.log.extended2_log_enabled`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:263 +msgid ":ts:cv:`proxy.config.log.extended2_log_is_ascii`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:264 +msgid ":ts:cv:`proxy.config.log.extended2_log_name`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:265 +msgid ":ts:cv:`proxy.config.log.extended2_log_header`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:275 +msgid "Using the Custom Format" +msgstr "" + +#: ../../admin/working-log-files.en.rst:277 +msgid "" +"The XML-based custom log format is more flexible then the standard log file " +"formats and gives you more control over the type of information recorded in " +"log files. You should create a custom log format if you need data for " +"analysis that's not available in the standard formats. You can decide what " +"information to record for each Traffic Server transaction and create " +"filters that specify which transactions to log." +msgstr "" + +#: ../../admin/working-log-files.en.rst:284 +msgid "" +"The heart of the XML-based custom logging feature is the XML-based logging " +"configuration file (:file:`logs_xml.config`) that enables you to create " +"very modular descriptions of logging objects. The :file:`logs_xml.config` " +"file uses three types of objects to create custom log files, as detailed " +"below. To generate a custom log format, you must specify at least one " +"``LogObject`` definition (one log file is produced for each ``LogObject`` " +"definition)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:292 +msgid "" +"The ``LogFormat`` object defines the content of the log file using printf-" +"style format strings." +msgstr "" + +#: ../../admin/working-log-files.en.rst:294 +msgid "" +"The ``LogFilter`` object defines a filter so that you include or exclude " +"certain information from the log file." +msgstr "" + +#: ../../admin/working-log-files.en.rst:296 +msgid "" +"The ``LogObject`` object specifies all the information needed to produce a " +"log file." +msgstr "" + +#: ../../admin/working-log-files.en.rst:299 +msgid "The name of the log file. (required)" +msgstr "" + +#: ../../admin/working-log-files.en.rst:300 +msgid "" +"The format to be used (required). This can be a standard format (Squid or " +"Netscape) or" +msgstr "" + +#: ../../admin/working-log-files.en.rst:302 +msgid "" +"a previously-defined custom format (i.e., a previously-defined " +"``LogFormat`` object)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:304 +msgid "" +"The file mode: ``ASCII``, ``Binary``, or ``ASCII_PIPE``. The default is " +"``ASCII``. The ``ASCII_PIPE`` mode writes log entries to a UNIX-named pipe " +"(a buffer in memory); other processes can then read the data using standard " +"I/O functions. The advantage of this option is that Traffic Server does not " +"have to write to disk, which frees disk space and bandwidth for other " +"tasks. When the buffer is full, Traffic Server drops log entries and issues " +"an error message indicating how many entries were dropped. Because Traffic " +"Server only writes complete log entries to the pipe, only full records are " +"dropped." +msgstr "" + +#: ../../admin/working-log-files.en.rst:315 +msgid "" +"Any filters you want to use (i.e., previously-defined ``LogFilter`` " +"objects)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:317 +msgid "The collation servers that are to receive the log files." +msgstr "" + +#: ../../admin/working-log-files.en.rst:318 +msgid "" +"The protocols you want to log. If the protocols tag is used, then Traffic " +"Server will only log transactions from the protocols listed; otherwise, all " +"transactions for all protocols are logged." +msgstr "" + +#: ../../admin/working-log-files.en.rst:321 +msgid "" +"The origin servers you want to log. If the ``servers`` tag is used, then " +"Traffic Server will only log transactions for the origin servers listed; " +"otherwise, transactions for all origin servers are logged." +msgstr "" + +#: ../../admin/working-log-files.en.rst:325 +msgid "" +"The header text you want the log files to contain. The header text appears " +"at the beginning of the log file, just before the first record." +msgstr "" + +#: ../../admin/working-log-files.en.rst:328 +msgid "The log file rolling options." +msgstr "" + +#: ../../admin/working-log-files.en.rst:330 +msgid "In order to accomplish this, we" +msgstr "" + +#: ../../admin/working-log-files.en.rst:332 +msgid "edit the following variables in the :file:`records.config` file:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:334 +msgid ":ts:cv:`proxy.config.log.custom_logs_enabled`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:335 +msgid "In the :file:`logs_xml.config` file" +msgstr "" + +#: ../../admin/working-log-files.en.rst:337 +msgid "" +"Add :ref:`LogFormat`, :ref:`LogFilters`, and :ref:`LogObject` " +"specifications to the configuration file." +msgstr "" + +#: ../../admin/working-log-files.en.rst:339 +msgid "Save and close the :file:`logs_xml.config` file." +msgstr "" + +#: ../../admin/working-log-files.en.rst:340 +msgid "" +"Run the command :option:`traffic_line -x` to apply your configuration " +"changes." +msgstr "" + +#: ../../admin/working-log-files.en.rst:344 +msgid "Creating Summary Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:346 +msgid "" +"Traffic Server performs several hundred operations per second; therefore, " +"event log files can quickly grow to large sizes. Using SQL-like aggregate " +"operators, you can configure Traffic Server to create summary log files " +"that summarize a set of log entries over a specified period of time. This " +"can significantly reduce the size of the log files generated." +msgstr "" + +#: ../../admin/working-log-files.en.rst:353 +msgid "" +"To generate a summary log file, create a :ref:`LogFormat` object in the XML-" +"based logging configuration file (:file:`logs_xml.config`) using the SQL-" +"like aggregate operators below. You can apply each of these operators to " +"specific fields, over a specified interval." +msgstr "" + +#: ../../admin/working-log-files.en.rst:359 +msgid "``COUNT``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:360 +msgid "``SUM``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:361 +msgid "``AVERAGE``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:362 +msgid "``FIRST``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:363 +msgid "``LAST``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:365 +msgid "To create a summary log file format, we" +msgstr "" + +#: ../../admin/working-log-files.en.rst:367 +msgid "" +"Define the format of the log file in :file:`logs_xml.config` as follows:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:380 +msgid "" +"where ``operator`` is one of the five aggregate operators (``COUNT``, " +"``SUM``, ``AVERAGE``, ``FIRST``, ``LAST``), ``field`` is the logging field " +"you want to aggregate, and ``n`` is the interval (in seconds) between " +"summary log entries. You can specify more than one ``operator`` in the " +"format line. For more information, refer to :file`logs_xml.config`." +msgstr "" + +#: ../../admin/working-log-files.en.rst:387 +msgid "" +"Run the command :option:`traffic_line -x` to apply configuration changes ." +msgstr "" + +#: ../../admin/working-log-files.en.rst:389 +msgid "" +"The following example format generates one entry every 10 seconds. Each " +"entry contains the timestamp of the last entry of the interval, a count of " +"the number of entries seen within that 10-second interval, and the sum of " +"all bytes sent to the client: ::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:402 +msgid "" +"You cannot create a format specification that contains both aggregate " +"operators and regular fields. For example, the following specification " +"would be **invalid**: ::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:409 +msgid "Choosing Binary or ASCII" +msgstr "" + +#: ../../admin/working-log-files.en.rst:411 +msgid "" +"You can configure Traffic Server to create event log files in either of the " +"following:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:414 +msgid "**ASCII**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:416 +msgid "" +"These files are human-readable and can be processed using standard, off-the-" +"shelf log analysis tools. However, Traffic Server must perform additional " +"processing to create the files in ASCII, which mildly impacts system " +"overhead. ASCII files also tend to be larger than the equivalent binary " +"files. By default, ASCII log files have a ``.log`` filename extension." +msgstr "" + +#: ../../admin/working-log-files.en.rst:423 +msgid "**Binary**" +msgstr "" + +#: ../../admin/working-log-files.en.rst:425 +msgid "" +"These files generate lower system overhead and generally occupy less space " +"on the disk than ASCII files (depending on the type of information being " +"logged). However, you must use a converter application before you can read " +"or analyze binary files via standard tools. By default, binary log files " +"use a ``.blog`` filename extension." +msgstr "" + +#: ../../admin/working-log-files.en.rst:432 +msgid "" +"While binary log files typically require less disk space, there are " +"exceptions." +msgstr "" + +#: ../../admin/working-log-files.en.rst:435 +msgid "" +"For example: the value ``0`` (zero) requires only one byte to store in " +"ASCII, but requires four bytes when stored as a binary integer. Conversely: " +"if you define a custom format that logs IP addresses, then a binary log " +"file would only require four bytes of storage per 32-bit address. However, " +"the same IP address stored in dot notation would require around 15 " +"characters (bytes) in an ASCII log file. Therefore, it's wise to consider " +"the type of data that will be logged before you select ASCII or binary for " +"your log files. For example, you might try logging for one day using ASCII " +"and then another day using binary. If the number of requests is roughly the " +"same for both days, then you can calculate a rough metric that compares the " +"two formats." +msgstr "" + +#: ../../admin/working-log-files.en.rst:447 +msgid "" +"For standard log formats, select Binary or ASCII (refer to `Setting " +"Standard Log File Format Options`). For the custom log format, specify " +"ASCII or Binary mode in the :ref:`LogObject` (refer to :ref:`Using the " +"Custom Format `). In addition to the ASCII and " +"binary options, you can also write custom log entries to a UNIX-named pipe " +"(i.e., a buffer in memory). Other processes can then read the data using " +"standard I/O functions. The advantage of using this option is that Traffic " +"Server does not have to write to disk, which frees disk space and bandwidth " +"for other tasks. In addition, writing to a pipe does not stop when logging " +"space is exhausted because the pipe does not use disk space. Refer to :file:" +"`logs_xml.config` for more information about the ``ASCII_PIPE`` option." +msgstr "" + +#: ../../admin/working-log-files.en.rst:463 +msgid "Rolling Event Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:465 +msgid "" +"Traffic Server provides automatic log file rolling. This means that at " +"specific intervals during the day or when log files reach a certain size, " +"Traffic Server closes its current set of log files and opens new log files. " +"Depending on the amount of traffic your servers are exposed to, you should " +"roll log files several times a day. Rolling every six hours is a good " +"guideline to start with." +msgstr "" + +#: ../../admin/working-log-files.en.rst:472 +msgid "Log file rolling offers the following benefits:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:474 +msgid "It defines an interval over which log analysis can be performed." +msgstr "" + +#: ../../admin/working-log-files.en.rst:475 +msgid "" +"It keeps any single log file from becoming too large and helps to keep the " +"logging system within the specified space limits." +msgstr "" + +#: ../../admin/working-log-files.en.rst:477 +msgid "" +"It provides an easy way to identify files that are no longer being used so " +"that an automated script can clean the logging directory and run log " +"analysis programs." +msgstr "" + +#: ../../admin/working-log-files.en.rst:482 +msgid "Rolled Log Filename Format" +msgstr "" + +#: ../../admin/working-log-files.en.rst:484 +msgid "" +"Traffic Server provides a consistent naming scheme for rolled log files " +"that enables you to easily identify log files. When Traffic Server rolls a " +"log file, it saves and closes the old file before it starts a new file. " +"Traffic Server renames the old file to include the following information:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:490 +msgid "The format of the file (such as ``squid.log``)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:491 +msgid "The hostname of the Traffic Server that generated the log file." +msgstr "" + +#: ../../admin/working-log-files.en.rst:492 +msgid "" +"Two timestamps separated by a hyphen (``-``). The first timestamp is a " +"**lower bound** for the timestamp of the first record in the log file. The " +"lower bound is the time when the new buffer for log records is created. " +"Under low load, the first timestamp in the filename can be different from " +"the timestamp of the first entry. Under normal load, the first timestamp in " +"the filename and the timestamp of the first entry are similar. The second " +"timestamp is an **upper bound** for the timestamp of the last record in the " +"log file (this is normally the rolling time)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:501 +msgid "" +"The suffix ``.old``, which makes it easy for automated scripts to find " +"rolled log files." +msgstr "" + +#: ../../admin/working-log-files.en.rst:504 +msgid "Timestamps have the following format: ::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:508 +msgid "The following table describes the format:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:511 +msgid "``%Y``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:511 +msgid "The year in four-digit format. For example: 2000." +msgstr "" + +#: ../../admin/working-log-files.en.rst:514 +#: ../../admin/working-log-files.en.rst:523 +msgid "``%M``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:514 +msgid "The month in two-digit format, from 01-12. For example: 07." +msgstr "" + +#: ../../admin/working-log-files.en.rst:517 +msgid "``%D``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:517 +msgid "The day in two-digit format, from 01-31. For example: 19." +msgstr "" + +#: ../../admin/working-log-files.en.rst:520 +msgid "``%H``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:520 +msgid "The hour in two-digit format, from 00-23. For example: 21." +msgstr "" + +#: ../../admin/working-log-files.en.rst:523 +msgid "The minute in two-digit format, from 00-59. For example: 52." +msgstr "" + +#: ../../admin/working-log-files.en.rst:526 +msgid "``%S``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:526 +msgid "The second in two-digit format, from 00-59. For example: 36." +msgstr "" + +#: ../../admin/working-log-files.en.rst:528 +msgid "The following is an example of a rolled log filename: ::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:532 +msgid "" +"The logging system buffers log records before writing them to disk. When a " +"log file is rolled, the log buffer might be partially full. If it is, then " +"the first entry in the new log file will have a timestamp earlier than the " +"time of rolling. When the new log file is rolled, its first timestamp will " +"be a lower bound for the timestamp of the first entry." +msgstr "" + +#: ../../admin/working-log-files.en.rst:538 +msgid "" +"For example, suppose logs are rolled every three hours, and the first " +"rolled log file is: ::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:543 +msgid "" +"If the lower bound for the first entry in the log buffer at 3:00:00 is " +"2:59:47, then the next log file will have the following timestamp when " +"rolled: ::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:549 +msgid "" +"The contents of a log file are always between the two timestamps. Log files " +"do not contain overlapping entries, even if successive timestamps appear to " +"overlap." +msgstr "" + +#: ../../admin/working-log-files.en.rst:554 +msgid "Rolling Intervals" +msgstr "" + +#: ../../admin/working-log-files.en.rst:556 +msgid "" +"Log files are rolled at specific intervals relative to a given hour of the " +"day. Two options control when log files are rolled:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:559 +msgid "The offset hour, which is an hour between 0 (midnight) and 23" +msgstr "" + +#: ../../admin/working-log-files.en.rst:560 +msgid "The rolling interval" +msgstr "" + +#: ../../admin/working-log-files.en.rst:562 +msgid "" +"Both the offset hour and the rolling interval determine when log file " +"rolling starts. Rolling occurs every rolling interval and at the offset " +"hour. For example, if the rolling interval is six hours and the offset hour " +"is 0 (midnight), then the logs will roll at midnight (00:00), 06:00, 12:00, " +"and 18:00 each day. If the rolling interval is 12 hours and the offset hour " +"is 3, then logs will roll at 03:00 and 15:00 each day." +msgstr "" + +#: ../../admin/working-log-files.en.rst:571 +msgid "Setting Log File Rolling Options" +msgstr "" + +#: ../../admin/working-log-files.en.rst:573 +msgid "" +"To set log file rolling options and/or configure Traffic Server to roll log " +"files when they reach a certain size, follow the steps below:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:578 +msgid ":ts:cv:`proxy.config.log.rolling_enabled`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:579 +msgid ":ts:cv:`proxy.config.log.rolling_size_mb`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:580 +msgid ":ts:cv:`proxy.config.log.rolling_offset_hr`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:581 +msgid ":ts:cv:`proxy.config.log.rolling_interval_sec`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:586 +msgid "" +"You can fine-tune log file rolling settings for a custom log file in the :" +"ref:`LogObject` specification in the :file:`logs_xml.config` file. The " +"custom log file uses the rolling settings in its :ref:`LogObject`, which " +"override the default settings you specify in Traffic Manager or the :file:" +"`records.config` file described above." +msgstr "" + +#: ../../admin/working-log-files.en.rst:596 +msgid "Splitting Event Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:598 +msgid "" +"By default, Traffic Server uses standard log formats and generates log " +"files that contain HTTP & ICP transactions in the same file. However, you " +"can enable log splitting if you prefer to log transactions for different " +"protocols in separate log files." +msgstr "" + +#: ../../admin/working-log-files.en.rst:604 +msgid "ICP Log Splitting" +msgstr "" + +#: ../../admin/working-log-files.en.rst:606 +msgid "" +"When ICP log splitting is enabled, Traffic Server records ICP transactions " +"in a separate log file with a name that contains ``icp``. For example: if " +"you enable the Squid format, then all ICP transactions are recorded in the " +"``squid-icp.log`` file. When you disable ICP log splitting, Traffic Server " +"records all ICP transactions in the same log file as HTTP transactions." +msgstr "" + +#: ../../admin/working-log-files.en.rst:614 +msgid "HTTP Host Log Splitting" +msgstr "" + +#: ../../admin/working-log-files.en.rst:616 +msgid "" +"HTTP host log splitting enables you to record HTTP transactions for " +"different origin servers in separate log files. When HTTP host log " +"splitting is enabled, Traffic Server creates a separate log file for each " +"origin server that's listed in the :file:`log_hosts.config` file. When both " +"ICP and HTTP host log splitting are enabled, Traffic Server generates " +"separate log files for HTTP transactions (based on the origin server) and " +"places all ICP transactions in their own respective log files. For example, " +"if the :file:`log_hosts.config` file contains the two origin servers ``uni." +"edu`` and ``company.com`` and Squid format is enabled, then Traffic Server " +"generates the following log files:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:628 +#: ../../admin/working-log-files.en.rst:644 +msgid "``squid-uni.edu.log``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:628 +msgid "All HTTP transactions for ``uni.edu``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:631 +#: ../../admin/working-log-files.en.rst:647 +msgid "``squid-company.com.log``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:631 +msgid "All HTTP transactions for ``company.com``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:634 +msgid "``squid-icp.log``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:634 +msgid "All ICP transactions for all hosts" +msgstr "" + +#: ../../admin/working-log-files.en.rst:637 +#: ../../admin/working-log-files.en.rst:650 +msgid "``squid.log``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:637 +msgid "All HTTP transactions for other hosts" +msgstr "" + +#: ../../admin/working-log-files.en.rst:639 +msgid "" +"If you disable ICP log splitting, then ICP transactions are placed in the " +"same log file as HTTP transactions. Using the hosts and log format from the " +"previous example, Traffic Server generates the log files below:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:644 +msgid "All entries for ``uni.edu``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:647 +msgid "All entries for ``company.com``" +msgstr "" + +#: ../../admin/working-log-files.en.rst:650 +msgid "All other entries" +msgstr "" + +#: ../../admin/working-log-files.en.rst:652 +msgid "" +"Traffic Server also enables you to create XML-based :ref:`Custom Log " +"Formats ` that offer even greater control over " +"log file generation." +msgstr "" + +#: ../../admin/working-log-files.en.rst:656 +msgid "Setting Log Splitting Options" +msgstr "" + +#: ../../admin/working-log-files.en.rst:658 +msgid "To set log splitting options, follow the steps below:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:662 +msgid ":ts:cv:`proxy.config.log.separate_icp_logs`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:663 +msgid ":ts:cv:`proxy.config.log.separate_host_logs`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:669 +msgid "Editing the log_hosts.config File" +msgstr "" + +#: ../../admin/working-log-files.en.rst:671 +msgid "" +"The default :file:`log_hosts.config` file is located in the Traffic Server " +"``config`` directory. To record HTTP transactions for different origin " +"servers in separate log files, you must specify the hostname of each origin " +"server on a separate line in the :file:`log_hosts.config` file. For " +"example, if you specify the keyword sports, then Traffic Server records all " +"HTTP transactions from ``sports.yahoo.com`` and ``www.foxsports.com`` in a " +"log file called ``squid-sports.log`` (if the Squid format is enabled)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:682 +msgid "" +"If Traffic Server is clustered and you enable log file collation, then you " +"should use the same :file:`log_hosts.config` file on every Traffic Server " +"node in the cluster." +msgstr "" + +#: ../../admin/working-log-files.en.rst:686 +msgid "To edit the :file:`log_hosts.config` file follow the steps below:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:688 +msgid "" +"In the :file:`log_hosts.config` file, enter the hostname of each origin " +"server on a separate line in the file, e.g.: ::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:700 +msgid "Collating Event Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:702 +msgid "" +"You can use the Traffic Server log file collation feature to collect all " +"logged information in one place. Log collation enables you to analyze a set " +"of Traffic Server clustered nodes as a whole (rather than as individual " +"nodes) and to use a large disk that might only be located on one of the " +"nodes in the cluster. Traffic Server collates log files by using one or " +"more nodes as log collation servers and all remaining nodes as log " +"collation clients. When a Traffic Server node generates a buffer of event " +"log entries, it first determines if it is the collation server or a " +"collation client. The collation server node writes all log buffers to its " +"local disk, just as it would if log collation was not enabled. Log " +"collation servers can be standalone or they can be part of a node running " +"Traffic Server." +msgstr "" + +#: ../../admin/working-log-files.en.rst:715 +msgid "" +"The collation client nodes prepare their log buffers for transfer across " +"the network and send the buffers to the log collation server. When the log " +"collation server receives a log buffer from a client, it writes it to its " +"own log file as if it was generated locally. For a visual representation of " +"this, see the figure below." +msgstr "" + +#: ../../admin/working-log-files.en.rst:725 +msgid "Log collation" +msgstr "" + +#: ../../admin/working-log-files.en.rst:727 +msgid "" +"If log clients cannot contact their log collation server, then they write " +"their log buffers to their local disks, into *orphan* log files. Orphan log " +"files require manual collation." +msgstr "" + +#: ../../admin/working-log-files.en.rst:733 +msgid "" +"Log collation can have an impact on network performance. Because all nodes " +"are forwarding their log data buffers to the single collation server, a " +"bottleneck can occur. In addition, collated log files contain timestamp " +"information for each entry, but entries in the files do not appear in " +"strict chronological order. You may want to sort collated log files before " +"doing analysis." +msgstr "" + +#: ../../admin/working-log-files.en.rst:740 +msgid "" +"To configure Traffic Server to collate event log files, you must perform " +"the following tasks:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:743 +msgid "" +"Either `Configure Traffic Server Node to Be a Collation Server `_ or install & configure a " +"`Standalone Collator `_" +msgstr "" + +#: ../../admin/working-log-files.en.rst:746 +msgid "" +"`Configure Traffic Server Nodes to Be a Collation Clients `_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:748 +msgid "" +"Add an attribute to the :ref:`LogObject` specification in the :file:" +"`logs_xml.config` file if you are using custom log file formats; refer to " +"`Collating Custom Event Log Files`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:756 +msgid "Configuring Traffic Server to Be a Collation Server" +msgstr "" + +#: ../../admin/working-log-files.en.rst:758 +msgid "" +"To configure a Traffic Server node to be a collation server, simply edit a " +"configuration file via the steps below." +msgstr "" + +#: ../../admin/working-log-files.en.rst:761 +msgid "In the :file:`records.config` file, edit the following variables" +msgstr "" + +#: ../../admin/working-log-files.en.rst:763 +msgid ":ts:cv:`proxy.local.log.collation_mode` (``1`` for server mode)" +msgstr "" + +#: ../../admin/working-log-files.en.rst:764 +#: ../../admin/working-log-files.en.rst:829 +msgid ":ts:cv:`proxy.config.log.collation_port`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:765 +#: ../../admin/working-log-files.en.rst:830 +msgid ":ts:cv:`proxy.config.log.collation_secret`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:772 +msgid "" +"If you modify the ``collation_port`` or ``secret`` after connections " +"between the collation server and collation clients have been established, " +"then you must restart Traffic Server." +msgstr "" + +#: ../../admin/working-log-files.en.rst:777 +msgid "Using a Standalone Collator" +msgstr "" + +#: ../../admin/working-log-files.en.rst:779 +msgid "" +"If you do not want the log collation server to be a Traffic Server node, " +"then you can install and configure a standalone collator (SAC) that will " +"dedicate more of its power to collecting, processing, and writing log files." +msgstr "" + +#: ../../admin/working-log-files.en.rst:784 +msgid "To install and configure a standalone collator:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:786 +msgid "" +"Configure your Traffic Server nodes as log collation clients; refer to " +"`Configuring Traffic Server to Be a Collation Client " +"<#ConfiguringTSCollationClient>`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:789 +msgid "" +"Copy the :program:`traffic_sac` binary from the Traffic Server ``bin`` " +"directory and" +msgstr "" + +#: ../../admin/working-log-files.en.rst:791 +msgid "" +"Copy the ``libtsutil.so`` libraries from the Traffic Server ``lib`` " +"directory to the machine serving as the standalone collator." +msgstr "" + +#: ../../admin/working-log-files.en.rst:793 +msgid "" +"Create a directory called ``config`` in the directory that contains the :" +"program:`traffic_sac` binary." +msgstr "" + +#: ../../admin/working-log-files.en.rst:795 +msgid "" +"Create a directory called ``internal`` in the ``config`` directory you " +"created in Step 4 (above). This directory is used internally by the " +"standalone collator to store lock files." +msgstr "" + +#: ../../admin/working-log-files.en.rst:798 +msgid "" +"Copy the :file:`records.config` file from a Traffic Server node configured " +"to be a log collation client to the ``config`` directory you created in " +"Step 4 on the standalone collator. The :file:`records.config` file contains " +"the log collation secret and the port you specified when configuring " +"Traffic Server nodes to be collation clients. The collation port and secret " +"must be the same for all collation clients and servers." +msgstr "" + +#: ../../admin/working-log-files.en.rst:805 +msgid "In the :file:`records.config` file, edit the following variable" +msgstr "" + +#: ../../admin/working-log-files.en.rst:810 +msgid "Enter the following command::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:815 +msgid "Configuring Traffic Server to Be a Collation Client" +msgstr "" + +#: ../../admin/working-log-files.en.rst:817 +msgid "" +"To configure a Traffic Server node to be a collation client, follow the " +"steps below. If you modify the ``collation_port`` or ``secret`` after " +"connections between the collation clients and the collation server have " +"been established, then you must restart Traffic Server." +msgstr "" + +#: ../../admin/working-log-files.en.rst:822 +msgid "In the :file:`records.config` file, edit the following variables:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:824 +msgid "" +":ts:cv:`proxy.local.log.collation_mode`: ``2`` to configure this node as " +"log collation client and send standard formatted log entries to the " +"collation server. For XML-based formatted log entries, see :file:`logs_xml." +"config` file; refer to :ref:`Using the Custom Format `." +msgstr "" + +#: ../../admin/working-log-files.en.rst:828 +msgid ":ts:cv:`proxy.config.log.collation_host`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:831 +msgid ":ts:cv:`proxy.config.log.collation_host_tagged`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:832 +msgid ":ts:cv:`proxy.config.log.max_space_mb_for_orphan_logs`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:838 +msgid "Collating Custom Event Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:840 +msgid "" +"If you use custom event log files, then you must edit the :file:`logs_xml." +"config` file (in addition to configuring a collation server and collation " +"clients)." +msgstr "" + +#: ../../admin/working-log-files.en.rst:844 +msgid "To collate custom event log files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:846 +msgid "On each collation client, edit the `:file:`logs_xml.config`" +msgstr "" + +#: ../../admin/working-log-files.en.rst:847 +msgid "" +"Add the :ref:`CollationHost ` attribute " +"to the :ref:`LogObject` specification: ::" +msgstr "" + +#: ../../admin/working-log-files.en.rst:858 +msgid "" +"where ``ipaddress`` is the hostname or IP address of the collation server " +"to which all log entries (for this object) are forwarded, and ``port`` is " +"the port number for communication between the collation server and " +"collation clients." +msgstr "" + +#: ../../admin/working-log-files.en.rst:863 +msgid "" +"Run the command :option:`traffic_line -L` to restart Traffic Server on the " +"local node or :option:`traffic_line -M` to restart Traffic Server on all " +"the nodes in a cluster." +msgstr "" + +#: ../../admin/working-log-files.en.rst:868 +msgid "Viewing Logging Statistics" +msgstr "" + +#: ../../admin/working-log-files.en.rst:870 +msgid "" +"Traffic Server generates logging statistics that enable you to see the " +"following information:" +msgstr "" + +#: ../../admin/working-log-files.en.rst:873 +msgid "How many log files (formats) are currently being written." +msgstr "" + +#: ../../admin/working-log-files.en.rst:874 +msgid "" +"The current amount of space used by the logging directory, which contains " +"all event and error logs." +msgstr "" + +#: ../../admin/working-log-files.en.rst:876 +msgid "" +"The number of access events written to log files since Traffic Server " +"installation. This counter represents one entry in one file; if multiple " +"formats are being written, then a single event creates multiple event log " +"entries." +msgstr "" + +#: ../../admin/working-log-files.en.rst:880 +msgid "" +"The number of access events skipped (because they were filtered) since " +"Traffic Server installation." +msgstr "" + +#: ../../admin/working-log-files.en.rst:882 +msgid "" +"The number of access events written to the event error log since Traffic " +"Server installation." +msgstr "" + +#: ../../admin/working-log-files.en.rst:885 +msgid "" +"You can retrieve the statistics via the Traffic Line command-line " +"interface; refer to `Monitoring Traffic <../monitoring-traffic>`_." +msgstr "" + +#: ../../admin/working-log-files.en.rst:889 +msgid "Viewing Log Files" +msgstr "" + +#: ../../admin/working-log-files.en.rst:891 +msgid "" +"You can view the system, event, and error log files Traffic Server creates. " +"You can also delete a log file or copy it to your local system if you have " +"the correct user permissions. Traffic Server displays only one MB of " +"information in the log file. If the log file you select to view is bigger " +"than 1MB, then Traffic Server truncates the file and displays a warning " +"message indicating that the file is too big." +msgstr "" + +#: ../../admin/working-log-files.en.rst:899 +msgid "Online Event Log XML Builder" +msgstr "" + +#: ../../admin/working-log-files.en.rst:901 +msgid "" +"If you need any assistance building your event log, you can try out our " +"`online log builder `_. This " +"is a work in progress, so any comments, critique or suggestions are most " +"welcome." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po b/doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po new file mode 100644 index 00000000000..78f930000dd --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po @@ -0,0 +1,530 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../admin/working-log-files/log-formats.en.rst:4 +msgid "Log Formats" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:26 +msgid "Squid Format" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:32 +#: ../../admin/working-log-files/log-formats.en.rst:115 +msgid "``1``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:29 +msgid "" +"``cqtq`` The client request timestamp in Squid format; the time of the " +"client request in seconds since January 1, 1970 UTC (with millisecond " +"resolution)." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:39 +#: ../../admin/working-log-files/log-formats.en.rst:119 +msgid "``2``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:35 +msgid "" +"``ttms`` The time Traffic Server spent processing the client request; the " +"number of milliseconds between the time the client established the " +"connection with Traffic Server and the time Traffic Server sent the last " +"byte of the response back to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:43 +#: ../../admin/working-log-files/log-formats.en.rst:124 +msgid "``3``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:42 +#: ../../admin/working-log-files/log-formats.en.rst:114 +msgid "``chi`` The IP address of the client’s host machine." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:51 +#: ../../admin/working-log-files/log-formats.en.rst:128 +msgid "``4``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:46 +msgid "" +"``crc/pssc`` The cache result code; how the cache responded to the request: " +"``HIT``, ``MISS``, and so on. Cache result codes are described :ref:`here " +"`. The proxy response status code (the HTTP " +"response status code from Traffic Server to client)." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:56 +#: ../../admin/working-log-files/log-formats.en.rst:132 +msgid "``5``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:54 +msgid "" +"``psql`` The length of the Traffic Server response to the client in bytes, " +"including headers and content." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:60 +#: ../../admin/working-log-files/log-formats.en.rst:136 +msgid "``6``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:59 +msgid "``cqhm`` The client request method: ``GET``, ``POST``, and so on." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:67 +#: ../../admin/working-log-files/log-formats.en.rst:140 +msgid "``7``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:63 +msgid "" +"``cquc`` The client request canonical URL; blanks and other characters that " +"might not be parsed by log analysis tools are replaced by escape sequences. " +"The escape sequence is a percentage sign followed by the ASCII code number " +"of the replaced character in hex." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:72 +#: ../../admin/working-log-files/log-formats.en.rst:147 +msgid "``8``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:70 +msgid "" +"``caun`` The username of the authenticated client. A hyphen (``-``) means " +"that no authentication was required." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:81 +#: ../../admin/working-log-files/log-formats.en.rst:152 +msgid "``9``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:75 +msgid "" +"``phr/pqsn`` The proxy hierarchy route; the route Traffic Server used to " +"retrieve the object." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:79 +msgid "" +"The proxy request server name; the name of the server that fulfilled the " +"request. If the request was a cache hit, then this field contains a hyphen " +"(``-``)." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:86 +#: ../../admin/working-log-files/log-formats.en.rst:157 +msgid "``10``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:84 +msgid "" +"``psct`` The proxy response content type; the object content type taken " +"from the Traffic Server response header." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:88 +msgid "The following figure shows a sample log entry in a ``squid.log`` file." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:94 +msgid "Sample log entry in squid.log" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:97 +msgid "Squid log in XML" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:108 +msgid "Netscape Formats" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:111 +#: ../../admin/working-log-files/log-formats.en.rst:218 +msgid "Netscape Common" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:118 +msgid "``-`` This hyphen (``-``) is always present in Netscape log entries." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:122 +msgid "" +"``caun`` The authenticated client username. A hyphen (``-``) means no " +"authentication was required." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:127 +msgid "" +"``cqtd`` The date and time of the client request, enclosed in brackets." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:131 +msgid "``cqtx`` The request line, enclosed in quotes." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:135 +msgid "``pssc`` The proxy response status code (HTTP reply code)." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:139 +msgid "" +"``pscl`` The length of the Traffic Server response to the client in bytes." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:143 +#: ../../admin/working-log-files/log-formats.en.rst:240 +msgid "Netscape Extended" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:146 +msgid "``sssc`` The origin server response status code." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:150 +msgid "" +"``sshl`` The server response transfer length; the body length in the origin " +"server response to Traffic Server, in bytes." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:155 +msgid "" +"``cqbl`` The client request transfer length; the body length in the client " +"request to Traffic Server, in bytes." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:162 +msgid "``11``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:160 +msgid "" +"``pqbl`` The proxy request transfer length; the body length in the Traffic " +"Server request to the origin server." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:167 +msgid "``12``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:165 +msgid "" +"``cqhl`` The client request header length; the header length in the client " +"request to Traffic Server." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:172 +msgid "``13``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:170 +msgid "" +"``pshl`` The proxy response header length; the header length in the Traffic " +"Server response to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:177 +msgid "``14``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:175 +msgid "" +"``pqhl`` The proxy request header length; the header length in Traffic " +"Server request to the origin server." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:182 +msgid "``15``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:180 +msgid "" +"``sshl`` The server response header length; the header length in the origin " +"server response to Traffic Server." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:189 +msgid "``16``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:185 +msgid "" +"``tts`` The time Traffic Server spent processing the client request; the " +"number of seconds between the time that the client established the " +"connection with Traffic Server and the time that Traffic Server sent the " +"last byte of the response back to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:192 +#: ../../admin/working-log-files/log-formats.en.rst:263 +msgid "Netscape Extended2" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:197 +msgid "``17``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:195 +msgid "" +"``phr`` The proxy hierarchy route; the route Traffic Server used to " +"retrieve the object." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:203 +msgid "``18``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:200 +msgid "" +"``cfsc`` The client finish status code: ``FIN`` if the client request " +"completed successfully or ``INTR`` if the client request was interrupted." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:209 +msgid "``19``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:206 +msgid "" +"``pfsc`` The proxy finish status code: ``FIN`` if the Traffic Server " +"request to the origin server completed successfully or ``INTR`` if the " +"request was interrupted." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:215 +msgid "``20``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:212 +msgid "" +"``crc`` The cache result code; how the Traffic Server cache responded to " +"the request: HIT, MISS, and so on. Cache result codes are described :ref:" +"`here `." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:220 +msgid "" +"The following figure shows a sample log entry in a ``common.log`` file, the " +"list following describes the fields of the format." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:227 +msgid "Sample log entry in common.log" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:230 +msgid "Netscape Common in XML" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:242 +msgid "" +"The following figure shows a sample log entry in an ``extended.log`` file." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:249 +msgid "sample log entry in extended.log" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:252 +#: ../../admin/working-log-files/log-formats.en.rst:275 +msgid "Netscape Extended in XML" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:265 +msgid "" +"The following figure shows a sample log entry in an ``extended2.log`` file." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:272 +msgid "sample log entry in extended2.log" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:288 +msgid "Squid- and Netscape-format: Cache Result Codes" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:290 +msgid "" +"The following table describes the cache result codes in Squid and Netscape " +"log files." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:295 +msgid "``TCP_HIT``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:294 +msgid "" +"A valid copy of the requested object was in the cache and Traffic Server " +"sent the object to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:300 +msgid "``TCP_MISS``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:298 +msgid "" +"The requested object was not in cache, so Traffic Server retrieved the " +"object from the origin server (or a parent proxy) and sent it to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:306 +msgid "``TCP_REFRESH_HIT``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:303 +msgid "" +"The object was in the cache, but it was stale. Traffic Server made an ``if-" +"modified-since`` request to the origin server and the origin server sent a " +"``304`` not-modified response. Traffic Server sent the cached object to the " +"client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:312 +msgid "``TCP_REF_FAIL_HIT``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:309 +msgid "" +"The object was in the cache but was stale. Traffic Server made an ``if-" +"modified-since`` request to the origin server but the server did not " +"respond. Traffic Server sent the cached object to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:318 +msgid "``TCP_REFRESH_MISS``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:315 +msgid "" +"The object was in the cache but was stale. Traffic Server made an ``if-" +"modified-since`` request to the origin server and the server returned a new " +"object. Traffic Server served the new object to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:324 +msgid "``TCP_CLIENT_REFRESH``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:321 +msgid "" +"The client issued a request with a ``no-cache`` header. Traffic Server " +"obtained the requested object from the origin server and sent a copy to the " +"client. Traffic Server deleted the previous copy of the object from cache." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:331 +msgid "``TCP_IMS_HIT``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:327 +msgid "" +"The client issued an ``if-modified-since`` request and the object was in " +"cache & fresher than the IMS date, **or** an ``if-modified-since`` request " +"to the origin server revealed the cached object was fresh. Traffic Server " +"served the cached object to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:338 +msgid "``TCP_IMS_MISS``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:334 +msgid "" +"The client issued an ``if-modified-since request``, and the object was " +"either not in cache or was stale in cache. Traffic Server sent an ``if-" +"modified-since request`` to the origin server and received the new object. " +"Traffic Server sent the updated object to the client." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:342 +msgid "``TCP_SWAPFAIL``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:341 +msgid "" +"The object was in the cache but could not be accessed. The client did not " +"receive the object." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:345 +msgid "``ERR_CLIENT_ABORT``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:345 +msgid "The client disconnected before the complete object was sent." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:348 +msgid "``ERR_CONNECT_FAIL``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:348 +msgid "Traffic Server could not reach the origin server." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:352 +msgid "``ERR_DNS_FAIL``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:351 +msgid "" +"The Domain Name Server (DNS) could not resolve the origin server name, or " +"no DNS could be reached." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:356 +msgid "``ERR_INVALID_REQ``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:355 +msgid "" +"The client HTTP request was invalid. (Traffic Server forwards requests with " +"unknown methods to the origin server.)" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:360 +msgid "``ERR_READ_TIMEOUT``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:359 +msgid "" +"The origin server did not respond to Traffic Server's request within the " +"timeout interval." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:363 +msgid "``ERR_PROXY_DENIED``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:363 +msgid "Client service was denied." +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:368 +msgid "``ERR_UNKNOWN``" +msgstr "" + +#: ../../admin/working-log-files/log-formats.en.rst:366 +msgid "" +"The client connected, but subsequently disconnected without sending a " +"request." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po new file mode 100644 index 00000000000..605146e9dab --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po @@ -0,0 +1,48 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/cache/cache-api.en.rst:22 +msgid "Cache Related API functions" +msgstr "" + +#: ../../arch/cache/cache-api.en.rst:26 +msgid "" +"Set a *flag* that marks a request as cacheable. This is a positive override " +"only, setting *flag* to 0 restores the default behavior, it does not force " +"the request to be uncacheable." +msgstr "" + +#: ../../arch/cache/cache-api.en.rst:30 +msgid "" +"Set the cache key for the transaction *txnp* as the string pointed at by " +"*url* of *length* characters. It need not be ``null`` terminated. This " +"should be called from ``TS_HTTP_READ_REQUEST_HDR_HOOK`` which is before " +"cache lookup but late enough that the HTTP request header is available." +msgstr "" + +#: ../../arch/cache/cache-api.en.rst:34 +msgid "Cache Internals" +msgstr "" + +#: ../../arch/cache/cache-api.en.rst:38 +msgid "" +"A preprocessor macro which computes the maximum size of a fragment based on " +"the value of *big*. This is computed as if the argument where the value of " +"the *big* field in a struct :cpp:class:`Dir`." +msgstr "" + +#: ../../arch/cache/cache-api.en.rst:42 +msgid "" +"A preprocessor macro which computes the block size multiplier for a struct :" +"cpp:class:`Dir` where *big* is the *big* field value." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po new file mode 100644 index 00000000000..78e00e00ca1 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po @@ -0,0 +1,238 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/cache/cache-appendix.en.rst:21 +msgid "Cache Tools" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:23 +msgid "Tools and techniques for cache monitoring and inspection." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:25 +msgid ":ref:`The cache inspector `." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:28 +msgid "Topics to be done" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:30 +msgid "Resident alternates" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:31 +msgid "Object refresh" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:34 +msgid "Cache Consistency" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:36 +msgid "" +"The cache is completely consistent, up to and including kicking the power " +"cord out, if the write buffer on consumer disk drives is disabled. You need " +"to use::" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:40 +msgid "" +"The cache validates that all the data for the document is available and " +"will silently mark a partial document as a \"miss\" on read. There is no " +"\"gentle\" shutdown for traffic server, you just kill the process, so the " +"\"recovery\" code (fsck) is run every time traffic server starts up." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:42 +msgid "" +"On startup the two versions of the index are checked, and the last valid " +"one is read into memory. Then traffic server moves forward from the last " +"snapped write cursor and reads all the fragments written to disk, and " +"updates the directory (as in a log-based file system). It stops reading at " +"the write before the last valid write header it sees (as a write is not " +"necessarily atomic because of sector reordering). Then the new updated " +"index is written to the invalid version (in case of a crash during startup) " +"and the system starts." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:47 +msgid "Volume Tagging" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:49 +msgid "" +"Currently cache volumes are allocated somewhat arbitrarily from storage " +"elements. `This enhancement `__ allows the :file:`storage.config` file to assign storage units " +"to specific volumes although the volumes must still be listed in :file:" +"`volume.config` in general and in particular to map domains to specific " +"volumes. A primary use case for this is to be able to map specific types of " +"content to different storage elements. This could to have different storage " +"devices for the content (SSD vs. rotational)." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:53 +msgid "Version Upgrade" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:55 +msgid "" +"It is currently the case that any change to the cache format will clear the " +"cache. This is an issue when upgrading the |TS| version and should be kept " +"in mind." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:61 +msgid "Controlling the cache key" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:63 +msgid "" +"The cache key is by default the URL of the request. There are two possible " +"choices, the original (\"pristine\") URL and the remapped URL. Which of " +"these is used is determined by the configuration value :ts:cv:`proxy." +"config.url_remap.pristine_host_hdr`." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:65 +msgid "" +"This is an ``INT`` value. If set to ``0`` (disabled) then the remapped URL " +"is used, and if it is not ``0`` (enabled) then the original URL is used. " +"This setting also controls the value of the ``HOST`` header that is placed " +"in the request sent to the origin server, using hostname from the original " +"URL if non-``0`` and the host name from the remapped URL if ``0``. It has " +"no other effects." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:67 +msgid "" +"For caching, this setting is irrelevant if no remapping is done or there is " +"a one to one mapping between the original and remapped URLs." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:69 +msgid "" +"It becomes significant if multiple original URLs are mapped to the same " +"remapped URL. If pristine headers are enabled requests to different " +"original URLs will be stored as distinct objects in the cache. If disabled " +"the remapped URL will be used and there may be collisions. This is bad if " +"the contents different but quite useful if they are the same (e.g., the " +"original URLs are just aliases for the same underlying server)." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:71 +msgid "" +"This is also an issue if a remapping is changed because it is effectively a " +"time axis version of the previous case. If an original URL is remapped to a " +"different server address then the setting determines if existing cached " +"objects will be served for new requests (enabled) or not (disabled). " +"Similarly if the original URL mapped to a particular URL is changed then " +"cached objects from the initial original URL will be served from the " +"updated original URL if pristine headers is disabled." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:77 +msgid "" +"A plugin that changes the cache key *must* do so consistently for both " +"cache hit and cache miss requests because two different requests that map " +"to the same cache key will be considered equivalent by the cache. Use of " +"the URL directly provides this and so must any substitute. This is entirely " +"the responsibility of the plugin, there is no way for the |TS| core to " +"detect such an occurrence." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:81 +msgid "" +"It is a requirement that the string be syntactically a URL but otherwise it " +"is completely arbitrary and need not have any path. For instance if the " +"company Network Geographics wanted to store certain content under its own " +"cache key, using a document GUID as part of the key, it could use a cache " +"key like ::" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:85 +msgid "" +"The scheme ``ngeo`` was picked because it is *not* a valid URL scheme and " +"so will not collide with any valid URL." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:87 +msgid "" +"This can be useful if the URL encodes both important and unimportant data. " +"Instead of storing potentially identical content under different URLs " +"(because they differ on the unimportant parts) a url containing only the " +"important parts could be created and used." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:89 +msgid "" +"For example, suppose the URL for Network Geographics content encoded both " +"the document GUID and a referral key. ::" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:93 +msgid "" +"We don't want to the same content for every possible referrer. Instead we " +"could use a plugin to convert this to the previous example and requests " +"that differed only in the referrer key would all reference the same cache " +"entry. Note that we would also map ::" +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:97 +msgid "" +"to the same cache key. This can be handy for \"sharing\" content between " +"servers when that content is identical. Note also the plugin can change the " +"cache key or not depending on any data in the request header, for instance " +"not changing the cache key if the request is not in the ``doc`` directory. " +"If distinguishing servers is important that can easily be pulled from the " +"request URL and used in the synthetic cache key. The implementor is free to " +"extract all relevant elements for use in the cache key." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:99 +msgid "" +"While there is explicit no requirement that the synthetic cache key be " +"based on the HTTP request header, in practice it is generally necessary due " +"to the consistency requirement. Because cache lookup happens before " +"attempting to connect to the origin server no data from the HTTP response " +"header is available, leaving only the request header. The most common case " +"is the one described above where the goal is to elide elements of the URL " +"that do not affect the content to minimize cache footprint and improve " +"cache hit rates." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:73 +msgid "" +"These collisions are not of themselves good or bad. An administrator needs " +"to decide which is appropriate for their situation and set the value " +"correspondingly." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:75 +msgid "" +"If a greater degree of control is desired a plugin must be used to invoke " +"the API call :c:func:`TSCacheUrlSet()` to provide a specific cache key. " +"The :c:func:`TSCacheUrlSet()` API can be called as early as " +"``TS_HTTP_READ_REQUEST_HDR_HOOK``, but no later than " +"``TS_HTTP_POST_REMAP_HOOK``. It can be called only once per transaction; " +"calling it multiple times has no additional effect." +msgstr "" + +#: ../../arch/cache/cache-appendix.en.rst:79 +msgid "" +"If :c:func:`TSHttpTxnCacheLookupUrlGet()` is called after new cache url set " +"by :c:func:`TSCacheUrlSet()`, it should use a URL location created by :c:" +"func:`TSUrlCreate()` as its 3rd input parameter instead of getting url_loc " +"from client request." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/cache-arch.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-arch.en.po new file mode 100644 index 00000000000..574da8537fa --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-arch.en.po @@ -0,0 +1,2091 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/cache/cache-arch.en.rst:19 +msgid "Cache Architecture" +msgstr "キャッシュアーキテクチャ" + +#: ../../arch/cache/cache-arch.en.rst:24 +msgid "Introduction" +msgstr "導入" + +#: ../../arch/cache/cache-arch.en.rst:31 +msgid "" +"The purpose of this document is to describe the basic structure and " +"implementation details of the |TS| cache. Configuration of the cache will " +"be discussed only to the extent needed to understand the internal " +"mechanisms. This document will be useful primarily to |TS| developers " +"working on the |TS| codebase or plugins for |TS|. It is assumed the reader " +"is already familiar with the :ref:`admin-guide` and specifically with :ref:" +"`http-proxy-caching` and :ref:`configuring-the-cache` along with the " +"associated configuration files and values." +msgstr "" +"このドキュメントの目的は、 |TS| キャッシュの基本構造と実装の詳細について記述" +"することです。キャッシュの設定については、内部の仕組みを理解するのに必要な範" +"囲でのみ記述します。このドキュメントは、主に |TS| のコードや |TS| のプラグイ" +"ンに関わる |TS| デベロッパーにとって有用となるでしょう。読者は、 :ref:" +"`admin-guide` と、特に :ref:`http-proxy-caching` と :ref:`configuring-the-" +"cache` 、加えて設定ファイルや設定値に詳しいことを前提とします。" + +#: ../../arch/cache/cache-arch.en.rst:37 +msgid "" +"Unfortunately the internal terminology is not particularly consistent so " +"this document will frequently use terms in different ways than they are " +"used in the code in an attempt to create some consistency." +msgstr "" +"不幸なことに、内部用語は一貫していません。そのためこのドキュメントにおいては" +"一貫性を得るためにコード内で使われるものとは違った方法で頻繁に用語を使用しま" +"す。" + +#: ../../arch/cache/cache-arch.en.rst:41 +msgid "Cache Layout" +msgstr "キャッシュレイアウト" + +#: ../../arch/cache/cache-arch.en.rst:48 +msgid "Cache storage" +msgstr "キャッシュストレージ" + +#: ../../arch/cache/cache-arch.en.rst:56 +msgid "Two cache spans" +msgstr "二つのキャッシュスパン" + +#: ../../arch/cache/cache-arch.en.rst:66 +msgid "If the cache volumes for the example cache spans were defined as" +msgstr "" +"もし、例としてキャッシュスパンのキャッシュボリュームが以下のように定義されて" +"いたら" + +#: ../../arch/cache/cache-arch.en.rst:71 +msgid "then the actual layout would look like" +msgstr "実際のレイアウトはこのようになるでしょう。" + +#: ../../arch/cache/cache-arch.en.rst:83 +msgid "" +"The layout and structure of the cache spans, the cache volumes, and the " +"cache stripes that compose them are derived entirely from the :file:" +"`storage.config` and :file:`cache.config` and is recomputed from scratch " +"when the :process:`traffic_server` is started. Therefore any change to " +"those files can (and almost always will) invalidate the existing cache in " +"its entirety." +msgstr "" +"キャッシュスパン、キャッシュボリューム、そしてそれらを構成するキャッシュスト" +"ライプのレイアウトと構造は、全て :file:`storage.config` と:file:`cache." +"config` から取得され、 :process:`traffic_server` が開始された時にはじめから" +"再計算されます。従って、これらのファイルへの任意の変更は(ほとんど常に)それら" +"全ての既存のキャッシュを無効化します。" + +#: ../../arch/cache/cache-arch.en.rst:89 +msgid "Stripe Structure" +msgstr "ストライプ構造" + +#: ../../arch/cache/cache-arch.en.rst:91 +msgid "" +"|TS| treats the storage associated with a cache stripe as an " +"undifferentiated span of bytes. Internally each stripe is treated almost " +"entirely independently. The data structures described in this section are " +"duplicated for each stripe. Internally the term \"volume\" is used for " +"these stripes and implemented primarily in :cpp:class:`Vol`. What a user " +"thinks of as a volume (what this document calls a \"cache volume\") is " +"represented by :cpp:class:`CacheVol`." +msgstr "" +"|TS| は、キャッシュストライプと結び付けられたストレージを区別されないバイト" +"列のスパンとして扱います。内部的に各ストライプはほぼ完全に独立して扱われま" +"す。この節で記述されるデータ構造は、各ストライプに複製されます。内部的に " +"\"ボリューム\" という単語はこれらのストライプに使用され、主に:cpp:class:" +"`Vol` で実装されています。ユーザが思うボリューム(このドキュメントでは " +"\"キャッシュボリューム\")は、 :cpp:class:`CacheVol` で表現されます。" + +#: ../../arch/cache/cache-arch.en.rst:98 +msgid "" +"Stripe assignment must be done before working with an object because the " +"directory is local to the stripe. Any cached objects for which the stripe " +"assignment is changed are effectively lost as their directory data will not " +"be found in the new stripe." +msgstr "" +"ディレクトリはストライプに配置されるため、ストライプ割当はオブジェクトを扱う" +"ような動作をする前に行われなければなりません。ストライプ割当が変更された" +"キャッシュオブジェクトは、新しいストライプ上で発見されないであろうディレクト" +"リデータとして事実上消失します。" + +#: ../../arch/cache/cache-arch.en.rst:106 +msgid "Cache Directory" +msgstr "キャッシュディレクトリ" + +#: ../../arch/cache/cache-arch.en.rst:122 +msgid "" +"The directory is used as a memory resident structure which means a " +"directory entry is as small as possible (currently 10 bytes). This forces " +"some compromises on the data that can be stored there. On the other hand " +"this means that most cache misses do not require disk I/O which has a large " +"performance benefit." +msgstr "" +"ディレクトリはメモリに常住する構成で使用されるので、ディレクトリエントリは可" +"能な限り小さくなっています。（現在は 10 バイト）このことは、そこに保存できる" +"データに幾つかの制約を強要します。一方でほとんどのキャッシュミスはディスク " +"I/O を要求せず、大きな性能面の恩恵を得ることになります。" + +#: ../../arch/cache/cache-arch.en.rst:126 +msgid "" +"An additional point is the directory is always fully sized. Once a stripe " +"is initialized the directory size is fixed and never changed. This size is " +"related (roughly linearly) to the size of the stripe. It is for this reason " +"the memory footprint of |TS| depends strongly on the size of the disk " +"cache. Because the directory size does not change, neither does this memory " +"requirement so |TS| does not consume more memory as more content is stored " +"in the cache. If there is enough memory to run |TS| with an empty cache " +"there is enough to run it with a full cache." +msgstr "" +"加えて、ディレクトリは常に最大のサイズになります。ストライプが一旦初期化され" +"ると、ディレクトリサイズは固定されて二度と変更されません。このサイズは、スト" +"ライプのサイズに（大雑把に、線形に）関係します。この理由は |TS| のメモリ使用" +"量は、ディスクキャッシュのサイズに強く依存することにあります。ディレクトリサ" +"イズは変わらずメモリ要件もまた変わらないため、 |TS| がキャッシュに保存された" +"コンテンツより多いメモリを消費することはありません。キャッシュが空の状態で |" +"TS| を動作させるのに十分なメモリがあるなら、キャッシュが満ちた状態で動作する" +"のに十分です。" + +#: ../../arch/cache/cache-arch.en.rst:193 +msgid "Storage Layout" +msgstr "ストレージレイアウト" + +#: ../../arch/cache/cache-arch.en.rst:195 +msgid "" +"The storage layout is the stripe metadata followed by cached content. The " +"metadata consists of three parts - the stripe header, the directory, and " +"the stripe footer. The metadata is stored twice. The header and the footer " +"are instances of :cpp:class:`VolHeaderFooter`. This is a stub structure " +"which can have a trailing variable sized array. This array is used as the " +"segment free list roots in the directory. Each contains the segment index " +"of the first element of the free list for the segment. The footer is a copy " +"of the header without the segment free lists. This makes the size of the " +"header dependent on the directory but not that of the footer." +msgstr "" +"ストレージレイアウトは、ストライプメタデータの後ろにキャッシュされたコンテン" +"ツが続きます。メタデータは三つの要素、ストライプヘッダ、ディレクトリ、ストラ" +"イプフッタで構成されます。メタデータは二度保存されます。ヘッダとフッタは :" +"cpp:class:`VolHeaderFooter` のインスタンスです。これは可変長配列を末尾に持つ" +"ことができるスタブ構造体です。この配列はディレクトリのルートのセグメントフ" +"リーリストとして使用されます。各要素はセグメントのフリーリストの、最初の要素" +"のセグメントインデックスを持ちます。フッタは、セグメントフリーリストを伴わな" +"いヘッダのコピーです。ヘッダのサイズはディレクトリに依存しますが、フッタは依" +"存しません。" + +#: ../../arch/cache/cache-arch.en.rst:205 +msgid "Each stripe has several values that describe its basic layout." +msgstr "各ストライプは、基本的なレイアウトを表現する幾つかの値を持ちます。" + +#: ../../arch/cache/cache-arch.en.rst:209 +msgid "skip" +msgstr "skip" + +#: ../../arch/cache/cache-arch.en.rst:208 +msgid "" +"The start of stripe data. This represents either space reserved at the " +"start of a physical device to avoid problems with the host operating " +"system, or an offset representing use of space in the cache span by other " +"stripes." +msgstr "" +"ストライプデータの開始地点です。これはホストオペレーティングシステムによる問" +"題を回避するために物理デバイスの始点に予約されたスペース、もしくは他のストラ" +"イプにキャッシュスパンのスペースが使用されていることを表すオフセットのどちら" +"かを表します。" + +#: ../../arch/cache/cache-arch.en.rst:212 +msgid "start" +msgstr "start" + +#: ../../arch/cache/cache-arch.en.rst:212 +msgid "The offset for the start of the content, after the stripe metadata." +msgstr "ストライプメタデータの後からの、コンテンツの開始地点を示すオフセット" + +#: ../../arch/cache/cache-arch.en.rst:215 +msgid "length" +msgstr "length" + +#: ../../arch/cache/cache-arch.en.rst:215 +msgid "Total number of bytes in the stripe. :cpp:member:`Vol::len`." +msgstr "ストライプのバイトの合計値。 :cpp:member:`Vol::len` " + +#: ../../arch/cache/cache-arch.en.rst:218 +msgid "data length" +msgstr "data length" + +#: ../../arch/cache/cache-arch.en.rst:218 +msgid "" +"Total number of blocks in the stripe available for content storage. :cpp:" +"member:`Vol::data_blocks`." +msgstr "" +"コンテンツストレージとして使用可能なストライプのブロックの合計値。:cpp:" +"member:`Vol::data_blocks` " + +#: ../../arch/cache/cache-arch.en.rst:220 +msgid "" +"Great care must be taken with sizes and lengths in the cache code because " +"there are at least three different metrics (bytes, cache blocks, store " +"blocks) used in various places." +msgstr "" +"キャッシュコードの size や length を扱う場合、特に注意しなければなりません。" +"これらは様々な箇所で、少なくとも三つの違うメトリクス(バイト、キャッシュブ" +"ロック、ストアブロック)が使われているからです。" + +#: ../../arch/cache/cache-arch.en.rst:222 +msgid "" +"The total size of the directory (the number of entries) is computed by " +"taking the size of the stripe and dividing by the average object size. The " +"directory always consumes this amount of memory which has the effect that " +"if cache size is increased so is the memory requirement for |TS|. The " +"average object size defaults to 8000 bytes but can be configured using :ts:" +"cv:`proxy.config.cache.min_average_object_size`. Increasing the average " +"object size will reduce the memory footprint of the directory at the " +"expense of reducing the number of distinct objects that can be stored in " +"the cache [#]_." +msgstr "" +"ディレクトリの合計サイズ（エントリ数）は、ストライプのサイズを取得して平均オ" +"ブジェクトサイズで割ることで計算されます。もしキャッシュサイズが |TS| のメモ" +"リ要件により増加する場合、ディレクトリは常に効率的なメモリ量を消費します。平" +"均オブジェクトサイズはデフォルトでは 8000 バイトですが、 :ts:cv:`proxy." +"config.cache.min_average_object_size` で設定できます。平均オブジェクトサイズ" +"を増加させることにより、キャッシュに保存するオブジェクト数を減らすことと引き" +"換えに、ディレクトリのメモリ使用量を減らすことができます。 [#]_" + +#: ../../arch/cache/cache-arch.en.rst:232 +msgid "" +"The content area stores the actual objects and is used as a circular buffer " +"where new objects overwrite the least recently cached objects. The location " +"in a stripe where new cache data is written is called the *write cursor*. " +"This means that objects can be de facto evicted from cache even if they " +"have not expired if the data is overwritten by the write cursor. If an " +"object is overwritten this is not detected at that time and the directory " +"is not updated. Instead it will be noted if the object is accessed in the " +"future and the disk read of the fragment fails." +msgstr "" +"コンテンツエリアは実際のオブジェクトを保存し、最もキャッシュされてから時間が" +"経過したオブジェクトを新たなドキュメントで上書きする循環バッファとして使用さ" +"れます。ストライプの新たなキャッシュデータの位置は、 *書込みカーソル* と呼ば" +"れます。これはデータが書込みカーソルによって上書きされる場合、たとえ失効して" +"いなくても、オブジェクトは事実上キャッシュから立ち退かせられることを意味しま" +"す。もしオブジェクトが上書きされる場合、検出されずディレクトリは更新されませ" +"ん。代わりに、もしオブジェクトが将来アクセスされてフラグメントのディスク読込" +"みが失敗する場合、警告されます。" + +#: ../../arch/cache/cache-arch.en.rst:241 +msgid "The write cursor and documents in the cache." +msgstr "書込みカーソルとキャッシュ内のドキュメント" + +#: ../../arch/cache/cache-arch.en.rst:243 +msgid "Cache data on disk is never updated." +msgstr "ディスク上のキャッシュデータは永遠に更新されません。" + +#: ../../arch/cache/cache-arch.en.rst:245 +msgid "" +"This is a key thing to keep in mind. What appear to be updates (such as " +"doing a refresh on stale content and getting back a 304) are actually new " +"copies of data being written at the write cursor. The originals are left as " +"\"dead\" space which will be consumed when the write cursor arrives at that " +"disk location. Once the stripe directory is updated (in memory!) the " +"original fragment in the cache is effectively destroyed. This is the " +"general space management techinque used in other cases as well. If an " +"object needs to removed from cache, only the directory needs to be changed. " +"No other work (and *particularly* no disk I/O) needs to be done." +msgstr "" +"これは、心に留めておくべき重要な事です。更新されるように見えるもの（新鮮では" +"なくなったコンテンツをリフレッシュし、 304 を返すような）は、実際には書込み" +"カーソルで書き込まれているデータの新しいコピーです。オリジナルは書込みカーソ" +"ルがディスクのその位置に到着する時に消去される、\"死んだ\" スペースとして残" +"されます。一旦ストライプディレクトリが（メモリ内で！）更新されると、キャッ" +"シュ上のオリジナルのフラグメントは事実上破棄されます。これは他のケースでも同" +"様に用いられる、一般的なスペース管理技術です。もしオブジェクトをキャッシュか" +"ら削除する必要がある場合、ディレクトリの変更のみ必要があります。他の動作（ *" +"特に* ディスク I/O も）を行う必要はありません。" + +#: ../../arch/cache/cache-arch.en.rst:253 +msgid "Object Structure" +msgstr "オブジェクトの構造" + +#: ../../arch/cache/cache-arch.en.rst:255 +msgid "" +"Objects are stored as two types of data, metadata and content data. " +"Metadata is all the data about the object and the content and includes the " +"HTTP headers. The content data is the content of the object, the octet " +"stream delivered to the client as the object." +msgstr "" +"オブジェクトは二つのデータのタイプ、メタデータとコンテンツデータとして保存" +"されます。メタデータは、 HTTP ヘッダを含むオブジェクトとコンテンツに関する" +"全てのデータです。コンテンツデータはオブジェクトのコンテンツで、オブジェクトと" +"してクライアントに配信されるオクテットストリームです。" + +#: ../../arch/cache/cache-arch.en.rst:259 +msgid "" +"Objects are rooted in a :cpp:class:`Doc` structure stored in the cache. :" +"cpp:class:`Doc` serves as the header data for a fragment and is contained " +"at the start of every fragment. The first fragment for an object is termed " +"the \"first ``Doc``\" and always contains the object metadata. Any " +"operation on the object will read this fragment first. The fragment is " +"located by converting the cache key for the object to a cache ID and then " +"doing a lookup for a directory entry with that key. The directory entry has " +"the offset and approximate size of the first fragment which is then read " +"from the disk. This fragment will contain the request header and response " +"along with overall object properties (such as content length)." +msgstr "" +"オブジェクトは、キャッシュに格納される :cpp:class:`Doc` 構造体をルートと" +"します。:cpp:class:`Doc` はフラグメントのヘッダデータとして提供し、各フラグ" +"メントの先頭に置かれます。これは \" first ``Doc``\" と呼ばれ、常にオブジェクト" +"メタデータに含まれます。オブジェクトの任意の操作は、最初にこのフラグメントを" +"読み込みます。そのフラグメントはオブジェクトのキャッシュキーをキャッシュ ID に" +"変換することにより発見され、その後そのキーを使ってディレクトリエントリが検索" +"されます。ディレクトリエントリは、その時ディスクから読み込まれる先頭の" +"フラグメントのオフセットとおおよそのサイズを持ちます。このフラグメントは、全て" +"のオブジェクトのプロパティ（コンテンツ長のような）に加えて、リクエストヘッダ" +"とレスポンスを持ちます。" + +#: ../../arch/cache/cache-arch.en.rst:269 +msgid "" +"|TS| supports `varying content `_ for objects. These are called *alternates*. All " +"metadata for all alternates is stored in the first fragment including the " +"set of alternates and the HTTP headers for them. This enables `alternate " +"selection `_ to be done after the first " +"``Doc`` is read from disk. An object that has more than one alternate will " +"have the alternate content stored separately from the first fragment. For " +"objects with only one alternate the content may or may not be in the same " +"(first) fragment as the metadata. Each separate alternate content is " +"allocated a directory entry and the key for that entry is stored in the " +"first fragment metadata." +msgstr "" +"|TS| はオブジェクト用に `コンテンツ変換 `_ をサポートします。これらを *代替* と呼びます。" +"全ての代替の全メタデータは、代替のセットとそれらの HTTP ヘッダを含む先頭の" +"フラグメントに格納されます。これは、 first ``Doc``がディスクから読込まれた" +"後に、`代替セクション `_ が実行されて有効に" +"なります。複数の代替を持つオブジェクトは、先頭のフラグメントとは別に" +"保存された代替コンテンツを持ちます。一つの代替のみ持つオブジェクトは、" +"コンテンツはメタデータと同じ（先頭の）フラグメントに置かれるかもしれないし、" +"そうでもないかもしれません。個々の分離された代替コンテンツはディレクトリ" +"エントリを割り当てられ、エントリのキーは先頭のフラグメントのメタデータに" +"保存されます。" + +#: ../../arch/cache/cache-arch.en.rst:278 +msgid "" +"Prior to version 4.0.1 the header data was stored in the :cpp:class:" +"`CacheHTTPInfoVector` class which was marshaled to a variable length area " +"of the on disk image, followed by information about additional fragments if " +"needed to store the object." +msgstr "" +"バージョン 4.0.1 以前は、ヘッダデータはディスクイメージの可変長領域をまとめる " +":cpp:class:`CacheHTTPInfoVector` クラス内に保存され、オブジェクトを保存する" +"必要がある場合、追加フラグメント情報がその後ろに続きます。" + +#: ../../arch/cache/cache-arch.en.rst:285 +msgid "``Doc`` layout 3.2.0" +msgstr "3.2.0 の ``Doc`` レイアウト" + +#: ../../arch/cache/cache-arch.en.rst:287 +msgid "" +"This had the problem that with only one fragment table it could not be " +"reliable for objects with more than one alternate [#]_. Therefore the " +"fragment data was moved from being a separate variable length section of " +"the metadata to being directly incorporated in to the :cpp:class:" +"`CacheHTTPInfoVector`, yielding a layout of the following form." +msgstr "" +"この方法では、一つのフラグメントテーブルのみでは複数の代替を持つオブジェクトに" +"対しては信頼性を確保できない問題がありました。 [#]_ 従って、フラグメントデータ" +"はメタデータ用に分離された可変長領域から :cpp:class:`CacheHTTPInfoVector` へ" +"直接統合されるよう移動し、以下の形式のレイアウトに生まれ変わりました。" + +#: ../../arch/cache/cache-arch.en.rst:294 +msgid "``Doc`` layout 4.0.1" +msgstr "4.0.1 の ``Doc`` レイアウト" + +#: ../../arch/cache/cache-arch.en.rst:296 +msgid "" +"Each element in the vector contains for each alternate, in addition to the " +"HTTP headers and the fragment table (if any), a cache key. This cache key " +"identifies a directory entry that is referred to as the \"earliest ``Doc``" +"\". This is the location where the content for the alternate begins." +msgstr "" +"ベクターの各要素は、各代替に加えて（もしあれば） HTTP ヘッダとフラグメント" +"テーブル、キャッシュキーを含みます。このキャッシュキーは \"earliest " +"``Doc`` \" として参照されるディレクトリエントリを特定します。これは代替の" +"コンテンツの開始位置です。" + +#: ../../arch/cache/cache-arch.en.rst:300 +msgid "" +"When the object is first cached, it will have a single alternate and that " +"will be stored (if not too large) in first ``Doc``. This is termed a " +"*resident alternate* in the code. This can only happen on the initial store " +"of the object. If the metadata is updated (such as a ``304`` response to an " +"``If-Modified-Since`` request) then unless the object is small, the object " +"data will be left in the original fragment and a new fragment written as " +"the first fragment, making the alternate non-resident. \"Small\" is defined " +"as a length smaller than :ts:cv:`proxy.config.cache.alt_rewrite_max_size`." +msgstr "" +"オブジェクトが最初にキャッシュされる際、それは単一の代替を持ち、（大き" +"すぎない場合は） first ``Doc`` に格納されます。これはコード中で *常駐代替* と" +"呼ばれます。この処理はオブジェクトの最初の保存時にのみ発生できます。メタ" +"データが更新される場合（``If-Modified-Since`` リクエストに対し、 ``304`` を" +"返すなど)、オブジェクトが小さくなければ、オブジェクトデータはオリジナルの" +"フラグメントに取り残され、新しいフラグメントが先頭のフラグメントとして書き" +"込まれ、非常駐の代替を作成します。 :ts:cv:`proxy.config.cache." +"alt_rewrite_max_size` より小さい長さを、 \"小さい\" と定義します。" + +#: ../../arch/cache/cache-arch.en.rst:308 +msgid "" +"The :cpp:class:`CacheHTTPInfoVector` is stored only in the first ``Doc``. " +"Subsequent ``Doc`` instances for the object, including the earliest " +"``Doc``, should have an ``hlen`` of zero and if not, it is ignored." +msgstr "" +":cpp:class:`CacheHTTPInfoVector` は first ``Doc`` にのみ保存されます。" +"earliest ``Doc`` を含む、 first ``Doc`` に続くオブジェクトの ``Doc`` インス" +"タンスはゼロの ``hlen`` を持つはずであり、もしそうでないものは無視されます。" + +#: ../../arch/cache/cache-arch.en.rst:311 +msgid "" +"Large objects are split in to multiple fragments when written to the cache. " +"This is indicated by a total document length that is longer than the " +"content in first ``Doc`` or an earliest ``Doc``. In such a case a fragment " +"offset table is stored. This contains the byte offset in the object content " +"of the first byte of content data for each fragment past the first (as the " +"offset for the first is always zero). This allows range requests to be " +"serviced much more efficiently for large objects, as intermediate fragments " +"that do not contain data in the range can be skipped. The last fragment in " +"the sequence is detected by the fragment size and offset reaching the end " +"of the total size of the object, there is no explicit end mark. Each " +"fragment is computationally chained from the previous in that the cache key " +"for fragment N is computed by::" +msgstr "" +"巨大なオブジェクトは、キャッシュに書き込まれる時に複数のフラグメントに分割され" +"ます。これは、ドキュメント長の合計が first ``Doc`` もしくは earliest ``Doc`` " +"のコンテンツより長いことを示します。このような場合には、フラグメントオフセット" +"テーブルが保存されます。このテーブルは（オフセットが常にゼロであるような）" +"先頭のフラグメントの次以降の各フラグメントのコンテンツデータの先頭バイト" +"を指し示す、オブジェクトコンテンツ全体の中でのバイトオフセットを含みます。" +"これは範囲内のデータを含まない、中間にあるフラグメントをスキップ可能にする" +"ことで、巨大なオブジェクトを非常に効率的に提供するためのレンジリクエストを" +"可能にします。シーケンスの最後のフラグメントは、明示的なエンドマーク無しに" +"フラグメントサイズとオフセットがオブジェクトの合計サイズの最後に到達することに" +"より検出されます。各フラグメントは、計算的に前のものと繋がっています。" +"フラグメント N のキャッシュキーは、以下により計算されます::" + +#: ../../arch/cache/cache-arch.en.rst:322 +msgid "" +"where ``next_key`` is a global function that deterministically computes a " +"new cache key from an existing cache key." +msgstr "" +"``next_key`` は既存のキャッシュキーから新しいキャッシュキーを決定論的に計算" +"するグローバル関数です。" + +#: ../../arch/cache/cache-arch.en.rst:324 +msgid "" +"Objects with multiple fragments are laid out such that the data fragments " +"(including the earliest ``Doc``) are written first and the first ``Doc`` is " +"written last. When read from disk, both the first and earliest ``Doc`` are " +"validated (tested to ensure that they haven't been overwritten by the write " +"cursor) to verify that the entire document is present on disk (as they " +"bookend the other fragments - the write cursor cannot overwrite them " +"without overwriting at leastone of the verified ``Doc`` instances). Note " +"that while the fragments of a single object are ordered they are not " +"necessarily contiguous as data from different objects are interleaved as " +"the data arrives in |TS|." +msgstr "" +"複数のフラグメントを伴うオブジェクトは、（earliest ``Doc`` を含む）データ" +"フラグメントが先頭に書き込まれ、 first ``Doc`` が末尾に書き込まれる形で" +"レイアウトされます。ディスクから読み込まれる時、先頭と earliest ``Doc`` の" +"両方は、ドキュメント全部がディスクに存在することを確認するため検証されます。" +"（それらが書込みカーソルにより上書きされていないことを確認することで試験" +"されます） （これらの ``Doc`` は他のフラグメントのブックエンドとなります。" +"書込みカーソルは、検証された ``Doc`` インスタンスの少なくとも一つの上書き" +"無しに、ドキュメントを上書き出来ません）単一のオブジェクトのフラグメントは、 " +"|TS| に届いたデータとして異なるオブジェクトのデータが挟み込められてしまう" +"ため、必然的に隣接しないように並べられていることに注意してください。" + +#: ../../arch/cache/cache-arch.en.rst:334 +msgid "Multi-alternate and multi-fragment object storage" +msgstr "オブジェクトストレージの、複数の代替と複数のフラグメント" + +#: ../../arch/cache/cache-arch.en.rst:338 +msgid "" +"Documents which are \"pinned\" into the cache must not be overwritten so " +"they are \"evacuated\" from in front of the write cursor. Each fragment is " +"read and rewritten. There is a special lookup mechanism for objects that " +"are being evacuated so that they can be found in memory rather than the " +"potentially unreliable disk regions. The cache scans ahead of the write " +"cursor to discover pinned objects as there is a dead zone immediately " +"before the write cursor from which data cannot be evacuated. Evacuated data " +"is read from disk and placed in the write queue and written as its turn " +"comes up." +msgstr "" +"キャッシュへ \"ピン留め\" されたドキュメントは上書きされてはならず、そのため" +"それらは書込みカーソルの前に \"退避\" させられます。各フラグメントは読み込ま" +"れ、再書込みされます。潜在的に信頼性の低いディスク領域ではなくメモリ上で検出" +"できるよう、退避されるオブジェクトの特殊な検出メカニズムが存在します。データを" +"退避させることができない書込みカーソル直前のデットゾーンがあるため、ピン留め" +"されたオブジェクトを発見するためにキャッシュは書込みカーソルより先にスキャン" +"します。退避されたデータはディスクから読み込まれて書込みキューに置かれ、出番が" +"来ると書き込まれます。" + +#: ../../arch/cache/cache-arch.en.rst:344 +msgid "" +"It appears that objects can only be pinned via the :file:`cache.config` " +"file and if the :ts:cv:`proxy.config.cache.permit.pinning` is set to non-" +"zero (it is zero by default). Objects which are in use when the write " +"cursor is near use the same underlying evacuation mechanism but are handled " +"automatically and not via the explicit ``pinned`` bit in :cpp:class:`Dir`." +msgstr "" +"オブジェクトは :file:`cache.config` ファイルと、 :ts:cv:`proxy.config.cache." +"permit.pinning` にゼロでない値（デフォルトではゼロ）を設定した場合のみピン留め" +"できます。書込みカーソルが接近している際に使用中のオブジェクトは、基本的な退避" +"メカニズムを同様に使用しますが、 :cpp:class:`Dir` の明示的な ``ピン留め`` " +"無しに自動的に扱われます。" + +#: ../../arch/cache/cache-arch.en.rst:349 +msgid "" +"It could, under certain circumstances, be accurate for none of the " +"alternates." +msgstr "それは、ある状況下では代替が正確になりません。" + +#: ../../arch/cache/cache-arch.en.rst:352 +msgid "Additional Notes" +msgstr "追加情報" + +#: ../../arch/cache/cache-arch.en.rst:354 +msgid "Some general observations on the data structures." +msgstr "データ構造のいくつかの概説。" + +#: ../../arch/cache/cache-arch.en.rst:357 +msgid "Cyclone buffer" +msgstr "循環バッファ" + +#: ../../arch/cache/cache-arch.en.rst:359 +msgid "" +"Because the cache is a cyclone cache objects are not preserved for an " +"indefinite time. Even if the object is not stale it can be overwritten as " +"the cache cycles through its volume. Marking an object as ``pinned`` " +"preserves the object through the passage of the write cursor but this is " +"done by copying the object across the gap, in effect re-storing it in the " +"cache. Pinning large objects or a large number objects can lead to a " +"excessive disk activity. The original purpose of pinning seems to have been " +"for small, frequently used objects explicitly marked by the administrator." +msgstr "" +"キャッシュは循環するため、キャッシュオブジェクトは無期限の保存はされません。" +"たとえオブジェクトが新鮮であっても、ボリュームのキャッシュサイクルとして上書き" +"する可能性があります。 ``ピン留め`` してオブジェクトをマーキングすることにより" +"書込みカーソルの通過をやり過ごしてオブジェクトを保護することができますが、これ" +"は書込みカーソルを跨いでオブジェクトをコピーすること、実際にはキャッシュ内に" +"再保存を行うことによって処理されます。巨大なオブジェクトや大量のオブジェクトの" +"ピン留めは、過度のディスク動作を引き起こす場合があります。ピン留めの本来の" +"目的は、管理者によって明示的にマークされた小さく頻繁に使用されるオブジェクトの" +"ためのものであったようです。" + +#: ../../arch/cache/cache-arch.en.rst:365 +msgid "" +"This means the purpose of expiration data on objects is simply to prevent " +"them from being served to clients. They are not in the standard sense " +"deleted or cleaned up. The space can't be immediately reclaimed in any " +"event because writing only happens at the write cursor. Deleting an object " +"consists only of removing the directory entries in the volume directory " +"which suffices to (eventually) free the space and render the document " +"inaccessible." +msgstr "" +"循環バッファの目的は、単純にオブジェクトの失効データがクライアントに提供される" +"のを防ぐことです。失効データは一般的な意味での削除やクリーンアップはされま" +"せん。書込み処理は書込みカーソルでのみ発生するので、どんなイベントにおいても" +"スペースは直ちには取り戻せません。オブジェクトの削除は（最終的には）スペースを" +"解放してかつドキュメントをアクセス不可能にするのに十分な処理である、ボリューム" +"ディレクトリのディレクトリエントリの削除のみで成り立ちます。" + +#: ../../arch/cache/cache-arch.en.rst:370 +msgid "" +"Historically the cache is designed this way because web content was " +"relatively small and not particularly consistent. The design also provides " +"high performance and low consistency requirements. There are no " +"fragmentation issues for the storage, and both cache misses and object " +"deletions require no disk I/O. It does not deal particularly well with long " +"term storage of large objects. See the :ref:`volume tagging` appendix for " +"details on some work in this area." +msgstr "" +"ウェブコンテンツは比較的小さく特に一貫もしていなかったので、歴史的に" +"キャッシュはこの方法の通りに設計されています。この設計は高性能でかつ低い" +"一貫性の要件となります。ストレージのフラグメンテーション問題は発生せず、また" +"キャッシュミスやオブジェクトの削除がディスク I/O を要求することもありません。" +"巨大なオブジェクトの長期間保存はうまく扱いません。この部分の動作の詳細について" +"は :ref:`volume tagging` の付録を見てください。" + +#: ../../arch/cache/cache-arch.en.rst:376 +msgid "Disk Failure" +msgstr "ディスク障害" + +#: ../../arch/cache/cache-arch.en.rst:378 +msgid "" +"The cache is designed to be relatively resistant to disk failures. Because " +"each storage unit in each volume is mostly independent the loss of a disk " +"simply means that the corresponding :cpp:class:`Vol` instances (one per " +"cache volume that uses the storage unit) becomes unusable. The primary " +"issue is updating the volume assignment table to both preserve assignments " +"for objects on still operational volumes while distributing the assignments " +"from the failed disk to those operational volumes. This mostly done in::" +msgstr "" +"キャッシュはディスク障害に比較的強いように設計されます。各ボリュームの" +"各ストレージユニットはほぼ独立しているので、ディスクの損失は対応する " +":cpp:class:`Vol` インスタンス（ストレージユニットを使うキャッシュボリューム" +"毎のもの）が使えなくなることを単純に意味します。主な課題は故障したディスクから" +"運用中のボリュームへの割当の配布中に、まだ運用中のボリューム上のオブジェクトの" +"割当を両方保存するためのボリューム割当テーブルの更新処理です。これはほとんどが" +"以下の中で処理されます::" + +#: ../../arch/cache/cache-arch.en.rst:382 +msgid "" +"Restoring a disk to active duty is quite a bit more difficult task. " +"Changing the volume assignment of a cache key renders any currently cached " +"data inaccessible. This is obviouly not a problem when a disk has failed, " +"but is a bit trickier to decide which cached objects are to be de facto " +"evicted if a new storage unit is added to a running system. The mechanism " +"for this, if any, is still under investigation." +msgstr "" +"ディスクを稼働状態に戻すのは非常に困難な作業です。キャッシュキーの" +"ボリューム割当の変更は、全ての現在キャッシュされているデータへのアクセスを" +"不可能にします。ディスクが故障した際にこれは当然ながら問題にはなりませんが、" +"新しいストレージユニットが動作中のシステムに追加された場合、どのキャッシュ" +"されたオブジェクトが事実上追い出されるか決定するのが少々扱いにくい処理です。" +"このためのメカニズムは何かないか、まだ調査です。" + +#: ../../arch/cache/cache-arch.en.rst:385 +msgid "Implementation Details" +msgstr "実装の詳細" + +#: ../../arch/cache/cache-arch.en.rst:388 +msgid "Stripe Directory" +msgstr "ストライプディレクトリ" + +#: ../../arch/cache/cache-arch.en.rst:392 +msgid "The in memory volume directory entries are defined as described below." +msgstr "メモリ上のボリュームディレクトリエントリは、以下の通りに定義されます。" + +#: ../../arch/cache/cache-arch.en.rst:396 +msgid "Defined in |P-CacheDir.h|_." +msgstr "|P-CacheDir.h|_ で定義される。" + +#: ../../arch/cache/cache-arch.en.rst:399 +msgid "Name" +msgstr "名前" + +#: ../../arch/cache/cache-arch.en.rst:399 +msgid "Type" +msgstr "型" + +#: ../../arch/cache/cache-arch.en.rst:399 +msgid "Use" +msgstr "用途" + +#: ../../arch/cache/cache-arch.en.rst:401 +msgid "offset" +msgstr "offset" + +#: ../../arch/cache/cache-arch.en.rst:401 +msgid "unsigned int:24" +msgstr "unsigned int:24" + +#: ../../arch/cache/cache-arch.en.rst:401 +msgid "Offset of first byte of metadata (volume relative)" +msgstr "（ボリュームに関連した）メタデータの先頭バイトのオフセット" + +#: ../../arch/cache/cache-arch.en.rst:402 +msgid "big" +msgstr "big" + +#: ../../arch/cache/cache-arch.en.rst:402 +msgid "unsigned in:2" +msgstr "unsigned in:2" + +#: ../../arch/cache/cache-arch.en.rst:402 +msgid "Size multiplier" +msgstr "サイズの乗数" + +#: ../../arch/cache/cache-arch.en.rst:403 +msgid "size" +msgstr "size" + +#: ../../arch/cache/cache-arch.en.rst:403 +msgid "unsigned int:6" +msgstr "unsigned int:6" + +#: ../../arch/cache/cache-arch.en.rst:403 +msgid "Size" +msgstr "サイズ" + +#: ../../arch/cache/cache-arch.en.rst:404 +msgid "tag" +msgstr "tag" + +#: ../../arch/cache/cache-arch.en.rst:404 +msgid "unsigned int:12" +msgstr "unsigned int:12" + +#: ../../arch/cache/cache-arch.en.rst:404 +msgid "Partial key (fast collision check)" +msgstr "（高速な衝突チェックの為の）キーの一部" + +#: ../../arch/cache/cache-arch.en.rst:405 +msgid "phase" +msgstr "phase" + +#: ../../arch/cache/cache-arch.en.rst:405 +#: ../../arch/cache/cache-arch.en.rst:406 +#: ../../arch/cache/cache-arch.en.rst:407 +#: ../../arch/cache/cache-arch.en.rst:408 +msgid "unsigned int:1" +msgstr "unsigned int:1" + +#: ../../arch/cache/cache-arch.en.rst:405 +msgid "Unknown" +msgstr "不明" + +#: ../../arch/cache/cache-arch.en.rst:406 +msgid "head" +msgstr "head" + +#: ../../arch/cache/cache-arch.en.rst:406 +msgid "Flag: first fragment in an object" +msgstr "オブジェクトの先頭のフラグメントを示すフラグ" + +#: ../../arch/cache/cache-arch.en.rst:407 +#: ../../arch/cache/cache-arch.en.rst:336 +msgid "pinned" +msgstr "pinned" + +#: ../../arch/cache/cache-arch.en.rst:407 +msgid "Flag: document is pinned" +msgstr "ドキュメントがピン留めされていることを示すフラグ" + +#: ../../arch/cache/cache-arch.en.rst:408 +msgid "token" +msgstr "token" + +#: ../../arch/cache/cache-arch.en.rst:408 +msgid "Flag: Unknown" +msgstr "不明なフラグ" + +#: ../../arch/cache/cache-arch.en.rst:409 +msgid "next" +msgstr "next" + +#: ../../arch/cache/cache-arch.en.rst:409 +msgid "unsigned int:16" +msgstr "unsigned int:16" + +#: ../../arch/cache/cache-arch.en.rst:409 +msgid "Segment local index of next entry." +msgstr "次エントリへのセグメントローカルインデックス" + +#: ../../arch/cache/cache-arch.en.rst:410 +msgid "offset_high" +msgstr "offset_high" + +#: ../../arch/cache/cache-arch.en.rst:410 +msgid "inku16" +msgstr "inku16" + +#: ../../arch/cache/cache-arch.en.rst:410 +msgid "High order offset bits" +msgstr "上位オフセットビット" + +#: ../../arch/cache/cache-arch.en.rst:413 +msgid "" +"The stripe directory is an array of ``Dir`` instances. Each entry refers to " +"a span in the volume which contains a cached object. Because every object " +"in the cache has at least one directory entry this data has been made as " +"small as possible." +msgstr "" +"ストライプディレクトリは ``Dir`` インスタンスの配列です。各エントリは" +"キャッシュされたオブジェクトを持つボリュームのスパンを参照します。キャッシュ内" +"の各オブジェクトは少なくとも一つのディレクトリエントリを持つため、このデータは" +"可能な限り小さくなるよう設計されました。" + +#: ../../arch/cache/cache-arch.en.rst:415 +msgid "" +"The offset value is the starting byte of the object in the volume. It is 40 " +"bits long split between the *offset* (lower 24 bits) and *offset_high* " +"(upper 16 bits) members. Note that since there is a directory for every " +"storage unit in a cache volume, this is the offset in to the slice of a " +"storage unit attached to that volume." +msgstr "" +"オフセット値はボリューム内におけるオブジェクトの開始バイトです。それは " +"*offset* （下位 24 ビット） と *offset_high* （上位 16 ビット） メンバに渡って" +"分割された 40 ビット長です。キャッシュボリュームの各ストレージユニット毎に" +"ディレクトリは存在するため、この値はボリュームに接続されたストレージユニットの" +"一部分へのオフセットであることに注意してください。" + +#: ../../arch/cache/cache-arch.en.rst:419 +msgid "" +"The *size* and *big* values are used to calculate the approximate size of " +"the span which contains the object. This value is used as the number of " +"bytes to read from storage at the offset value. The exact size is contained " +"in the object metadata in :cpp:class:`Doc` which is consulted once the read " +"has completed. For this reason the approximate size needs to be at least as " +"large as the actual size but can be larger, at the cost of reading the " +"extraneous bytes." +msgstr "" +"*size* と *big* 値はオブジェクトを持つスパンの大まかなサイズを計算する為に" +"使用されます。この値はストレージのオフセット値から読込み処理を行うための" +"バイト数として使用されます。正確なサイズは一旦読込みが完了した後に、参照される" +" :cpp:class:`Doc` のオブジェクトメタデータに含まれます。この理由は、大まかな" +"サイズは少なくとも実サイズと同じかそれより大きくする必要があるものの、" +"無関係なバイト列の読込みをするためコストが大きくなることにあります。" + +#: ../../arch/cache/cache-arch.en.rst:421 +msgid "" +"The computation of the approximate size of the fragment is defined as::" +msgstr "" +"フラグメントの大まかなサイズの計算は以下のように定義されます。::" + +#: ../../arch/cache/cache-arch.en.rst:425 +msgid "" +"where ``CACHE_BLOCK_SHIFT`` is the bit width of the size of a basic cache " +"block (9, corresponding to a sector size of 512). Therefore the value with " +"current defines is::" +msgstr "" +"``CACHE_BLOCK_SHIFT`` は基本的なキャッシュブロックのサイズのビット幅（9 で" +"あり、 512 のセクタサイズに対応している） です。従ってその値は現在は以下の" +"ように定義されます。::" + +#: ../../arch/cache/cache-arch.en.rst:429 +msgid "Because *big* is 2 bits the values for the multiplier of *size* are" +msgstr "*big* は 2 ビットであるため、*size* の乗数の値は、" + +#: ../../arch/cache/cache-arch.en.rst:434 +msgid "*big*" +msgstr "*big*" + +#: ../../arch/cache/cache-arch.en.rst:434 +msgid "Multiplier" +msgstr "乗数" + +#: ../../arch/cache/cache-arch.en.rst:434 +msgid "Maximum Size" +msgstr "最大サイズ" + +#: ../../arch/cache/cache-arch.en.rst:436 +msgid "0" +msgstr "0" + +#: ../../arch/cache/cache-arch.en.rst:436 +msgid "512 (2^9)" +msgstr "512 (2^9)" + +#: ../../arch/cache/cache-arch.en.rst:436 +#: ../../arch/cache/cache-arch.en.rst:438 +msgid "32768 (2^15)" +msgstr "32768 (2^15)" + +#: ../../arch/cache/cache-arch.en.rst:437 +msgid "1" +msgstr "1" + +#: ../../arch/cache/cache-arch.en.rst:437 +msgid "4096 (2^12)" +msgstr "4096 (2^12)" + +#: ../../arch/cache/cache-arch.en.rst:437 +#: ../../arch/cache/cache-arch.en.rst:439 +msgid "262144 (2^18)" +msgstr "262144 (2^18)" + +#: ../../arch/cache/cache-arch.en.rst:438 +msgid "2" +msgstr "2" + +#: ../../arch/cache/cache-arch.en.rst:438 +msgid "2097152 (2^21)" +msgstr "2097152 (2^21)" + +#: ../../arch/cache/cache-arch.en.rst:439 +msgid "3" +msgstr "3" + +#: ../../arch/cache/cache-arch.en.rst:439 +msgid "16777216 (2^24)" +msgstr "16777216 (2^24)" + +#: ../../arch/cache/cache-arch.en.rst:442 +msgid "" +"Note also that *size* is effectively offset by one, so a value of 0 " +"indicates a single unit of the multiplier." +msgstr "" +"*size* も 1 が効率的なオフセットであり、そのため 0 は乗数の単一のユニットを" +"示すことに注意してください。" + +#: ../../arch/cache/cache-arch.en.rst:446 +msgid "The target fragment size can set with the :file:`records.config` value" +msgstr "" +"ターゲットフラグメントサイズは :file:`records.config` の値で設定できます。" + +#: ../../arch/cache/cache-arch.en.rst:448 +msgid "``proxy.config.cache.target_fragment_size``" +msgstr "``proxy.config.cache.target_fragment_size``" + +#: ../../arch/cache/cache-arch.en.rst:450 +msgid "" +"This value should be chosen so that it is a multiple of a :ref:`cache entry " +"multiplier `. It is not necessary to make it a power of 2 [#]_. " +"Larger fragments increase I/O efficiency but lead to more wasted space. The " +"default size (1M, 2^20) is a reasonable choice in most circumstances " +"altough in very specific cases there can be benefit from tuning this " +"parameter. |TS| imposes an internal maximum of a 4194232 bytes which is 4M " +"(2^22) less the size of a struct :cpp:class:`Doc`. In practice then the " +"largest reasonable target fragment size is 4M - 262144 = 3932160." +msgstr "" +":ref:`キャッシュエントリ乗数 ` の倍数になるようにこの値を選択する" +"べきです。 2 の冪乗にする必要はありません。 [#]_ 巨大なフラグメントは I/O の" +"効率を向上しますが、無駄なスペースが増加します。デフォルトサイズ（1M, " +"2^20）はこのパラメータを合わせることにより恩恵が得られる、非常に特殊なケースを" +"除いてほとんどの環境において合理的な選択です。 |TS| は :cpp:class:`Doc` " +"構造のサイズより少ない 4M（2^22） である 4194232 バイトの内部的な最大値を" +"強制します。事実上、最大の合理的なターゲットフラグメントサイズは 4M - 262144 " +"= 3932160 です。" + +#: ../../arch/cache/cache-arch.en.rst:456 +msgid "" +"When a fragment is stored to disk the size data in the cache index entry is " +"set to the finest granularity permitted by the size of the fragment. To " +"determine this consult the :ref:`cache entry multipler ` table, " +"find the smallest maximum size that is at least as large as the fragment. " +"That will indicate the value of *big* selected and therefore the " +"granularity of the approximate size. That represents the largest possible " +"amount of wasted disk I/O when the fragment is read from disk." +msgstr "" +"フラグメントがディスクへ保存される際、キャッシュインデックスエントリのサイズ" +"データはフラグメントのサイズにより許容される最小粒度で設定されます。これが " +":ref:`キャッシュエントリ乗数 ` テーブルを参照するかを決定する" +"ため、少なくともフラグメントと同じくらい大きな、最も小さな最大サイズを検索" +"します。それは選択された *big* の値であり、従って大まかなサイズの粒度を示すで" +"しょう。それはフラグメントがディスクから読み込まれる際に発生しうる最大の余分な" +"ディスク I/O の量を表します。" + +#: ../../arch/cache/cache-arch.en.rst:464 +msgid "" +"The set of index entries for a volume are grouped in to *segments*. The " +"number of segments for an index is selected so that there are as few " +"segments as possible such that no segment has more than 2^16 entries. Intra-" +"segment references can therefore use a 16 bit value to refer to any other " +"entry in the segment." +msgstr "" +"ボリュームのインデックスエントリのセットは *セグメント* へグループ化されます。" +"インデックスのセグメントの数は、 2^16 エントリを超えるセグメント数にならない" +"ように可能な限り少ないセグメントになるよう選択されます。内部セグメントの参照は" +"そのため、セグメントの任意の他のエントリを参照する為に 16 ビット値を使用" +"します。" + +#: ../../arch/cache/cache-arch.en.rst:468 +msgid "" +"Index entries in a segment are grouped *buckets* each of ``DIR_DEPTH`` " +"(currently 4) entries. These are handled in the standard hash table way, " +"giving somewhat less than 2^14 buckets per segment." +msgstr "" +"セグメントのインデックスエントリは ``DIR_DEPTH`` （現在は 4）エントリ毎に " +"*バケット* へグループ化されます。これらはセグメント毎に 2^14 未満のバケットを" +"割り当てる標準的なハッシュテーブルの手法で処理されます。" + +#: ../../arch/cache/cache-arch.en.rst:471 +msgid "The comment in :file:`records.config` is simply wrong." +msgstr ":file:`records.config` のコメントは単純に間違っています。" + +#: ../../arch/cache/cache-arch.en.rst:476 +msgid "Directory Probing" +msgstr "ディレクトリ検索" + +#: ../../arch/cache/cache-arch.en.rst:478 +msgid "" +"Directory probing is locating a specific directory entry in the stripe " +"directory based on a cache ID. This is handled primarily by the function :" +"cpp:func:`dir_probe()`. This is passed the cache ID (:arg:`key`), a stripe " +"(:arg:`d`), and a last collision (:arg:`last_collision`). The last of these " +"is an in and out parameter, updated as useful during the probe." +msgstr "" +"ディレクトリ検索はキャッシュ ID に基づくストライプディレクトリの特定の" +"ディレクトリエントリを検索します。これは主に :cpp:func:`dir_probe()` 関数に" +"よって処理されます。この関数はキャッシュ ID（:arg:`key`） 、ストライプ（" +":arg:`d`）、そして最後の衝突（:arg:`last_collision`）が渡されます。最後の衝突" +"はパラメータを読み書きして検索に役立つよう更新されます。" + +#: ../../arch/cache/cache-arch.en.rst:483 +msgid "" +"Given an ID, the top half (64 bits) is used as a :ref:`segment ` index, taken modulo the number of segments in the directory. The " +"bottom half is used as a :ref:`bucket ` index, taken modulo the " +"number of buckets per segment. The :arg:`last_collision` value is used to " +"mark the last matching entry returned by `dir_probe`." +msgstr "" +"与えられた ID の上位半分（64 ビット）は :ref:`セグメント ` " +"インデックスとして使用され、ディレクトリのセグメント数の剰余として扱われます。" +"下位半分は :ref:`バケット ` インデックスとして使用され、" +"セグメント毎のバケット数の剰余として扱われます。:arg:`last_collision` の" +"値は `dir_probe` の戻り値となる最後にマッチするエントリをマークするために使用" +"されます。" + +#: ../../arch/cache/cache-arch.en.rst:487 +msgid "" +"After computing the appropriate bucket, the entries in that bucket are " +"searched to find a match. In this case a match is detected by comparison of " +"the bottom 12 bits of the cache ID (the *cache tag*). The search starts at " +"the base entry for the bucket and then proceeds via the linked list of " +"entries from that first entry. If a tag match is found and there is no :arg:" +"`collision` then that entry is returned and :arg:`last_collision` is " +"updated to that entry. If :arg:`collision` is set, then if it isn't the " +"current match the search continues down the linked list, otherwise :arg:" +"`collision` is cleared and the search continues. The effect of this is that " +"matches are skipped until the last returned match (:arg:`last_collision`) " +"is found, after which the next match (if any) is returned. If the search " +"falls off the end of the linked list then a miss result is returned (if no " +"last collision), otherwise the probe is restarted after clearing the " +"collision on the presumption that the entry for the collision has been " +"removed from the bucket. This can lead to repeats among the returned values " +"but guarantees that no valid entry will be skipped." +msgstr "" +"適切なバケットを算出した後、バケットのエントリはマッチするものを探すために" +"検索されます。この場合、マッチするかがキャッシュキーの下位 12 ビット" +"（ *キャッシュタグ* ）の比較によって検出されます。検索はバケットのベース" +"エントリから開始して、その後先頭のエントリからのエントリ連結リストから" +"進めます。タグのマッチが発見されていてかつ :arg:`collision` が無い場合、" +"エントリは返されてそのエントリへの :arg:`last_collision` が更新されます。 " +":arg:`collision` がセットされていて現在マッチしていない場合、検索は連結" +"リストの次へ続きます。あるいは :arg:`collision` をクリアし、検索を継続します。" +"これにより最後に返されたマッチしたもの （:arg:`last_collision`） が見つかる" +"までマッチングがスキップされ、その後に次のマッチするものが（もしあるなら）" +"返されます。検索が連結リストの最後まで到達した場合、失敗した結果が返される" +"（もし最後の衝突がないなら）、あるいは衝突したエントリがバケットから削除されて" +"いるとの想定の上で、衝突を解消した後に検索が再開されます。この処理は値が返され" +"るまで繰り返すことができますが、正常なエントリがスキップされることがないことを" +"保証します。" + +#: ../../arch/cache/cache-arch.en.rst:498 +msgid "" +"Last collision can therefore be used to restart a probe at a later time. " +"This is important because the match returned may not be the actual object - " +"although the hashing of the cache ID to a bucket and the tag matching is " +"unlikely to create false positives, that is possible. When a fragment is " +"read the full cache ID is available and checked and if wrong, that read can " +"be discarded and the next possible match from the directory found because " +"the cache virtual connection tracks the last collision value." +msgstr "" +"最後の衝突は従って後で検索を再開するのに使用できます。返されたマッチしたものが" +"実際のオブジェクトではないかも知れないため、これは重要です。バケットへの" +"キャッシュ ID のハッシュ化とタグマッチングが偽陽性を発生しそうに無くても、" +"それは使用可能です。フラグメントが読み込まれる際、キャッシュ ID の全てが使用" +"可能でありチェックされた結果誤りがある場合、その読込みは破棄が可能であり" +"キャッシュ仮想接続は最後の衝突値を追跡するためディレクトリから次のマッチする" +"可能性があるものが検索されます。" + +#: ../../arch/cache/cache-arch.en.rst:506 +msgid "Cache Operations" +msgstr "キャッシュ操作" + +#: ../../arch/cache/cache-arch.en.rst:508 +msgid "" +"Cache activity starts after the HTTP request header has been parsed and " +"remapped. Tunneled transactions do not interact with the cache because the " +"headers are never parsed." +msgstr "" +"キャッシュアクティビティは HTTP リクエストヘッダがパースされ、リマップされて" +"から開始します。トンネルされたトランザクションはヘッダがパースされることがない" +"ためキャッシュに影響しません。" + +#: ../../arch/cache/cache-arch.en.rst:510 +msgid "" +"To understand the logic we must introduce the term \"cache valid\" which " +"means something that is directly related to an object that is valid to be " +"put in the cache (e.g. a ``DELETE`` which refers to a URL that is cache " +"valid but cannot be cached itself). This is important because |TS| computes " +"cache validity several times during a transaction and only performs cache " +"operations for cache valid results. The criteria used changes during the " +"course of the transaction as well. This is done to avoid the cost of cache " +"activity for objects that cannot be in the cache." +msgstr "" +"ロジックを理解するため、\"キャッシュバリッド\" という用語を紹介しなければ" +"なりません。これはキャッシュされるのに有効なオブジェクトに直接関係するもの" +"を意味します。（例えばキャッシュバリッドな URL を参照する ``DELETE`` は" +"それ自身はキャッシュできません） |TS| はトランザクション中に何度かキャッシュの" +"正当性を計算してキャッシュバリッドの結果によってのみキャッシュ操作を行うため、" +"この用語は重要です。正当性の基準は同様にトランザクション中の変更を使用しま" +"した。この処理はキャッシュできないオブジェクトの為のキャッシュアクティビティに" +"よるコストを避けるために実行されます。" + +#: ../../arch/cache/cache-arch.en.rst:512 +msgid "" +"The three basic cache operations are lookup, read, and write. We will take " +"deleting entries as a special case of writing where only the volume " +"directory is updated." +msgstr "" +"3 つの基本的なキャッシュ操作は検索、読込み、そして書込みです。エントリの" +"削除はボリュームディレクトリが更新される場合のみの書込みの特殊なケースとして" +"扱います。" + +#: ../../arch/cache/cache-arch.en.rst:514 +msgid "" +"After the client request header is parsed and is determined to be " +"potentially cacheable, a `cache lookup`_ is done. If successful a `cache " +"read`_ is attempted. If either the lookup or the read fails and the content " +"is considered cacheable then a `cache write`_ is attempted." +msgstr "" +"クライアントリクエストヘッダがパースされてキャッシュできると決定された後、 " +"`キャッシュ検索`_ が行われます。成功した場合 `キャッシュ読込み`_ が試みられ" +"ます。検索か読込みのいずれかが失敗してかつコンテンツがキャッシュできると判断" +"される場合、 `キャッシュ書込み`_ が試みられます。" + +#: ../../arch/cache/cache-arch.en.rst:517 +msgid "Cacheability" +msgstr "キャッシャビリティ" + +#: ../../arch/cache/cache-arch.en.rst:519 +msgid "" +"The first thing done with a request with respect to cache is to determine " +"whether it is potentially a valid object for the cache. After initial " +"parsing and remapping this check is done primarily to detect a negative " +"result because if so all further cache processing is skipped -- it will not " +"be put in to the cache nor will a cache lookup be done. There are a number " +"of prerequisites along with configuration options to change them. " +"Additional cacheability checks are done later in the process when more is " +"known about the transaction (such as plugin operations and the origin " +"server response). Those checks are described as appropriate in the sections " +"on the relevant operations." +msgstr "" +"キャッシュに関するリクエストで最初に行われるのは、潜在的にキャッシュするのに" +"有効なオブジェクトであるかどうかを決定することです。最初のパースとリマップの" +"後、このチェックは主にネガティブな結果を検出するために行われます。これはもし" +"ネガティブな結果が出た場合は全ての後のキャッシュ処理がスキップされる、すなわち" +"キャッシュに配置されずキャッシュ検索も実行されなくなるためです。それらを変更" +"する設定オプションに加え、必要条件が数多く存在します。追加のキャッシャビリティ" +"チェックは、トランザクションについてより多くのことが分かった際の処理" +"（プラグイン操作やオリジンサーバレスポンスのような）以降に実行されます。" +"それらのチェックについては関連する操作のセクションで適切に説明します。" + +#: ../../arch/cache/cache-arch.en.rst:521 +msgid "The set of things which can affect cacheability are" +msgstr "キャッシャビリティに影響できる項目のセットは、" + +#: ../../arch/cache/cache-arch.en.rst:523 +msgid "Built in constraints" +msgstr "組込みの制約" + +#: ../../arch/cache/cache-arch.en.rst:524 +msgid "Settings in :file:`records.config`" +msgstr ":file:`records.config` の設定" + +#: ../../arch/cache/cache-arch.en.rst:525 +msgid "Settings in :file:`cache.config`" +msgstr ":file:`cache.config` の設定" + +#: ../../arch/cache/cache-arch.en.rst:526 +msgid "Plugin operations" +msgstr "プラグインの操作" + +#: ../../arch/cache/cache-arch.en.rst:528 +msgid "" +"The initial internal checks, along with their :file:`records.config` " +"overrides[#]_, are done in::" +msgstr "" +"初期の内部チェック、それらの :file:`records.config` を伴ったオーバー" +"ライドは以下の関数内で処理されます。 ::" + +#: ../../arch/cache/cache-arch.en.rst:532 +msgid "The checks that are done are" +msgstr "チェックは以下のように行われます。" + +#: ../../arch/cache/cache-arch.en.rst:537 +msgid "Cacheable Method" +msgstr "キャッシュ可能なメソッド" + +#: ../../arch/cache/cache-arch.en.rst:535 +msgid "" +"The request must be one of ``GET``, ``HEAD``, ``POST``, ``DELETE``, ``PUT``." +msgstr "" +"リクエストは ``GET``, ``HEAD``, ``POST``, ``DELETE``, ``PUT`` のいずれかで" +"なければなりません。" + +#: ../../arch/cache/cache-arch.en.rst:537 +msgid "See ``HttpTransact::is_method_cache_lookupable()``." +msgstr "``HttpTransact::is_method_cache_lookupable()`` を確認してください。" + +#: ../../arch/cache/cache-arch.en.rst:551 +msgid "Dynamic URL" +msgstr "動的 URL" + +#: ../../arch/cache/cache-arch.en.rst:540 +msgid "" +"|TS| tries to avoid caching dynamic content because it's dynamic. A URL is " +"considered dynamic if it" +msgstr "" +"URL が動的であるため |TS| は動的コンテンツのキャッシングを避けようとします。" +"もし以下の条件に当てはまるなら URL は動的であると考えられます。" + +#: ../../arch/cache/cache-arch.en.rst:542 +msgid "is not ``HTTP`` or ``HTTPS``" +msgstr "``HTTP`` や ``HTTPS`` ではない" + +#: ../../arch/cache/cache-arch.en.rst:543 +msgid "has query parameters" +msgstr "クエリパラメータを含む" + +#: ../../arch/cache/cache-arch.en.rst:544 +msgid "ends in ``asp``" +msgstr "``asp`` で終わる" + +#: ../../arch/cache/cache-arch.en.rst:545 +msgid "has ``cgi`` in the path" +msgstr "パスに ``cgi`` を含む" + +#: ../../arch/cache/cache-arch.en.rst:547 +msgid "This check can be disabled by setting a non-zero value for::" +msgstr "このチェックは以下にゼロでない値を設定することで無効にできます::" + +#: ../../arch/cache/cache-arch.en.rst:551 +msgid "" +"In addition if a TTL is set for rule that matches in :file:`cache.config` " +"then this check is not done." +msgstr "" +"加えて、 :file:`cache.config` にマッチするルールに TTL が設定されていたら" +"このチェックは行われません。" + +#: ../../arch/cache/cache-arch.en.rst:554 +msgid "Range Request" +msgstr "レンジリクエスト" + +#: ../../arch/cache/cache-arch.en.rst:554 +msgid "" +"Cache valid only if :ts:cv:`proxy.config.http.cache.range.lookup` in :file:" +"`records.config` is non-zero. This does not mean the range request can be " +"cached, only that it might be satisfiable from the cache." +msgstr "" +":file:`records.config` の :ts:cv:`proxy.config.http.cache.range.lookup` が" +"ゼロでない値である場合に限りキャッシュバリッドです。これはレンジリクエストが" +"キャッシュ可能であることを意味しません。キャッシュから満たされるかもしれないと" +"いうだけです。" + +#: ../../arch/cache/cache-arch.en.rst:556 +msgid "" +"A plugin can call :c:func:`TSHttpTxnReqCacheableSet()` to force the request " +"to be viewed as cache valid." +msgstr "" +"プラグインはリクエストがキャッシュバリッドと見なされる事を強制するため " +":c:func:`TSHttpTxnReqCacheableSet()` を呼び出せます。" + +#: ../../arch/cache/cache-arch.en.rst:558 +msgid "" +"The code appears to check :file:`cache.config` in this logic by setting the " +"``does_config_permit_lookup`` in the ``cache_info.directives`` of the state " +"machine instance but I can find no place where the value is used. The " +"directive ``does_config_permit_storing`` is set and later checked so the " +"directive (from the administrator point of view) is effective in preventing " +"caching of the object." +msgstr "" +"コード上ではこのロジックにおいてステートマシンインスタンスの " +"``cache_info.directives`` の中の ``does_config_permit_lookup`` の値を設定する" +"ことにより :file:`cache.config` をチェックするように見えますが、その値が使用" +"されている箇所は発見できません。 ``does_config_permit_storing`` ディレクティブ" +"が設定されてその後にチェックされるので、このディレクティブは（管理者の観点" +"から）オブジェクトのキャッシュすることを妨げるのに効果的です。" + +#: ../../arch/cache/cache-arch.en.rst:561 +msgid "Cache Lookup" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:563 +msgid "" +"If the initial request is not determined to be cache invalid then a lookup " +"is done. Cache lookup determines if an object is in the cache and if so, " +"where it is located. In some cases the lookup proceeds to read the first " +"``Doc`` from disk to verify the object is still present in the cache." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:565 +msgid "There are three basic steps to a cache lookup." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:567 +msgid "The cache key is computed." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:569 +msgid "" +"This is normally computed using the request URL but it can be overridden :" +"ref:`by a plugin ` . As far as I can tell the cache index string " +"is not stored anywhere, it presumed computable from the client request " +"header." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:571 +msgid "The cache stripe is determined (based on the cache key)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:573 +msgid "" +"The cache key is used as a hash key in to an array of :cpp:class:`Vol` " +"instances. The construction and arrangement of this array is the essence of " +"how volumes are assigned." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:577 +msgid "" +"Various other lookaside directories are checked as well, such as the :ref:" +"`aggregation buffer `." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:579 +msgid "" +"If the directory entry is found the first ``Doc`` is read from disk and " +"checked for validity." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:581 +msgid "" +"This is done in :cpp:func:`CacheVC::openReadStartHead()` or :cpp:func:" +"`CacheVC::openReadStartEarliest()` which are tightly coupled methods." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:583 +msgid "" +"If the lookup succeeds then a more detailed directory entry (struct :cpp:" +"class:`OpenDir`) is created. Note that the directory probe includes a check " +"for an already extant ``OpenDir`` which if found is returned without " +"additional work." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:586 +msgid "Cache Read" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:588 +msgid "" +"Cache read starts after a successful `cache lookup`_. At this point the " +"first ``Doc`` has been loaded in to memory and can be consulted for " +"additional information. This will always contain the HTTP headers for all " +"alternates of the object." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:0 +msgid "Read while write" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:592 +msgid "" +"There is provision in the code to support \"read while write\", that is " +"serving an object from cache in one transaction while it is being written " +"in another. It is unclear to me if this actually works. It must " +"specifically enabled in :file:`records.config` and if not, a cache read " +"will fail if the object is currently be written or updated." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:594 +msgid "" +"At this point an alternate for the object is selected. This is done by " +"comparing the client request to the stored response headers, but it can be " +"controlled by a plugin using ``TS_HTTP_ALT_SELECT_HOOK``." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:596 +msgid "" +"The content can now be checked to see if it is stale by calculating the " +"\"freshness\" of the object. This is essential checking how old the object " +"is by looking at the headers and possibly other metadata (note the headers " +"can't be checked until we've selected an alternate)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:598 +msgid "Most of this work is done in::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:602 +msgid "" +"First the TTL (time to live) value which can be set in:file:`cache.config` " +"is checked if the request matches the configuration file line. This is done " +"based on when the object was placed in cache, not on any data in the " +"headers." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:604 +msgid "" +"Next an internal flag (\"needs-revalidate-once\") is checked if the :file:" +"`cache.config` value \"revalidate-after\" is not set, and if set the object " +"is marked \"stale\"." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:606 +msgid "After these checks the object age is calculated by::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:610 +msgid "" +"and then any configured fuzzing is applied. The limits to this age based on " +"available data is calculated by::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:614 +msgid "" +"How this age is used is determined by the :file:`records.config` value::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:618 +msgid "" +"If this is zero then the built caclulations are used which compare the " +"freshness limits with document age, modified by any of the client supplied " +"cache control values ``max-age``, ``min-fresh``, ``max-stale`` unless " +"explicitly overridden in :file:`cache.config`." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:620 +msgid "" +"If the object is not stale then it is served to the client. If stale the " +"client request may be changed to an ``If Modified Since`` request to " +"revalidate." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:622 +msgid "" +"The request is served using a standard virtual connection tunnel " +"(``HttpTunnel``) with the :cpp:class:`CacheVC` acting as the producer and " +"the client ``NetVC`` acting as the sink. If the request is a range request " +"this can be modified with a transform to select the appropriate parts of " +"the object or, if the request contains a single range, it can use the range " +"acceleration." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:627 +msgid "" +"Range acceleration is done by consulting a fragment offset table attached " +"to the earliest ``Doc`` which contains offsets for all fragments past the " +"first. This allows loading the fragment containing the first requested byte " +"immediately rather than performing reads on the intermediate fragments." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:632 +msgid "Cache Write" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:634 +msgid "" +"Writing to cache is handled by an instance of the class :cpp:class:" +"`CacheVC`. This is a virtual connection which receives data and writes it " +"to cache, acting as a sink. For a standard transaction data transfers " +"between virtual connections (*VConns*) are handled by :cpp:class:" +"HttpTunnel. Writing to cache is done by attaching a ``CacheVC`` instance as " +"a tunnel consumer. It therefore operates in parallel with the virtual " +"connection that transfers data to the client. The data does not flow to the " +"cache and then to the client, it is split and goes both directions in " +"parallel. This avoids any data synchronization issues between the two." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:0 +msgid "Writing to disk" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:643 +msgid "" +"The actual write to disk is handled in a separate thread dedicated to I/O " +"operations, the AIO threads. The cache logic marshals the data and then " +"hands the operation off to the AIO thread which signals back once the " +"operation completes." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:647 +msgid "" +"While each ``CacheVC`` handles its transactions independently, they do " +"interact at the volume level as each ``CacheVC`` makes calls to the volume " +"object to write its data to the volume content. The ``CacheVC`` accumulates " +"data internally until either the transaction is complete or the amount of " +"data to write exceeds the target fragment size. In the former case the " +"entire object is submitted to the volume to be written. In the latter case " +"a target fragment size amount of data is submitted and the ``CacheVC`` " +"continues to operate on subsequent data. The volume in turn places these " +"write requests in an holding area called the `aggregation buffer`_." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:654 +msgid "" +"For objects under the target fragment size there is no consideration of " +"order, the object is simply written to the volume content. For larger " +"objects the earliest ``Doc`` is written first and the first ``Doc`` written " +"last. This provides some detection ability should the object be " +"overwritten. Because of the nature of the write cursor no fragment after " +"the first fragment (in the earliest ``Doc``) can be overwritten without " +"also overwriting that first fragment (since we know at the time the object " +"was finalized in the cache the write cursor was at the position of the " +"first ``Doc``)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:661 +msgid "" +"It is the responsibility of the ``CacheVC`` to not submit writes that " +"exceed the target fragment size." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:666 +msgid "Update" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:668 +msgid "" +"Cache write also covers the case where an existing object in the cache is " +"modified. This occurs when" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:670 +msgid "" +"A conditional request is made to the origin server and a ``304 - Not " +"Modified`` response is received." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:671 +msgid "" +"An alternate of the object is retrieved from an origin server and added to " +"the object." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:672 +msgid "" +"An alternate of the object is removed (e.g., due to a ``DELETE`` request)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:674 +msgid "" +"In every case the metadata for the object must be modified. Because |TS| " +"never updates data already in the cache this means the first ``Doc`` will " +"be written to the cache again and the volume directory entry updated. " +"Because a client request has already been processed the first ``Doc`` has " +"been read from cache and is in memory. The alternate vector is updated as " +"appropriate (an entry added or removed, or changed to contain the new HTTP " +"headers), and then written to disk. It is possible for multiple alternates " +"to be updated by different ``CacheVC`` instances at the same time. The only " +"contention is the first ``Doc``, the rest of the data for each alternate is " +"completely independent." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:684 +msgid "Aggregation Buffer" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:686 +msgid "" +"Disk writes to cache are handled through an *aggregation buffer*. There is " +"one for each :cpp:class:`Vol` instance. To minimize the number of system " +"calls data is written to disk in units of roughly :ref:`target fragment " +"size ` bytes. The algorithm used is simple - data is " +"piled up in the aggregation buffer until no more will fit without going " +"over the targer fragment size, at which point the buffer is written to disk " +"and the volume directory entries for objects with data in the buffer are " +"updated with the actual disk locations for those objects (which are " +"determined by the write to disk action). After the buffer is written it is " +"cleared and process repeats. There is a special lookup table for the " +"aggregation buffer so that object lookup can find cache data in that memory." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:694 +msgid "" +"Because data in the aggregation buffer is visible to other parts of the " +"cache, particularly `cache lookup`_, there is no need to push a partial " +"filled aggregation buffer to disk. In effect any such data is effectively " +"memory cached until enough additional cache content arrives to fill the " +"buffer." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:698 +msgid "" +"The target fragment size has little effect on small objects because the " +"fragment sized is used only to parcel out disk write operations. For larger " +"objects the effect very significant as it causes those objects to be broken " +"up in to fragments at different locations on in the volume. Each fragment " +"write has its own entry in the volume directory which are computational " +"chained (each cache key is computed from the previous one). If possible a " +"fragment table is accumulated in the earliest ``Doc`` which has the offsets " +"of the first byte for each fragment." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:705 +msgid "Evacuation Mechanics" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:707 +msgid "" +"By default the write cursor will overwrite (de facto evict from cache) " +"objects as it proceeds once it has gone around the cache stripe at least " +"once. In some cases this is not acceptable and the object is *evacuated* by " +"reading it from the cache and then writing it back to cache which moves the " +"physical storage of the object from in front of the write cursor to behind " +"the write cursor. Objects that are evacuated are handled in this way based " +"on data in stripe data structures (attached to the :cpp:class:`Vol` " +"instance)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:713 +msgid "" +"Evacuation data structures are defined by dividing up the volume content in " +"to a disjoint and contiguous set of regions of ``EVACUATION_BUCKET_SIZE`` " +"bytes. The :cpp:member:`Vol::evacuate` member is an array with an element " +"for each evacuation region. Each element is a doubly linked list of :cpp:" +"class:`EvacuationBlock` instances. Each instance contains a :cpp:class:" +"`Dir` that specifies the fragment to evacuate. It is assumed that an " +"evacuation block is placed in the evacuation bucket (array element) that " +"corresponds to the evacuation region in which the fragment is located " +"although no ordering per bucket is enforced in the linked list (this " +"sorting is handled during evacuation). Objects are evacuated by specifying " +"the first or earliest fragment in the evactuation block. The evactuation " +"operation will then continue the evacuation for subsequent fragments in the " +"object by adding those fragments in evacuation blocks. Note that the actual " +"evacuation of those fragments is delayed until the write cursor reaches the " +"fragments, it is not ncessarily done at the time the first / earliest " +"fragment is evacuated." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:724 +msgid "" +"There are two types of evacuations, reader based and forced. The " +"``EvacuationBlock`` has a reader count to track this. If the reader count " +"is zero, then it is a forced evacuation and the the target, if it exists, " +"will be evacuated when the write cursor gets close. If the reader value is " +"non-zero then it is a count of entities that are currently expecting to be " +"able to read the object. Readers increment the count when they require read " +"access to the object, or create the ``EvacuationBlock`` with a count of 1. " +"When a reader is finished with the object it decrements the count and " +"removes the ``EvacuationBlock`` if the count goes to zero. If the " +"``EvacuationBlock`` already exists with a count of zero, the count is not " +"modified and the number of readers is not tracked, so the evacuation is " +"valid as long as the object exists." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:732 +msgid "" +"Evacuation is driven by cache writes, essentially in :cpp:member:`Vol::" +"aggWrite`. This method processes the pending cache virtual connections that " +"are trying to write to the stripe. Some of these may be evacuation virtual " +"connections. If so then the completion callback for that virtual connection " +"is called as the data is put in to the aggregation buffer." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:737 +msgid "" +"When no more cache virtual connections can be processed (due to an empty " +"queue or the aggregation buffer filling) then :cpp:member:`Vol::evac_range` " +"is called to clear the range to be overwritten plus an additional :ts:const:" +"`EVACUATION_SIZE` range. The buckets covering that range are checked. If " +"there are any items in the buckets a new cache virtual connection (a \"doc " +"evacuator\") is created and used to read the evacuation item closest to the " +"write cursor (i.e. with the smallest offset in the stripe) instead of the " +"aggregation write proceeding. When the read completes it is checked for " +"validity and if valid, the cache virtual connection for it is placed at the " +"front of the write queue for the stripe and the write aggregation resumed." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:745 +msgid "" +"Before doing a write, the method :cpp:func:`Vol::evac_range()` is called to " +"start an evacuation. If any fragments are found in the buckets in the range " +"the earliest such fragment (smallest offset, closest to the write cursor) " +"is selected and read from disk and the aggregation buffer write is " +"suspended. The read is done via a cache virtual connection which also " +"effectively serves as the read buffer. Once the read is complete, that " +"cache virtual connection instance (the \"doc evacuator\") is place at the " +"front of the stripe write queue and written out in turn. Because the " +"fragment data is now in memory it is acceptable to overwrite the disk image." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:752 +msgid "" +"Note that when normal stripe writing is resumed, this same check is done " +"again, each time evauating (if needed) a fragment and queuing them for " +"writing in turn." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:755 +msgid "" +"Updates to the directory are done when the write for the evacuated fragment " +"completes. Multi-fragment objects are detected after the read completes for " +"a fragment. If it is not the first fragment then the next fragment is " +"marked for evacuation (which in turn, when it is read, will pull the " +"subsequent fragment). The logic doesn't seem to check the length and " +"presumes that the end of the alternate is when the next key is not in the " +"directory." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:760 +msgid "" +"This interacts with the \"one at a time\" strategy of the aggregation write " +"logic. If a fragment is close to the fragment being evacuated it may end up " +"in the same evacuation bucket. Because the aggregation write checks every " +"time for the \"next\" fragment to evacuate it will find that next fragment " +"and evacuate it before it is overwritten." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:777 +msgid "Evacuation Operation" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:779 +msgid "" +"The primary source of fragments to be evacuated are active fragments. That " +"is fragments which are currently open, to be read or written. This is " +"tracked by the reader value in the evacuation blocks noted above." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:781 +msgid "" +"If object pinning is enabled then a scan is done on a regular basis as the " +"write cursor moves to detected pinned objects and mark them for evacuation." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:783 +msgid "" +"Fragments can also be evacuated through *hit evacuation*. This is " +"configured by :ts:cv:`proxy.config.cache.hit_evacuate_percent` and :ts:cv:" +"`proxy.config.cache.hit_evacuate_size_limit`. When a fragment is read it is " +"checked to see if it is close and in front of the write cursor, close being " +"less than the specified percent of the size of the stripe. If set at the " +"default value of 10, then if the fragment is withing 10% of the size of the " +"stripe it is marked for evacuation. This is cleared if the write cursor " +"passes through the fragment while it remains open (as all open objects are " +"evacuated). If when the object is closed the fragment is still marked then " +"it is placed in the appropriate evacuation bucket." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:786 +msgid "Initialization" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:788 +msgid "" +"Initialization starts with an instance of :cpp:class:`Store` reading the " +"storage configuration file, by default :file:`storage.config`. For each " +"valid element in the file an instance of :cpp:class:`Span` is created. " +"These are of basically four types," +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:792 +msgid "File" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:793 +msgid "Directory" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:794 +msgid "Disk" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:795 +msgid "Raw device" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:804 +msgid "" +"After configuration initialization the cache processor is started by " +"calling :ccp:func:`CacheProcessor::start()`. This does a number of things." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:838 +msgid "Footnotes" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:839 +msgid "" +"`Work is under way `_ on " +"extending this to include objects that are in the ram cache." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:842 +msgid "" +"This linked list is mostly ignored in later processing, causing all but one " +"file or directory storage units on the same device to be ignored. See " +"`TS-1869 `_." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:845 +msgid "" +"It is unclear to me how that can happen, as the offsets are computed later " +"and should all be zero at the time the spans are coalesced, and as far as I " +"can tell the sort / coalesce is only done during initialization." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:102 +msgid "cache directory" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:108 +msgid "directory entry" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:109 +msgid "fragment" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:110 +msgid "cache ID" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:267 +msgid "alternate" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:462 +msgid "DIR_DEPTH" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:462 +msgid "index segment" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:462 +msgid "index buckets" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:26 +msgid "" +"In addition to an HTTP proxy, |ATS| is also an HTTP cache. |TS| can cache " +"any octet stream although it currently supports only those octet streams " +"delivered by the HTTP protocol. When such a stream is cached (along with " +"the HTTP protocol headers) it is termed an :term:`object ` in " +"the cache. Each object is identified by a globally unique value called a :" +"term:`cache key`." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:43 +msgid "" +"The following sections describe how persistent cache data is structured. |" +"TS| treats its persisent storage an undifferentiated collection of bytes, " +"assuming no other structure to it. In particular it does not use the file " +"system of the host operating system. If a file is used it is used only to " +"mark out the set of bytes to be used." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:50 +msgid "" +"The raw storage for the |TS| cache is configured in :file:`storage.config`. " +"Each line in the file defines a :term:`cache span` which is treated as a " +"uniform persistent store." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:58 +msgid "" +"This storage organized in to a set of :term:`cache volume`\\ s which are " +"defined in :file:`volume.config` for the purposes of the administrator. " +"These are the units that used for all other administator level " +"configuration." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:61 +msgid "" +"Cache volumes can be defined by a percentage of the total storage or an " +"absolute amount of storage. By default each cache volume is spread across " +"all of the cache spans for robustness. The intersection of a cache volume " +"and a cache span is a :term:`cache stripe`. Each cache span is divided in " +"to cache stripes and each cache volume is a collection of those stripes." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:76 +msgid "" +"Cache stripes are the fundamental unit of cache for the implementation. A " +"cached object is stored entirely in a single stripe, and therefore in a " +"single cache span - objects are never split across cache spans or volumes. " +"Objects are assigned to a stripe (and hence to a cache volume) " +"automatically based on a hash of the URI used to retrieve the object from " +"the origin server. It is possible to configure this to a limited extent in :" +"file:`hosting.config` which supports content from specific host or domain " +"to be stored on specific cache volumes. In addition, as of version 4.0.1 it " +"is possible to control which cache spans (and hence, which cache stripes) " +"are contained in a specific cache volume." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:114 +msgid "" +"Content in a stripe is tracked via a directory. We call each element of the " +"directory a \"directory entry\" and each is represented by :cpp:class:" +"`Dir`. Each entry refers to a chunk of contiguous storage in the cache. " +"These are referred to variously as \"fragments\", \"segments\", \"docs\" / " +"\"documents\", and a few other things. This document will use the term " +"\"fragment\" as that is the most common reference in the code. The term " +"\"Doc\" (for :cpp:class:`Doc`) will be used to refer to the header data for " +"a fragment. Overall the directory is treated as a hash with the :term:" +"`cache ID` as the key. See :ref:`directory probing ` " +"for how the cache ID is used to locate a directory entry. The cache ID is " +"in turn computed from a :term:`cache key` which by default is the URL of " +"the content." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:135 +msgid "" +"Each entry stores an offset in the stripe and a size. The size stored in " +"the directory entry is an :ref:`approximate size ` which is at " +"least as big as the actual data in the fragment. Exact size data is stored " +"in the fragment header on disk." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:141 +msgid "" +"Data in HTTP headers cannot be examined without disk I/O. This includes the " +"original URL for the object. The cache key is not stored explicitly and " +"therefore cannot be reliably retrieved." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:144 +msgid "" +"The directory is a hash table that uses `chaining `_ for collision " +"resolution. Because each entry is small they are used directly as the list " +"header of the hash bucket." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:151 +msgid "" +"Chaining is implemented by imposing grouping structures on the entries in a " +"directory. The first level grouping is a :term:`directory bucket`. This is " +"a fixed number (currently 4 - defined as ``DIR_DEPTH``) of entries. This " +"serves to define the basic hash buckets with the first entry in each cache " +"bucket serving as the root of the hash bucket." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:158 +msgid "" +"The term \"bucket\" is used in the code to mean both the conceptual bucket " +"for hashing and for a structural grouping mechanism in the directory and so " +"these will be qualified as needed to distinguish them. The unqualified term " +"\"bucket\" is almost always used to mean the structural grouping in the " +"directory." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:162 +msgid "" +"Directory buckets are grouped in to :term:`segments `. " +"All segments in a stripe have the same number of buckets. The number of " +"segments in a stripe is chosen so that each segment has as many buckets as " +"possible without exceeding 65535 (2\\ :sup:`16`\\ -1) entries in a segment." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:169 +msgid "" +"Each directory entry has a previous and next index value which is used to " +"link entries in the same segment. Because no segment has more than 65535 " +"entries 16 bits suffices for storing the index values. The stripe header " +"contains an array of entry indices which are used as the roots of entry " +"free lists, one for each segment. Active entries are stored via the bucket " +"structure. When a stripe is initialized the first entry in each bucket is " +"zeroed (marked unused) and all other entries are put in the corresponding " +"segment free list in the stripe header. This means the first entry of each " +"directory bucket is used as the root of a hash bucket and is therefore " +"marked unused rather than being put a free list. The other entries in the " +"directory bucket are preferentially preferred for adding to the " +"corresponding hash bucket but this is not required. The segment free lists " +"are initialized such that the extra bucket entries are added in order - all " +"the seconds, then the thirds, then the fourths. Because the free lists are " +"FIFOs this means extra entries will be selected from the fourth entries " +"across all the buckets first, then the thirds, etc. When allocating a new " +"directory entry in a bucket the entries are searched from first to last, " +"which maximizes bucket locality (that is, cache IDs that map to the same " +"hash bucket will also tend to use the same directory bucket)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:185 +msgid "" +"Entries are removed from the free list when used and returned when no " +"longer in use. When a fragment needs to be put in to the directory the " +"cache ID is used to locate a hash bucket (which also determines the segment " +"and directory bucket). If the first entry in the directory bucket is marked " +"unused, it is used. If not then the other entries in the bucket are " +"searched and if any are on the free list, that entry is used. If none are " +"available then the first entry on the segment free list is used. This entry " +"is attached to the hash bucket via the same next and previous indices used " +"for the free list so that it can be found when doing a lookup of a cache ID." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:575 +msgid "" +"The cache stripe directory :ref:`is probed ` using " +"the index key computed from the cache key." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:797 +msgid "" +"After creating all the `Span` instances they are grouped by device id to " +"internal linked lists attached to the :cpp:member:`Store::disk` array [#]_. " +"Spans that refer to the same directory, disk, or raw device are coalesced " +"in to a single span. Spans that refer to the same file with overlapping " +"offsets are also coalesced [#]_. This is all done in :c:func:" +"`ink_cache_init()` called during startup." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:802 +msgid "" +"The span logic is also used by the HostDB and more than one otherwise " +"inexplicable feature is provided by the span logic for that module." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:807 +msgid "" +"For each valid span, an instance of :cpp:class:`CacheDisk` is created. This " +"class is a continuation and so can be used to perform potentially blocking " +"operations on the span. The primary use of these is to be passed to the AIO " +"threads as the callback when an I/O operation completes. These are then " +"dispatched to AIO threads to perform storage unit initialization. After all " +"of those have completed, the resulting storage is distributed across the " +"volumes in :c:func:`cplist_reconfigure`. The :cpp:class:`CacheVol` " +"instances are created at this time." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:813 +msgid "" +"Cache stripe assignment setup is done once all stripes have initialized " +"(that is, the stripe header information has been successfully read from " +"disk for all stripes). The assignment information is stored as an array of " +"indices. These are indices in to an array of stripes. Both the assignment " +"and the stripe arrays are stored in an instance of :cpp:class:" +"`CacheHostRecord`. Assignment initialization consists of populating the " +"assignment array which is much larger than the stripe array." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:819 +msgid "" +"There is an instance of :cpp:class:`CacheHostRecord` for each line in :file:" +"`hosting.config` and one \"generic\" record. For the configured instances " +"the set of stripes is determined from the cache volume specified in the " +"line. If no lines are specified all stripes are placed in the generic " +"record, otherwise only those stripes marked as default are placed in the " +"generic record." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:822 +msgid "" +"If hosting records are specified it is an error to not specify at least one " +"default cache volume." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:824 +msgid "" +"The assignment table is initialized in :c:func:`build_vol_hash_table` which " +"is called for each :cpp:class:`CacheHostRecord` instance. For each strip in " +"the host record a sequence of pseudo-random numbers is generated, starting " +"with the folded hash of the stripe hash identifier, which is the device " +"path followed by the skip and size values for that stripe, making it " +"unique. This also makes the sequence deterministic for any particular " +"stripe. Each stripe gets one number in its sequence for every " +"`VOL_HASH_ALLOC_SIZE` (8 MB currently) of storage. These numbers are paired " +"with the stripe index, combined across all stripes, then sorted by the " +"random values. The resulting array is sampled for every slot in the stripe " +"assignment table by dividing the maximum random value by the size of the " +"assignment table and using the value midway between each multiple of the " +"result of the division. The coalesced psuedo-random sequence is scanned for " +"each sample in turn and the first number not greater than the sample is " +"found. The stripe associated with that value is used for that assignment " +"table entry." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:835 +msgid "" +"While this procedure is determinstic it is sensitive to initial conditions, " +"including the size of each stripe." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/cache-data-structures.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-data-structures.en.po new file mode 100644 index 00000000000..253023ad810 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-data-structures.en.po @@ -0,0 +1,273 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/cache/cache-data-structures.en.rst:19 +msgid "Cache Data Structures" +msgstr "キャッシュデータ構造" + +#: ../../arch/cache/cache-data-structures.en.rst:25 +msgid "" +"An open directory entry. It contains all the information of a :cpp:class:" +"`Dir` plus additional information from the first :cpp:class:`Doc`." +msgstr "" +"オープンされたディレクトリエントリ。 :cpp:class:`Dir` と、それに加えて 先頭" +"の :cpp:class:`Doc` の全情報を含みます。" + +#: ../../arch/cache/cache-data-structures.en.rst:29 +msgid "A virtual connection class which accepts input for writing to cache." +msgstr "キャッシュへ書込む入力を受け付ける仮想接続クラス。" + +#: ../../arch/cache/cache-data-structures.en.rst:33 +msgid "Do the initial read for a cached object." +msgstr "キャッシュされたオブジェクトの初回の読込みを実行します。" + +#: ../../arch/cache/cache-data-structures.en.rst:37 +msgid "Do the initial read for an alternate of an object." +msgstr "オブジェクトの代替の初回の読込みを実行します。" + +#: ../../arch/cache/cache-data-structures.en.rst:41 +msgid "" +"Data transfer driver. This contains a set of *producers*. Each producer is " +"connected to one or more *consumers*. The tunnel handles events and buffers " +"so that data moves from producers to consumers. The data, as much as " +"possible, is kept in reference counted buffers so that copies are done only " +"when the data is modified or for sources (which acquire data from outside |" +"TS|) and sinks (which move data to outside |TS|)." +msgstr "" +"データ転送ドライバ。これは *プロデューサ* のセットを含みます。各プロデューサ" +"は一つ以上の *コンシューマ* に接続されます。トンネルは、プロデューサからコン" +"シューマへデータを移動させる為に、イベントとバッファを扱います。データは、" +"データが修正される時のみ、またはソース(|TS| の外からデータを取得するもの)と" +"シンク(|TS| の外へデータを移動するもの)のためにコピーが実行されるため、可能" +"な限り参照カウントバッファに維持されます。" + +#: ../../arch/cache/cache-data-structures.en.rst:45 +msgid "Holds the data from a line in :file:`cache.config`." +msgstr ":file:`cache.config` のある行からデータを保持します。" + +#: ../../arch/cache/cache-data-structures.en.rst:49 +msgid "" +"Defined in |P-CacheHttp.h|_. This is an array of :cpp:class:`HTTPInfo` " +"objects and serves as the respository of information about alternates of an " +"object. It is marshaled as part of the metadata for an object in the cache." +msgstr "" +"|P-CacheHttp.h|_ で定義されます。これは :cpp:class:`HTTPInfo` オブジェクトの" +"配列であり、オブジェクトの代替に関する情報のリポジトリとして提供します。それ" +"はキャッシュ内のオブジェクトのメタデータ部分に配置されます。" + +#: ../../arch/cache/cache-data-structures.en.rst:53 +#: ../../arch/cache/cache-data-structures.en.rst:63 +msgid "Defined in |HTTP.h|_." +msgstr "|HTTP.h|_ で定義されます。" + +#: ../../arch/cache/cache-data-structures.en.rst:55 +msgid "" +"This class is a wrapper for :cpp:class:`HTTPCacheAlt`. It provides the " +"external API for accessing data in the wrapped class. It contains only a " +"pointer (possibly ``NULL``) to an instance of the wrapped class." +msgstr "" +"このクラスは :cpp:class:`HTTPCacheAlt` のラッパーです。ラップされたクラス内" +"のデータへのアクセスのための外部 API を提供します。ラップされたクラスのイン" +"スタンスへのポインター(``NULL`` の可能性がある)のみ保持します。" + +#: ../../arch/cache/cache-data-structures.en.rst:59 +msgid "A typedef for :cpp:class:`HTTPInfo`." +msgstr ":cpp:class:`HTTPInfo` の typedef 。" + +#: ../../arch/cache/cache-data-structures.en.rst:65 +msgid "" +"This is the metadata for a single alternate for a cached object. In " +"contains among other data" +msgstr "" +"キャッシュオブジェクトの単一の代替のメタデータです。下記の他データを含みま" +"す。" + +#: ../../arch/cache/cache-data-structures.en.rst:67 +msgid "The key for the earliest ``Doc`` of the alternate." +msgstr "代替の earliest ``Doc`` のキー。" + +#: ../../arch/cache/cache-data-structures.en.rst:68 +msgid "The request and response headers." +msgstr "リクエストヘッダとレスポンスヘッダ。" + +#: ../../arch/cache/cache-data-structures.en.rst:69 +msgid "The fragment offset table. [#]_" +msgstr "フラグメントオフセットテーブル。 [#]_" + +#: ../../arch/cache/cache-data-structures.en.rst:70 +msgid "Timestamps for request and response from origin server." +msgstr "オリジンサーバからのリクエストとレスポンスのタイムスタンプ。" + +#: ../../arch/cache/cache-data-structures.en.rst:74 +msgid "Record for evacuation." +msgstr "退避のためのレコード。" + +#: ../../arch/cache/cache-data-structures.en.rst:78 +msgid "This represents a storage unit inside a cache volume." +msgstr "キャッシュボリューム内においてストレージユニットを表します。" + +#: ../../arch/cache/cache-data-structures.en.rst:82 +msgid "" +"The number of segments in the volume. This will be roughly the total number " +"of entries divided by the number of entries in a segment. It will be " +"rounded up to cover all entries." +msgstr "" +"ボリュームのセグメント数。セグメント内のエントリ数で分割されたエントリのおお" +"よその合計数。全エントリをカバーするように丸め込まれます。" + +#: ../../arch/cache/cache-data-structures.en.rst:86 +msgid "" +"The number of buckets in the volume. This will be roughly the number of " +"entries in a segment divided by ``DIR_DEPTH``. For currently defined values " +"this is around 16,384 (2^16 / 4). Buckets are used as the targets of the " +"index hash." +msgstr "" +"ボリュームのバケット数。 ``DIR_DEPTH`` で分割されるセグメント内のおおよその" +"エントリ数。現在は約 16,384 (2^16 / 4) で定義されます。バケットはインデック" +"スハッシュの対象として使用されます。" + +#: ../../arch/cache/cache-data-structures.en.rst:90 +msgid "" +"Array of of :cpp:class:`EvacuationBlock` buckets. This is sized so there is " +"one bucket for every evacuation span." +msgstr "" +":cpp:class:`EvacuationBlock` バケットの配列。これは、退避スパンごとに一つの" +"バケットを持つようなサイズになります。" + +#: ../../arch/cache/cache-data-structures.en.rst:94 +msgid "Length of stripe in bytes." +msgstr "バイト単位のストライプ長。" + +#: ../../arch/cache/cache-data-structures.en.rst:98 +msgid "" +"Start an evacuation if there is any :cpp:class:`EvacuationBlock` in the " +"range from *low* to *high*. Return 0 if no evacuation was started, non-zero " +"otherwise." +msgstr "" +"*low* から *high* の範囲に任意の :cpp:class:`EvacuationBlock` がある場合、退" +"避を開始します。退避が開始されなかった場合は 0 を、それ以外は非 0 を返しま" +"す。" + +#: ../../arch/cache/cache-data-structures.en.rst:102 +msgid "A cache volume as described in :file:`volume.config`." +msgstr ":file:`volume.config` で記述されるキャッシュボリューム。" + +#: ../../arch/cache/cache-data-structures.en.rst:106 +msgid "Defined in |P-CacheVol.h|_." +msgstr "|P-CacheVol.h|_ で定義されます。" + +#: ../../arch/cache/cache-data-structures.en.rst:110 +msgid "Validity check value. Set to ``DOC_MAGIC`` for a valid document." +msgstr "" +"正当性チェック値。正当なドキュメントには ``DOC_MAGIC`` が設定されます。" + +#: ../../arch/cache/cache-data-structures.en.rst:114 +msgid "" +"The length of this segment including the header length, fragment table, and " +"this structure." +msgstr "" +"ヘッダ長、フラグメントテーブル、この構造体を含む、このセグメントの長さ。" + +#: ../../arch/cache/cache-data-structures.en.rst:118 +msgid "" +"Total length of the entire document not including meta data but including " +"headers." +msgstr "メタデータを含まない、ヘッダを含むドキュメント全体の長さ。" + +#: ../../arch/cache/cache-data-structures.en.rst:122 +msgid "" +"First index key in the document (the index key used to locate this object " +"in the volume index)." +msgstr "" +"ドキュメントの最初のインデックスキー。（インデックスキーはボリュームインデッ" +"クスにおいてこのオブジェクトを見つけるのに使用されます。)" + +#: ../../arch/cache/cache-data-structures.en.rst:126 +msgid "" +"The index key for this fragment. Fragment keys are computationally chained " +"so that the key for the next and previous fragments can be computed from " +"this key." +msgstr "" +"このフラグメントのインデックスキー。前後のフラグメントのキーがこのキーから計" +"算出来るように、フラグメントキーは計算的に繋がっています。" + +#: ../../arch/cache/cache-data-structures.en.rst:130 +msgid "" +"Document header (metadata) length. This is not the length of the HTTP " +"headers." +msgstr "ドキュメントヘッダ(メタデータ)長。 HTTP ヘッダの長さではありません。" + +#: ../../arch/cache/cache-data-structures.en.rst:134 +msgid "" +"Fragment type. Currently only `CACHE_FRAG_TYPE_HTTP` is used. Other types " +"may be used for cache extensions if those are ever used / implemented." +msgstr "" +"フラグメントタイプ。現在、 `CACHE_FRAG_TYPE_HTTP` のみ使用されます。キャッ" +"シュ拡張がいつか使用/実装されれば、他のタイプが使用されるかもしれません。" + +#: ../../arch/cache/cache-data-structures.en.rst:138 +msgid "" +"Fragment table length, if any. Only the first ``Doc`` in an object should " +"contain a fragment table." +msgstr "" +"もしあるなら、フラグメントテーブル長。オブジェクトの、先頭の ``Doc`` のみが" +"フラグメントテーブルを持つべきです。" + +#: ../../arch/cache/cache-data-structures.en.rst:140 +msgid "" +"The fragment table is a list of offsets relative to the HTTP content (not " +"counting metadata or HTTP headers). Each offset is the byte offset of the " +"first byte in the fragment. The first element in the table is the second " +"fragment (what would be index 1 for an array). The offset for the first " +"fragment is of course always zero and so not stored. The purpose of this is " +"to enable a fast seek for range requests - given the first ``Doc`` the " +"fragment containing the first byte in the range can be computed and loaded " +"directly without further disk access." +msgstr "" +"フラグメントテーブルは、 HTTP コンテンツ(メタデータや HTTP ヘッダは含みませ" +"ん)に関係したオフセットのリストです。各オフセットは、フラグメントの最初のバ" +"イトのバイトオフセットです。テーブルの最初の要素は、二番目のフラグメントで" +"す。(配列のインデックス 1 となるでしょう) 最初のフラグメントのオフセットはも" +"ちろん常にゼロであり、保存されません。この目的は、レンジリクエストの高速な検" +"索を可能にすることです。先頭の ``Doc`` が指定されると、範囲の最初のバイトを" +"含むフラグメントはそれ以上のディスクアクセス無しに、直接計算して読み込むこと" +"ができます。" + +#: ../../arch/cache/cache-data-structures.en.rst:142 +msgid "Removed as of version 3.3.0." +msgstr "バージョン 3.3.0 で削除されました。" + +#: ../../arch/cache/cache-data-structures.en.rst:146 +#: ../../arch/cache/cache-data-structures.en.rst:150 +msgid "Unknown." +msgstr "不明。" + +#: ../../arch/cache/cache-data-structures.en.rst:154 +msgid "Flag and timer for pinned objects." +msgstr "ピン留めされたオブジェクトのフラグとタイマー。" + +#: ../../arch/cache/cache-data-structures.en.rst:158 +msgid "Unknown. (A checksum of some sort)" +msgstr "不明。(何らかのチェックサム)" + +#: ../../arch/cache/cache-data-structures.en.rst:163 +msgid "Footnotes" +msgstr "脚注" + +#: ../../arch/cache/cache-data-structures.en.rst:164 +msgid "" +"Changed in version 3.2.0. This previously resided in the first ``Doc`` but " +"that caused different alternates to share the same fragment table." +msgstr "" +"バージョン 3.2.0 で変更されました。以前は先頭の ``Doc`` 内で持ちましたが、同" +"一フラグメントテーブルを共有するために異なる代替を引き起こしました。" diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/cache.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/cache.en.po new file mode 100644 index 00000000000..d2baa3a1ea6 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache.en.po @@ -0,0 +1,20 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/cache/cache.en.rst:19 +msgid "Apache Traffic Server Cache" +msgstr "" + +#: ../../arch/cache/cache.en.rst:21 +msgid "Contents:" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/ram-cache.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/ram-cache.en.po new file mode 100644 index 00000000000..c75039b25e8 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/ram-cache.en.po @@ -0,0 +1,256 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-15 22:31+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/cache/ram-cache.en.rst:22 +msgid "Ram Cache" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:25 +msgid "New Ram Cache Algorithm (CLFUS)" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:27 +msgid "" +"The new Ram Cache uses ideas from a number of cache replacement policies " +"and algorithms, including LRU, LFU, CLOCK, GDFS and 2Q, called CLFUS " +"(Clocked Least Frequently Used by Size). It avoids any patented algorithms " +"and includes the following features:" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:29 +msgid "" +"Balances Recentness, Frequency and Size to maximize hit rate (not byte hit " +"rate)." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:30 +msgid "" +"Is Scan Resistant and extracts robust hit rates even when the working set " +"does not fit in the Ram Cache." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:31 +msgid "" +"Supports compression at 3 levels fastlz, gzip(libz), and xz(liblzma). " +"Compression can be moved to another thread." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:32 +msgid "" +"Has very low CPU overhead, only little more than a basic LRU. Rather than " +"using an O(lg n) heap, it uses a probabilistic replacement policy for O(1) " +"cost with low C." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:33 +msgid "" +"Has relatively low memory overhead of approximately 200 bytes per object in " +"memory." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:35 +msgid "" +"The rational for emphasizing hit rate over byte hit rate is that the " +"overhead of pulling more bytes from secondary storage is low compared to " +"the cost of a request." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:37 +msgid "" +"The Ram Cache consists of an object hash fronting 2 LRU/CLOCK lists and a " +"\"Seen\" hash table. The first \"Cached\" list contains objects in memory " +"while the second contains a \"History\" of objects which have either " +"recently been in memory or are being considered for keeping in memory. The " +"\"Seen\" hash table is used to make the algorithm scan resistant." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:39 +msgid "The list entries record the following information:" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:41 +msgid "key - 16 byte unique object identifier" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:42 +msgid "" +"auxkeys - 8 bytes worth of version number (in our system the block in the " +"partition). When the version of an object changes old entries are purged " +"from the cache." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:43 +msgid "hits - number of hits within this clock period" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:44 +msgid "size - the size of the object in the cache" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:45 +msgid "" +"len - the actual length of the object (differs from size because of " +"compression and padding)" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:46 +msgid "compressed_len - the compressed length of the object" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:47 +msgid "compressed (none, fastlz, libz, liblzma)" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:48 +msgid "uncompressible (flag)" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:49 +msgid "" +"copy - whether or not this object should be copied in and copied out (e.g. " +"HTTP HDR)" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:50 +msgid "LRU link" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:51 +msgid "HASH link" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:52 +msgid "IOBufferData (smart point to the data buffer)" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:55 +msgid "" +"The interface to the cache is Get and Put operations. Get operations check " +"if an object is in the cache and are called on a read attempt. The Put " +"operation decides whether or not to cache the provided object in memory. " +"It is called after a read from secondary storage." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:58 +msgid "Seen Hash" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:60 +msgid "" +"The Seen List becomes active after the Cached and History lists become full " +"after a cold start. The purpose is to make the cache scan resistant which " +"means that the cache state must not be effected at all by a long sequence " +"Get and Put operations on objects which are seen only once. This is " +"essential, without it not only would the cache be polluted, but it could " +"lose critical information about the objects that it cares about. It is " +"therefore essential that the Cache and History lists are not effected by " +"Get or Put operations on objects seen the first time. The Seen Hash " +"maintains a set of 16 bit hash tags, and requests which do not hit in the " +"object cache (are in the Cache List or History List) and do not match the " +"hash tag result in the hash tag begin updated but are otherwise ignored. " +"The Seen Hash is sized to approximately the number of objects in the cache " +"in order to match the number that are passed through it with the CLOCK rate " +"of the Cached and History Lists." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:63 +msgid "Cached List" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:65 +msgid "" +"The Cached list contains objects actually in memory. The basic operation " +"is LRU with new entries inserted into a FIFO (queue) and hits causing " +"objects to be reinserted. The interesting bit comes when an object is " +"being considered for insertion. First we check if the Object Hash to see " +"if the object is in the Cached List or History. Hits result in updating " +"the \"hit\" field and reinsertion. History hits result in the \"hit\" " +"field being updated and a comparison to see if this object should be kept " +"in memory. The comparison is against the least recently used members of " +"the Cache List, and is based on a weighted frequency::" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:69 +msgid "" +"A new object must beat enough bytes worth of currently cached objects to " +"cover itself. Each time an object is considered for replacement the CLOCK " +"moves forward. If the History object has a greater value then it is " +"inserted into the Cached List and the replaced objects are removed from " +"memory and their list entries are inserted into the History List. If the " +"History object has a lesser value it is reinserted into the History List. " +"Objects considered for replacement (at least one) but not replaced have " +"their \"hits\" field set to zero and are reinserted into the Cached List. " +"This is the CLOCK operation on the Cached List." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:72 +msgid "History List" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:74 +msgid "" +"Each CLOCK the least recently used entry in the History List is dequeued " +"and if the \"hits\" field is not greater than 1 (it was hit at least once " +"in the History or Cached List) it is deleted, otherwise the \"hits\" is set " +"to zero and it is requeued on the History List." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:77 +msgid "Compression/Decompression" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:79 +msgid "" +"Compression is performed by a background operation (currently called as " +"part of Put) which maintains a pointer into the Cached List and runs toward " +"the head compressing entries. Decompression occurs on demand during a " +"Get. In the case of objects tagged \"copy\" the compressed version is " +"reinserted in the LRU since we need to make a copy anyway. Those not " +"tagged \"copy\" are inserted uncompressed in the hope that they can be " +"reused in uncompressed form. This is a compile time option and may be " +"something we want to change." +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:81 +msgid "" +"There are 3 algorithms and levels of compression (speed on 1 thread i7 " +"920) :" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:83 +msgid "" +"fastlz: 173 MB/sec compression, 442 MB/sec decompression : basically free " +"since disk or network will limit first, ~53% final size" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:84 +msgid "" +"libz: 55 MB/sec compression, 234 MB/sec decompression : almost free, " +"particularly decompression, ~37% final size" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:85 +msgid "" +"liblzma: 3 MB/sec compression, 50 MB/sec decompression : expensive, ~27% " +"final size" +msgstr "" + +#: ../../arch/cache/ram-cache.en.rst:87 +msgid "" +"These are ballpark numbers, and your millage will vary enormously. JPEG " +"for example will not compress with any of these. The RamCache does detect " +"compression level and will declare something \"incompressible\" if it " +"doesn't get below 90% of the original size. This value is cached so that " +"the RamCache will not attempt to compress it again (at least as long as it " +"is in the history)." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/tier-storage.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/tier-storage.en.po new file mode 100644 index 00000000000..f17789b07d1 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/tier-storage.en.po @@ -0,0 +1,209 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/cache/tier-storage.en.rst:20 +msgid "Tiered Storage Design" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:26 +msgid "Introduction" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:28 +msgid "" +"Tiered storage is an attempt to allow |TS| to take advantage of physical " +"storage with different properties. This design concerns only mechanism. " +"Policies to take advantage of these are outside of the scope of this " +"document. Instead we will presume an *oracle* which implements this policy " +"and describe the queries that must be answered by the oracle and the " +"effects of the answers." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:33 +msgid "" +"Beyond avoiding question of tier policy the design is also intended to be " +"effectively identical to current operations for the case where there is " +"only one tier." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:36 +msgid "" +"The most common case for tiers is an ordered list of tiers, where higher " +"tiers are presumed faster but more expensive (or more limited in capacity). " +"This is not required. It might be that different tiers are differentiated " +"by other properties (such as expected persistence). The design here is " +"intended to handle both cases." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:46 +msgid "Configuration" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:48 +msgid "" +"Each storage unit in :file:`storage.config` can be marked with a *quality* " +"value which is 32 bit number. Storage units that are not marked are all " +"assigned the same value which is guaranteed to be distinct from all " +"explicit values. The quality value is arbitrary from the point of view of " +"this design, serving as a tag rather than a numeric value. The user (via " +"the oracle) can impose what ever additional meaning is useful on this value " +"(rating, bit slicing, etc.). In such cases all volumes should be explicitly " +"assigned a value, as the default / unmarked value is not guaranteed to have " +"any relationship to explicit values. The unmarked value is intended to be " +"useful in situations where the user has no interest in tiered storage and " +"so wants to let Traffic Server automatically handle all volumes as a single " +"tier." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:58 +msgid "Operations" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:60 +msgid "" +"After a client request is received and processed, volume assignment is " +"done. This would be changed to do volume assignment across all tiers " +"simultaneously. For each tier the oracle would return one of four values " +"along with a volume pointer." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:63 +msgid "`READ`" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:63 +msgid "The tier appears to have the object and can serve it." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:66 +msgid "`WRITE`" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:66 +msgid "" +"The object is not in this tier and should be written to this tier if " +"possible." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:69 +msgid "`RW`" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:69 +msgid "" +"Treat as `READ` if possible but if the object turns out to not in the cache " +"treat as `WRITE`." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:72 +msgid "`NO_SALE`" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:72 +msgid "Do not interact with this tier for this object." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:74 +msgid "" +"The volume returned for the tier must be a volume with the corresponding " +"tier quality value. In effect the current style of volume assignment is " +"done for each tier, by assigning one volume out of all of the volumes of " +"the same quality and returning one of `RW` or `WRITE` depending on whether " +"the initial volume directory lookup succeeds. Note that as with current " +"volume assignment it is presumed this can be done from in memory structures " +"(no disk I/O required)." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:79 +msgid "" +"If the oracle returns `READ` or `RW` for more than one tier, it must also " +"return an ordering for those tiers (it may return an ordering for all " +"tiers, ones that are not readable will be ignored). For each tier, in that " +"order, a read of cache storage is attempted for the object. A successful " +"read locks that tier as the provider of cached content. If no tier has a " +"successful read, or no tier is marked `READ` or `RW` then it is a cache " +"miss. Any tier marked `RW` that fails the read test is demoted to `WRITE`." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:85 +msgid "" +"If the object is cached every tier that returns `WRITE` receives the object " +"to store in the selected volume (this includes `RW` returns that are " +"demoted to `WRITE`). This is a cache to cache copy, not from the origin " +"server. In this case tiers marked `RW` that are not tested for read will " +"not receive any data and will not be further involved in the request " +"processing." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:90 +msgid "" +"For a cache miss, all tiers marked `WRITE` will receive data from the " +"origin server connection (if successful)." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:92 +msgid "" +"This means, among other things, that if there is a tier with the object all " +"other tiers that are written will get a local copy of the object, the " +"origin server will not be used. In terms of implementation, currently a " +"cache write to a volume is done via the construction of an instance of " +"`CacheVC` which recieves the object stream. For tiered storage the same " +"thing is done for each target volume." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:97 +msgid "" +"For cache volume overrides (e.g. via :file:`hosting.config`) this same " +"process is used except with only the volumes stripes contained within the " +"specified cache volume." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:102 +msgid "Copying" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:104 +msgid "" +"It may be necessary to provide a mechanism to copy objects between tiers " +"outside of a client originated transaction. In terms of implementation this " +"is straight forward using `HttpTunnel` as if in a transaction only using a " +"`CacheVC` instance for both the producer and consumer. The more difficult " +"question is what event would trigger a possible copy. A signal could be " +"provided whenever a volume directory entry is deleted although it should be " +"noted that the object in question may have already been evicted when this " +"event happens." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:112 +msgid "Additional Notes" +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:114 +msgid "" +"As an example use, it would be possible to have only one cache volume that " +"uses tiered storage for a particular set of domains using volume tagging. :" +"file:`hosting.config` would be used to direct those domains to the selected " +"cache volume. The oracle would check the URL in parallel and return " +"`NO_SALE` for the tiers in the target cache volume for other domains. For " +"the other tier (that of the unmarked storage units) the oracle would return " +"`RW` for the tier in all cases as that tier would not be queried for the " +"target domains." +msgstr "" + +#: ../../arch/cache/tier-storage.en.rst:40 +msgid "" +"The design presumes that if a user has multiple tiers of storage and an " +"ordering for those tiers, they will usually want content stored at one tier " +"level to also be stored at every other lower level as well, so that it does " +"not have to be copied if evicted from a higher tier." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/arch/hacking/index.en.po b/doc/locale/ja/LC_MESSAGES/arch/hacking/index.en.po new file mode 100644 index 00000000000..4196b20ae56 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/hacking/index.en.po @@ -0,0 +1,27 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-02-05 23:44+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/hacking/index.en.rst:2 +msgid "Hacking" +msgstr "" + +#: ../../arch/hacking/index.en.rst:22 +msgid "Introduction" +msgstr "" + +#: ../../arch/hacking/index.en.rst:24 +msgid "" +"This is a documentation stub on how to hack Apache Traffic Server. Here we " +"try to document things such as how to write and run unit or regression " +"tests or how to inspect the state of the core with a debugger." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/arch/index.en.po b/doc/locale/ja/LC_MESSAGES/arch/index.en.po new file mode 100644 index 00000000000..f5d0ca06430 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/index.en.po @@ -0,0 +1,47 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/index.en.rst:22 +msgid "Introduction" +msgstr "導入" + +#: ../../arch/index.en.rst:30 +msgid "Contents:" +msgstr "内容:" + +#: ../../arch/index.en.rst:2 +msgid "Architecture and Hacking" +msgstr "アーキテクチャとハッキング" + +#: ../../arch/index.en.rst:24 +#, fuzzy +msgid "" +"The original architectural documents for Traffic Server were lost in the " +"transition to an open source project. The documents in this section are " +"provisional and were written based on the existing code. The purpose is to " +"have a high level description of aspects of Traffic Server to better inform " +"ongoing work." +msgstr "" +"Traffic Server のオリジナルのアーキテクチャに関するドキュメントは、オープ" +"ンソースプロジェクトへの移行時に失われました。このセクションのドキュメン" +"トは暫定的なものであり、既存のコードを元に書かれています。このドキュメン" +"トの目的は進行中の作業をより知らせるため、 Traffic Server の側面の高度な" +"説明をすることです。" + +#: ../../arch/index.en.rst:28 +msgid "" +"In the final section on \"hacking\" we try to document our approaches to " +"understanding and modifying the source." +msgstr "" +"最終章の\"ハッキング\"ではソースを理解し変更するためのアプローチについて" +"記載します。" diff --git a/doc/locale/ja/LC_MESSAGES/arch/proposals/hostdb.en.po b/doc/locale/ja/LC_MESSAGES/arch/proposals/hostdb.en.po new file mode 100644 index 00000000000..c9639b09213 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/proposals/hostdb.en.po @@ -0,0 +1,357 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../arch/proposals/hostdb.en.rst:2 +msgid "Host Resolution" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:22 +msgid "Introduction" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:24 +msgid "" +"The current mechanism for resolving host names to IP addresses for Traffic " +"Server is contained the HostDB and DNS libraries. These take hostnames and " +"provide IP addresses for them." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:27 +msgid "" +"The current implementation is generally considered inadequate, both from a " +"functionality point of view and difficulty in working with it in other " +"parts of Traffic Server. As Traffic Server is used in more complex " +"situtations this inadequacy presents increasing problems." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:32 +msgid "Goals" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:34 +msgid "" +"Updating the host name resolution (currently referred to as \"HostDB\") has " +"several functions goals" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:36 +msgid "Enable additional processing layers to be easily added." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:37 +msgid "Enable plugins to directly access the name resolution logic" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:38 +msgid "Enable plugins to provide name resolution" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:39 +msgid "Asynchronous (immediate resolve or callback on block)" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:40 +msgid "" +"Minimize allocations -- in particular no allocations for cached resolutions" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:41 +msgid "" +"Simplify interactions with the resolution, particularly with regard to " +"nameservers, origin server failover, and address family handling." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:44 +msgid "" +"It is also necessary to support a number of specific features that are " +"either currently available or strongly desired." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:46 +msgid "SplitDNS or its equivalent" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:47 +msgid "Use of a hosts file (e.g. ``/etc/hosts``)" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:48 +msgid "Simultaneous IPv4 and IPv6 queries" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:49 +msgid "IP family control" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:50 +msgid "" +"Negative caching * Server connection failures * Query failures * " +"Nameserver failures." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:54 +msgid "Address validity time out control" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:55 +msgid "Address round robin support" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:56 +msgid "SRV record support (weighted records)" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:57 +msgid "Nameserver round robin" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:58 +msgid "Plugin access to nameserver data (add, remove, enumerate)" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:59 +msgid "Plugin provision of resolvers." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:60 +msgid "Hooks for plugin detection / recovery from resolution events." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:62 +msgid "" +"One issue is persistence of the cached resolutions. This creates problems " +"for the current implementation (because of size limits it imposes on the " +"cached data) but also allows for quicker restarts in a busy environment." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:66 +msgid "Basics" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:68 +msgid "" +"The basic design is to separate the functionality into chainable layers so " +"that a resolver with the desired attributes can be assembled from those " +"layers. The core interface is that of a lazy iterator. This object returns " +"one of four results when asked for an address" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:72 +msgid "An IP address" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:73 +msgid "Done(no more addresses are available)" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:74 +msgid "Wait(an address may be available in the future)" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:75 +msgid "Fail (no address is available and none will be so in the future)" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:77 +msgid "" +"Each layer (except the bottom) uses this API and also provides it. This " +"enables higher level logic such as the state machine to simply use the " +"resolver as a list without having to backtrack states in the case of " +"failures, or have special cases for different resolution sources." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:81 +msgid "" +"To perform a resolution, a client creates a query object (potentially on " +"the stack), initializes it with the required data (at least the hostname) " +"and then starts the resolution. Methods on the query object allow its state " +"and IP address data to be accessed." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:86 +msgid "Required Resolvers" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:90 +msgid "Nameserver" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:89 +msgid "" +"A bottom level resolver that directly queries a nameserver for DNS data. " +"This contains much of the functionality currently in the ``iocore/dns`` " +"directory." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:94 +msgid "SplitDNS" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:93 +msgid "" +"A resolver that directs requests to one of several resolvers. To emulate " +"current behavior these would be Nameserver instances." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:98 +msgid "NameserverGroup" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:97 +msgid "" +"A grouping mechanism for Nameserver instances that provides failover, round " +"robin, and ordering capabilities. It may be reasonable to merge this with " +"the SplitDNS resolver." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:101 +msgid "HostFile" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:101 +msgid "A resolver that uses a local file to resolve names." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:105 +msgid "AddressCache" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:104 +msgid "" +"A resolver that also has a cache for resolution results. It requires " +"another resolver instance to perform the actual resolution." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:109 +msgid "Preloaded" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:108 +msgid "" +"A resolver that can contain one or more explicitly set IP addresses which " +"are returned. When those are exhausted it falls back to another resolver." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:112 +msgid "Configuration" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:114 +msgid "" +"To configuration the resolution, each resolver would be assigned a tag. It " +"is not, however, sufficient to simply provide the list of resolver tags " +"because some resolvers require additional configuration. Unfortunately this " +"will likely require a separate configuration file outside of :file:`records." +"config`, although we would be able to remove :file:`splitdns.config`. In " +"this case we would need chain start / end markers around a list of resolver " +"tags. Each tag would the be able to take additional resolver configuration " +"data. For instance, for a SplitDNS resolver the nameservers." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:121 +msgid "Examples" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:123 +msgid "" +"Transparent operations would benefit from the *Preloaded* resolver. This " +"would be loaded with the origin host address provided by the client " +"connection. This could be done early in processing and then no more logic " +"would be required to skip DNS processing as it would happen without " +"additional action by the state machine. It would handle the problem of de " +"facto denial of service if an origin server becomes unavailable in that " +"configuration, as *Preloaded* would switch to alternate addresses " +"automatically." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:129 +msgid "" +"Adding host file access would be easier as well, as it could be done in a " +"much more modular fashion and then added to the stack at configuration " +"time. Whether such addresses were cached would be controlled by chain " +"arrangement rather yet more configuration knobs." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:133 +msgid "" +"The default configuration would be *Preloaded* : *AddressCache* : " +"*Nameserver*." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:135 +msgid "" +"In all cases the state machine makes requests against the request object to " +"get IP addresses as needed." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:138 +msgid "Issues" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:141 +msgid "Request object allocation" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:143 +msgid "" +"The biggest hurdle is being able to unwind a resolver chain when a block is " +"encountered. There are some ways to deal with this." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:145 +msgid "" +"1) Set a maximum resolver chain length and declare the request instance so " +"that there is storage for state for that many resolvers. If needed and " +"additional value of maximum storage per chain could be set as well. The " +"expected number of elements in a chain is expected to be limited, 10 would " +"likely be a reaosnable limit. If settable at source configuration time this " +"should be sufficient." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:150 +msgid "" +"2) Embed class allocators in resolver chains and mark the top / outermost / " +"first resolver. The maximum state size for a resolution can be calculated " +"when the chain is created and then the top level resolver can use an " +"allocation pool to efficiently allocate request objects. This has an " +"advantage that with a wrapper class the request object can be passed along " +"cheaply. Whether that's an advantage in practice is unclear." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:156 +msgid "Plugin resolvers" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:158 +msgid "" +"If plugins can provide resolvers, how can these can integrated in to " +"existing resolver chains for use by the HTTP SM for instance?" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:162 +msgid "Feedback" +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:164 +msgid "" +"It should be possible for a client to provide feedback about addresses (e." +"g., the origin server at this address is not available). Not all resolvers " +"will handle feedback but some will and that must be possible." +msgstr "" + +#: ../../arch/proposals/hostdb.en.rst:167 +msgid "" +"Related to this is that caching resolvers (such as *AddressCache*) must be " +"able to iterator over all resolved addresses even if their client does not " +"ask for them. In effect they must background fill the address data." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/glossary.en.po b/doc/locale/ja/LC_MESSAGES/glossary.en.po new file mode 100644 index 00000000000..a45991f8fd1 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/glossary.en.po @@ -0,0 +1,269 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../glossary.en.rst:20 +msgid "Glossary" +msgstr "用語集" + +#: ../../glossary.en.rst:49 +msgid "cache span" +msgstr "キャッシュスパン" + +#: ../../glossary.en.rst:51 +msgid "" +"The physical storage described by a single line in :file:`storage.config`." +msgstr ":file:`storage.config` の各行に記述された物理ストレージです。" + +#: ../../glossary.en.rst:44 +msgid "cache stripe" +msgstr "キャッシュストライプ" + +#: ../../glossary.en.rst:39 +msgid "cache volume" +msgstr "キャッシュボリューム" + +#: ../../glossary.en.rst:41 +msgid "" +"A user defined unit of persistent storage for the cache. Cache volumes are " +"defined in :file:`volume.config`. A cache volume is by default spread " +"across :term:`cache span`\\ s to increase robustness. Each section of a " +"cache volume on a specific cache span is a :term:`cache stripe`." +msgstr "" +"ユーザがキャッシュとして定義した永続ストレージの単位です。キャッシュボリュー" +"ムは :file:`volume.config` で定義されます。キャッシュボリュームは頑強性を高" +"めるため :term:`キャッシュスパン`\\ を跨いで分散されます。特定のキャッシュス" +"パンにおけるキャッシュボリュームの各セクションは :term:`キャッシュストライプ" +"` です。" + +#: ../../glossary.en.rst:24 +msgid "continuation" +msgstr "継続" + +#: ../../glossary.en.rst:26 +msgid "" +"A callable object that contains state. These are are mechanism used by " +"Traffic Server to implement callbacks and continued computations. Continued " +"computations are critical to efficient processing of traffic because by " +"avoiding any blocking operations that wait on external events. In any such " +"case a continuation is used so that other processing can continue until the " +"external event occurs. At that point the continuation is invoked to " +"continue the suspended processing. This can be considered similar to co-" +"routines." +msgstr "" +"状態を持った呼び出し可能なオブジェクトです。 コールバックと継続的な計算を実" +"装するために Traffic Server で用いられるメカニズムです。外部イベントを待つ操" +"作のブロッキングを避けることによりトラフィックを効率良く処理するため、継続的" +"な計算は重要です。そのような場合において、他の処理が外部イベントが起こるまで" +"続けられるようにするため継続が使用されます。その時点で継続は中断した処理を続" +"けるために発動されます。これはコルーチンに似た考えができます。" + +#: ../../glossary.en.rst:77 +msgid "revalidation" +msgstr "再確認" + +#: ../../glossary.en.rst:79 +msgid "" +"Verifying that a currently cached object is still valid. This is usually " +"done using an `If-Modified-Since `_ request which allows the origin server to " +"validate the content without resending the content." +msgstr "" +"現在のキャッシュされたオブジェクトがまだ有効か確認することです。これは通常オ" +"リジンサーバがコンテンツの再送信をすることなくコンテンツの確認を行うことを可" +"能にする `If-Modified-Since `_ リクエストを使って行われます。" + +#: ../../glossary.en.rst:31 +msgid "session" +msgstr "セッション" + +#: ../../glossary.en.rst:33 +msgid "" +"A single connection from a client to Traffic Server, covering all requests " +"and responses on that connection. A session starts when the client " +"connection opens, and ends when the connection closes." +msgstr "" +"全てのリクエストとレスポンスをカバーする、クライアントから Traffic Server へ" +"の単一のコネクションです。セッションはクライアントがコネクションをオープンし" +"た際に開始し、コネクションをクローズする際に終了します。" + +#: ../../glossary.en.rst:74 +msgid "storage unit" +msgstr "ストレージユニット" + +#: ../../glossary.en.rst:76 +msgid "Obsolete term for :term:`cache span`." +msgstr ":term:`キャッシュスパン` の旧称です。" + +#: ../../glossary.en.rst:35 +msgid "transaction" +msgstr "トランザクション" + +#: ../../glossary.en.rst:37 +msgid "" +"A client request and response, either from the origin server or from the " +"cache. A transaction begins when Traffic Server receives a request, and " +"ends when Traffic Server sends the response." +msgstr "" +"クライアントのリクエストと、オリジンサーバーもしくはキャッシュからレスポンス" +"です。トランザクションは Traffic Server がリクエストを受け付けた際に開始" +"し、 Traffic Server がレスポンスを送る際に終了します。" + +#: ../../glossary.en.rst:82 +msgid "write cursor" +msgstr "書込みカーソル" + +#: ../../glossary.en.rst:84 +msgid "The location in a :term:`cache stripe` where new data is written." +msgstr "新しいデータが書き込まれる :term:`キャッシュストライプ` の位置です。" + +#: ../../glossary.en.rst:68 +msgid "alternate" +msgstr "代替" + +#: ../../glossary.en.rst:70 +msgid "" +"A variant of a :term:`cache object`. This was originally created to handle " +"the `VARY mechanism `_ but has since been used for additional purposes. All " +"alternates of an object must be equivalent in some manner, that is they are " +"alternate forms of the same stream. The most common example is having " +"normal and compressed versions of the stream." +msgstr "" +":term:`キャッシュオブジェクト` の変形です。元々は `VARY メカニズム `_ を処理するために" +"作られましたが、以来他の目的のためにも使われています。オブジェクトの全ての代" +"替は何らかの方法で同質にならなければならず、同じストリームの形式に変化しま" +"す。最も一般的な例はストリームの通常版と圧縮版を持つことです。" + +#: ../../glossary.en.rst:97 +msgid "cache fragment" +msgstr "キャッシュフラグメント" + +#: ../../glossary.en.rst:99 +msgid "" +"The unit of storage in the cache. All reads from the cache always read " +"exactly one fragment. Fragments may be written in groups, but every write " +"is always an integral number of fragments. Each fragment has a " +"corresponding :term:`directory entry` which describes its location in the " +"cache storage." +msgstr "" +"キャッシュ内のストレージの単位です。キャッシュの全ての読込みは常にちょうど一" +"つのフラグメントを読み込みます。フラグメントはまとめて書き込まれるかも知れま" +"せんが、全ての書込みは常にフラグメントの整数になります。各フラグメントは " +"キャッシュストレージにおける自身の位置情報を持つ :term:`ディレクトリエントリ" +"` に対応しています。" + +#: ../../glossary.en.rst:56 +msgid "cache ID" +msgstr "キャッシュ ID" + +#: ../../glossary.en.rst:58 +msgid "" +"A 128 bit value used as a fixed sized identifier for an object in the " +"cache. This is computed from the :term:`cache key` using the `MD5 hashing " +"function `_." +msgstr "" +"キャッシュのオブジェクトの固定サイズの識別子として使用される 128 ビットの値" +"です。 `MD5 ハッシュ関数 `_ を" +"用いて :term:`キャッシュキー` から計算されます。" + +#: ../../glossary.en.rst:52 +msgid "cache key" +msgstr "キャッシュキー" + +#: ../../glossary.en.rst:54 +msgid "" +"A byte sequence that is a globally unique identifier for an :term:`object " +"` in the cache. By default the URL for the object is used." +msgstr "" +"キャッシュの :term:`オブジェクト <キャッシュオブジェクト>` の大域的にユニー" +"クな識別子のバイト列です。デフォルトではオブジェクトの URL が使用されます。" + +#: ../../glossary.en.rst:64 +msgid "cache object" +msgstr "キャッシュオブジェクト" + +#: ../../glossary.en.rst:66 +msgid "" +"The minimal self contained unit of data in the cache. Cache objects are the " +"stored version of equivalent content streams from an origin server. A " +"single object can have multiple variants called :term:`alternates " +"`." +msgstr "" +"キャッシュのデータの最小の自己完結した単位です。キャッシュオブジェクトはオリ" +"ジンサーバーからのコンテンツストリームと等価な保存されたバージョンです。単一" +"のオブジェクトは :term:`代替 <代替>` と呼ばれる複数の変形を持ち得ます。" + +#: ../../glossary.en.rst:46 +msgid "" +"A homogenous persistent store for the cache in a single :term:`cache span`. " +"A stripe always resides entirely on a single physical device and is treated " +"as an undifferentiated span of bytes. This is the smallest independent unit " +"of storage." +msgstr "" +"単一の :term:`キャッシュスパン` におけるキャッシュの同質な永続ストアです。ス" +"トライプは常に一つの物理デバイスに全体的に置かれ、区別されないバイト列のスパ" +"ンとして扱われます。これはストレージの最小の独立した単位です。" + +#: ../../glossary.en.rst:60 +msgid "cache tag" +msgstr "キャッシュタグ" + +#: ../../glossary.en.rst:62 +msgid "" +"The bottom few bits (12 currently) of the :term:`cache ID`. This is used in " +"the :ref:`cache directory ` for a preliminary identity " +"check before going to disk." +msgstr "" +":term:`キャッシュ ID` の下位数ビット（現在は 12）です。ディスクへアクセスす" +"る前に予備的な識別チェックを行うために :ref:`キャッシュディレクトリ ` で使用されます。" + +#: ../../glossary.en.rst:90 +msgid "directory bucket" +msgstr "ディレクトリバケット" + +#: ../../glossary.en.rst:92 +msgid "" +"A contiguous fixed sized group of :term:`directory entries `. This is used for hash bucket maintenance optimization." +msgstr "" +"隣接した :term:`ディレクトリエントリ <ディレクトリエントリ>` の固定サイズの" +"グループです。ハッシュバケットのメンテナンスの最適化に使用されます。" + +#: ../../glossary.en.rst:94 +msgid "directory entry" +msgstr "ディレクトリエントリ" + +#: ../../glossary.en.rst:96 +msgid "An in memory entry that describes a :term:`cache fragment`." +msgstr ":term:`キャッシュフラグメント` を指すメモリに置かれるエントリです。" + +#: ../../glossary.en.rst:85 +msgid "directory segment" +msgstr "ディレクトリセグメント" + +#: ../../glossary.en.rst:87 +msgid "" +"A contiguous group of :term:`buckets `. Each :term:`cache " +"stripe` has a set of segments all of which have the same number of buckets, " +"although the number of buckets per segment can vary between cache stripes. " +"Segments are administrative in purpose to minimize the size of free list " +"and hash bucket pointers." +msgstr "" +"隣接した :term:`バケット <ディレクトリバケット>` のグループです。セグメント" +"あたりのバケット数はキャッシュストライプの間で変化する可能性がありますが、" +"各 :term:`キャッシュストライプ` は同じ数のバケットを持つ全てのセグメントの" +"セットを持ちます。セグメントはフリーリストとハッシュバケットポインタのサイズ" +"を最小限にするため管理できます。" diff --git a/doc/locale/ja/LC_MESSAGES/index.po b/doc/locale/ja/LC_MESSAGES/index.po new file mode 100644 index 00000000000..c159279a8a9 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/index.po @@ -0,0 +1,58 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../index.rst:2 +msgid "Apache Traffic Server" +msgstr "" + +#: ../../index.rst:22 +msgid "" +"Apache Traffic Server™ speeds Internet access, enhances website " +"performance, and delivers unprecedented web hosting capabilities." +msgstr "" +"Apache Traffic Server™ はインターネットアクセスを加速させ、ウェブサイトのパ" +"フォーマンスを高め、かつて無いウェブホスティング性能を提供します。" + +#: ../../index.rst:26 +msgid "What Is Apache Traffic Server?" +msgstr "Apache Traffic Server とは？" + +#: ../../index.rst:28 +msgid "" +"Traffic Server is a high-performance web proxy cache that improves network " +"efficiency and performance by caching frequently-accessed information at " +"the edge of the network. This brings content physically closer to end " +"users, while enabling faster delivery and reduced bandwidth use. Traffic " +"Server is designed to improve content delivery for enterprises, Internet " +"service providers (ISPs), backbone providers, and large intranets by " +"maximizing existing and available bandwidth." +msgstr "" +"Traffic Server はハイパフォーマンスなウェブプロキシーキャッシュであり、それ" +"はネットワークの端で頻繁にアクセスされる情報をキャッシュすることによりネット" +"ワーク効率とパフォーマンスを改善します。これは物理的に近いエンドユーザーにコ" +"ンテンツを運ぶ一方で、素早い提供と帯域使用量の削減を可能にします。Traffic " +"Server は商用のコンテンツ配信やインターネットサービスプロバイダー( ISP )や" +"バックボーンプロバイダーや巨大なイントラネットを現行の利用可能な帯域を最大化" +"することで改善するようにデザインされています。" + +#: ../../index.rst:50 +msgid "Indices and tables" +msgstr "Indices and tables" + +#: ../../index.rst:52 +msgid ":ref:`genindex`" +msgstr ":ref:`genindex`" + +#: ../../index.rst:53 +msgid ":ref:`search`" +msgstr ":ref:`search`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSAPI.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSAPI.en.po new file mode 100644 index 00000000000..9170a0ff3ae --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSAPI.en.po @@ -0,0 +1,305 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSAPI.en.rst:21 +msgid "TSAPI" +msgstr "TSAPI" + +#: ../../reference/api/TSAPI.en.rst:24 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSAPI.en.rst:25 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSAPI.en.rst:26 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSAPI.en.rst:29 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSAPI.en.rst:30 +msgid "" +"The Apache Traffic Server API enables you to create plugins, using the C " +"programming language, that customize the behavior of your Traffic Server " +"installation." +msgstr "" +"Apache Traffic Server API は C 言語を使ってインストール済みの Traffic " +"Server の振る舞いをカスタマイズするプラグインの作成を可能にします。" + +#: ../../reference/api/TSAPI.en.rst:34 +msgid "" +"Traffic Server enables sophisticated caching and processing of web-related " +"traffic, such as DNS and HTTP requests and responses. Traffic Server itself " +"consists of an event-driven loop that can be simplified as follows::" +msgstr "" +"Traffic Server は洗練されたキャッシュと DNS や HTTP のリクエストやレスポンス" +"のような Web 関連トラフィックの処理を可能とします。Traffic Server 自体は次の" +"ように簡素化されたイベントドリブンループから成っています。" + +#: ../../reference/api/TSAPI.en.rst:44 +msgid "" +"You compile your plugin source code to create a shared library that Traffic " +"Server loads when it is started. Your plugin contains callback functions " +"that are registered for specific Traffic Server events. When Traffic Server " +"needs to process an event, it invokes any and all call-back functions " +"you've registered for that event type." +msgstr "" +"Traffic Server が動作を開始するときに読み込まれる共有ライブラリを作るために" +"プラグインのソースをコンパイルします。プラグインは特定の Traffic Server イベ" +"ントに登録されるコールバック関数を含んでいます。Traffic Server がイベントの" +"処理を必要とすると、そのイベントタイプに登録したあらゆるコールバック関数が呼" +"び出されます。" + +#: ../../reference/api/TSAPI.en.rst:51 +msgid "Possible uses for plugins include the following:" +msgstr "プラグインは次の使い方ができます。" + +#: ../../reference/api/TSAPI.en.rst:53 +msgid "" +"HTTP processing plugins can filter, blacklist, authorize users or transform " +"content." +msgstr "" +"HTTP 処理プラグインはフィルター、ブラックリスト、ユーザー認証、コンテンツの" +"変換ができます。" + +#: ../../reference/api/TSAPI.en.rst:54 +msgid "" +"Protocol plugins can enable Traffic Server to proxy-cache new protocol " +"content." +msgstr "" +"プロトコルプラグインは Traffic Server が新しいプロトコルコンテンツをプロキ" +"シーキャッシュできるようにします。" + +#: ../../reference/api/TSAPI.en.rst:55 +msgid "" +"A blacklisting plugin denies attempts to access web sites that are off-" +"limits." +msgstr "" +"ブラックリストプラグインは進入禁止の Web サイトへのアクセスを拒絶します。" + +#: ../../reference/api/TSAPI.en.rst:56 +msgid "Append transform plugins add data to HTTP response content." +msgstr "追加変換プラグインは HTTP レスポンスコンテンツにデータを追加します。" + +#: ../../reference/api/TSAPI.en.rst:57 +msgid "An image conversion plugin transforms JPEG images to GIF images." +msgstr "画像変換プラグインは JPEG 画像を GIF 画像に変換します。" + +#: ../../reference/api/TSAPI.en.rst:58 +msgid "" +"Compression plugins send response content to a compression server that " +"compresses the data (alternatively, a compression library local to the " +"Traffic Server host machine could do the compression)." +msgstr "" +"圧縮プラグインはデータを圧縮する圧縮サーバーにレスポンスデータを送信します " +"(もしくは、Traffic Server のホストマシンにある圧縮ライブラリが圧縮を行うかも" +"しれません) 。" + +#: ../../reference/api/TSAPI.en.rst:61 +msgid "" +"Authorization plugins check a user's permissions to access particular web " +"sites. The plugin could consult a local authorization program or send " +"queries to an authorization server." +msgstr "" +"認証プラグインは特定の Web サイトにアクセスするためのユーザーの権限を確認し" +"ます。このプラグインはローカルの認証プログラムに問い合わせたり、認証サーバー" +"に問い合わせを送信したりするかもしれません。" + +#: ../../reference/api/TSAPI.en.rst:64 +msgid "" +"A plugin that gathers client information from request headers and enters " +"this information in a database." +msgstr "" +"リクエストヘッダーからクライアントの情報を収集しその情報をデータベースに入力" +"するプラグイン。" + +#: ../../reference/api/TSAPI.en.rst:66 +msgid "" +"A protocol plugin listen for specific protocol requests on a designated " +"port and then uses Traffic Server's proxy server and cache to serve client " +"requests." +msgstr "" +"プロトコルプラグインは指定されたポートへの特定のプロトコルのリクエストを受" +"け、クライアントのリクエストに応えるために Traffic Server のプロキシーサー" +"バーとキャッシュを使用します。" + +#: ../../reference/api/TSAPI.en.rst:71 +msgid "Naming conventions" +msgstr "命名規則" + +#: ../../reference/api/TSAPI.en.rst:73 +msgid "The Traffic Server API adheres to the following naming conventions:" +msgstr "Traffic Server API は次の命名規則に従います。" + +#: ../../reference/api/TSAPI.en.rst:75 +msgid "" +"The TS prefix is used for all function and variable names defined in the " +"Traffic Server API. For example, :data:`TS_EVENT_NONE`, :type:`TSMutex`, " +"and :func:`TSContCreate`." +msgstr "" +"TS プレフィックスは Traffic Server API のすべての関数と変数の名前に使用され" +"ます。例えば、:data:`TS_EVENT_NONE` 、:type:`TSMutex` 、:func:" +"`TSContCreate` となります。" + +#: ../../reference/api/TSAPI.en.rst:78 +msgid "" +"Enumerated values are always written in all uppercase letters. For " +"example, :data:`TS_EVENT_NONE` and :data:`TS_VC_CLOSE_ABORT`." +msgstr "" +"列挙された値は常にすべて大文字で書かれます。例えば、:data:`TS_EVENT_NONE` " +"や :data:`TS_VC_CLOSE_ABORT` となります。" + +#: ../../reference/api/TSAPI.en.rst:80 +msgid "" +"Constant values are all uppercase; enumerated values can be seen as a " +"subset of constants. For example, :data:`TS_URL_SCHEME_FILE` and :data:" +"`TS_MIME_FIELD_ACCEPT`." +msgstr "" +"定数はすべて大文字です。列挙された値は定数の一部に見えるかもしれません。例え" +"ば、:data:`TS_URL_SCHEME_FILE` や :data:`TS_MIME_FIELD_ACCEPT` となります。" + +#: ../../reference/api/TSAPI.en.rst:83 +msgid "" +"The names of defined types are mixed-case. For example, :type:`TSHttpSsn` " +"and :func:`TSHttpTxn`. :func:`TSDebug`" +msgstr "" +"定義された型の名前は大文字小文字が混在します。例えば、:type:`TSHttpSsn` 、:" +"func:`TSHttpTxn` 、:func:`TSDebug` となります。" + +#: ../../reference/api/TSAPI.en.rst:85 +msgid "" +"Function names are mixed-case. For example, :func:`TSUrlCreate` and :func:" +"`TSContDestroy`." +msgstr "" +"関数名は混在になります。例えば、:func:`TSUrlCreate` や :func:" +"`TSContDestroy` となります。" + +#: ../../reference/api/TSAPI.en.rst:87 +msgid "" +"Function names use the following subject-verb naming style: TS--" +", where goes from general to specific. This makes it easier " +"to determine what a function does by reading its name. For example, the " +"function to retrieve the password field (the specific subject) from a URL " +"(the general subject) is :func:`TSUrlPasswordGet`." +msgstr "" +"関数名は次の 主語-動詞 命名スタイルを使用します。TS-<主語>-<動詞> 、<主語> " +"の部分は一般的なものから限定的なものにしていきます。これはその名前を読むこと" +"で関数が何をするのかを分かりやすくします。例えば、URL (一般的な主語) からパ" +"スワードフィールド (限定的な主語) を取得する関数は :func:`TSUrlPasswordGet` " +"となります。" + +#: ../../reference/api/TSAPI.en.rst:93 +msgid "" +"Common verbs like Create, Destroy, Get, Set, Copy, Find, Retrieve, Insert, " +"Remove, and Delete are used only when appropriate." +msgstr "" +"Create 、Destroy 、Get 、Set 、Copy 、Find 、Retrieve 、Insert 、Remove 、" +"Delete のような一般的な動詞はそれが適切な場合にのみ使用されます。" + +#: ../../reference/api/TSAPI.en.rst:97 +msgid "Plugin loading and configuration" +msgstr "プラグインの読み込みと設定" + +#: ../../reference/api/TSAPI.en.rst:99 +msgid "" +"When Traffic Server is first started, it consults the plugin.config file to " +"determine the names of all shared plugin libraries that need to be loaded. " +"The plugin.config file also defines arguments that are to be passed to each " +"plugin's initialization function, :func:`TSPluginInit`. The :file:`records." +"config` file defines the path to each plugin shared library." +msgstr "" +"Traffic Server が最初にスタートするとき、読み込まれる必要のあるすべての共有" +"ライブラリの名前を決定するために plugin.config ファイルを参照します。 " +"plugin.config ファイルは個々のプラグインの初期化関数 :func:`TSPluginInit` に" +"渡される引数も定義します。:file:`records.config` ファイルは個々のプラグイン" +"共有ライブラリのパスを定義します。" + +#: ../../reference/api/TSAPI.en.rst:106 +msgid "" +"The sample :file:`plugin.config` file below contains a comment line, a " +"blank line, and two plugin configurations::" +msgstr "" +"以下の :file:`plugin.config` ファイルのサンプルはコメント行、空行、二つのプ" +"ラグインの設定から成っています。" + +#: ../../reference/api/TSAPI.en.rst:113 +msgid "" +"Each plugin configuration in the :file:`plugin.config` file resembles a " +"UNIX or DOS shell command; each line in :file:`plugin.config` cannot exceed " +"1023 characters." +msgstr "" +":file:`plugin.config` ファイル内の個々のプラグインの設定は UNIX または DOS " +"のシェルコマンドに似ています。:file:`plugin.config` 内の各行は 1023 文字を超" +"えることはできません。" + +#: ../../reference/api/TSAPI.en.rst:117 +msgid "" +"The first plugin configuration is for a plugin named my-plugin.so. It " +"contains three arguments that are to be passed to that plugin's " +"initialization routine. The second configuration is for a plugin named some-" +"plugin.so; it contains three arguments. The last argument, $proxy.config." +"http.cache.on, is actually a configuration variable. Traffic Server will " +"look up the specified configuration variable and substitute its value." +msgstr "" +"最初のプラグインの設定は my-plugin.so と名付けられたプラグインのためのもので" +"す。これはそのプラグインの初期化ルーチンに渡される三つの引数を含んでいます。" +"二番目の設定は some-plugin.so と名付けられたプラグインのためのものです。これ" +"は三つの引数を含んでいます。その最後の引数である $proxy.config.http.cache." +"on は実は設定変数です。Traffic Server は指定された設定変数を参照し、その値で" +"置き換えます。" + +#: ../../reference/api/TSAPI.en.rst:125 +msgid "" +"Plugins are loaded and initialized by Traffic Server in the order they " +"appear in the :file:`plugin.config` file." +msgstr "" +"プラグインは :file:`plugin.config` ファイルに出てくる順番で Traffic Server " +"に読み込まれ初期化されます。" + +#: ../../reference/api/TSAPI.en.rst:129 +msgid "Plugin initialization" +msgstr "プラグインの初期化" + +#: ../../reference/api/TSAPI.en.rst:131 +msgid "" +"Each plugin must define an initialization function named :func:" +"`TSPluginInit` that Traffic Server invokes when the plugin is loaded. :func:" +"`TSPluginInit` is commonly used to read configuration information and " +"register hooks for event notification." +msgstr "" +"各プラグインはプラグインが読み込まれたときに Traffic Server が呼び出す :" +"func:`TSPluginInit` という初期化関数を定義していなければなりません。:func:" +"`TSPluginInit` は一般的に設定情報を読み込みイベント通知のフックを登録するた" +"めに使用されます。" + +#: ../../reference/api/TSAPI.en.rst:138 +msgid "Files" +msgstr "ファイル" + +#: ../../reference/api/TSAPI.en.rst:139 +msgid "" +":file:`{CONFIG_DIR}/plugin.config`, :file:`{CONFIG_DIR}/records.config`" +msgstr "" +":file:`{CONFIG_DIR}/plugin.config`, :file:`{CONFIG_DIR}/records.config`" + +#: ../../reference/api/TSAPI.en.rst:142 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSAPI.en.rst:143 +msgid ":manpage:`TSPluginInit(3ts)`" +msgstr ":manpage:`TSPluginInit(3ts)`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSDebug.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSDebug.en.po new file mode 100644 index 00000000000..5d7c5e45d60 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSDebug.en.po @@ -0,0 +1,102 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSDebug.en.rst:21 +msgid "TSDebug" +msgstr "TSDebug" + +#: ../../reference/api/TSDebug.en.rst:24 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSDebug.en.rst:25 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSDebug.en.rst:39 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSDebug.en.rst:41 +msgid "" +":func:`TSError` is similar to :func:`printf` except that instead of writing " +"the output to the C standard output, it writes output to the Traffic Server " +"error log." +msgstr "" +":func:`TSError` は C 標準出力に書き込む代わりに Traffic Server のエラーログ" +"に書き込むことを除けば :func:`printf` に似ています。" + +#: ../../reference/api/TSDebug.en.rst:45 +msgid "" +":func:`TSDebug` is the same as :func:`TSError` except that it only logs the " +"debug message if the given debug tag is enabled. It writes output to the " +"Traffic Server debug log." +msgstr "" +":func:`TSDebug` は与えられたデバッグタグが有効化されている場合にのみログメッ" +"セージを出力する点を除いて :func:`TSError` と同じです。" + +#: ../../reference/api/TSDebug.en.rst:49 +msgid "" +":func:`TSIsDebugTagSet` returns non-zero if the given debug tag is enabled." +msgstr "" +":func:`TSIsDebugTagSet` は与えられたデバッグタグが有効化されている場合に非ゼ" +"ロを返します。" + +#: ../../reference/api/TSDebug.en.rst:52 +msgid "" +"In debug mode, :macro:`TSAssert` Traffic Server to prints the file name, " +"line number and expression, and then aborts. In release mode, the " +"expression is not removed but the effects of printing an error message and " +"aborting are. :macro:`TSReleaseAssert` prints an error message and aborts " +"in both release and debug mode." +msgstr "" +"デバッグモードでは、:macro:`TSAssert` は Traffic Server にファイル名、行番" +"号、式を出力させ、処理を中断します。リリースモードでは、式の出力は残ります" +"が、エラーメッセージの出力と処理の中断は行われません。:macro:" +"`TSReleaseAssert` はリリースモードとデバッグモードのどちらでもエラーメッセー" +"ジの出力と処理の中断を行います。" + +#: ../../reference/api/TSDebug.en.rst:65 +msgid "Examples" +msgstr "例" + +#: ../../reference/api/TSDebug.en.rst:67 +msgid "" +"This example uses :func:`TSDebugSpecific` to log a message when a specific " +"debugging flag is enabled::" +msgstr "" +"この例は特定のデバッグフラグが有効になっている場合にメッセージをログに出力す" +"るために :func:`TSDebugSpecific` を使用しています。" + +#: ../../reference/api/TSDebug.en.rst:78 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSDebug.en.rst:79 +msgid ":manpage:`TSAPI(3ts)`, :manpage:`printf(3)`" +msgstr ":manpage:`TSAPI(3ts)`, :manpage:`printf(3)`" + +#: ../../reference/api/TSDebug.en.rst:58 +msgid "" +":func:`TSDebugSpecific` emits a debug line even if the debug tag is turned " +"off, as long as debug flag is enabled. This can be used in conjunction " +"with :func:`TSHttpTxnDebugSet`, :func:`TSHttpSsnDebugSet`, :func:" +"`TSHttpTxnDebugGet` and :func:`TSHttpSsnDebugGet` to enable debugging on " +"specific session and transaction objects." +msgstr "" +":func:`TSDebugSpecific` はデバッグタグがオフにされていてもデバッグフラグ" +"が有効化されてさえいればデバッグ行を出力します。これは特定のセッションと" +"トランザクションオブジェクトでデバッグを有効化するために :func:" +"`TSHttpTxnDebugSet` 、:func:`TSHttpSsnDebugSet` 、:func:" +"`TSHttpTxnDebugGet` 、:func:`TSHttpSsnDebugGet` と組み合わせて使用される" +"ことがあります。" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpHookAdd.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpHookAdd.en.po new file mode 100644 index 00000000000..55ee5212dd7 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpHookAdd.en.po @@ -0,0 +1,117 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSHttpHookAdd.en.rst:22 +msgid "TSHttpHookAdd" +msgstr "TSHttpHookAdd" + +#: ../../reference/api/TSHttpHookAdd.en.rst:25 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSHttpHookAdd.en.rst:26 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSHttpHookAdd.en.rst:33 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSHttpHookAdd.en.rst:35 +msgid "" +"Hooks are points in Apache Traffic Server transaction HTTP processing where " +"plugins can step in and do some work. Registering a plugin function for " +"callback amounts to adding the function to a hook. You can register your " +"plugin to be called back for every single transaction, or for specific " +"transactions only." +msgstr "" +"フックは Apache Traffic Server の HTTP 処理の中でプラグインが入り込み何かで" +"きる場所です。コールバックのためのプラグインの関数を登録することはフックに関" +"数を追加することと同じです。一つずつすべてのトランザクション、もしくは特定の" +"トランザクションのみにコールバックされるプラグインを登録することができます。" + +#: ../../reference/api/TSHttpHookAdd.en.rst:41 +msgid "" +"HTTP :term:`transaction` hooks are set on a global basis using the " +"function :func:`TSHttpHookAdd`. This means that the continuation specified " +"as the parameter to :func:`TSHttpHookAdd` is called for every transaction. :" +"func:`TSHttpHookAdd` is typically called from :func:`TSPluginInit` or :func:" +"`TSRemapInit`." +msgstr "" +"HTTP :term:`transaction` フックは関数 :func:`TSHttpHookAdd` を使いグローバル" +"にセットされます。これは :func:`TSHttpHookAdd` のパラメーターとして指定され" +"た継続は全トランザクションで呼ばれるということを意味します。:func:" +"`TSHttpHookAdd` は一般的に :func:`TSPluginInit` もしくは :func:" +"`TSRemapInit` から呼ばれます。" + +#: ../../reference/api/TSHttpHookAdd.en.rst:47 +msgid "" +":func:`TSHttpSsnHookAdd` adds :arg:`contp` to the end of the list of HTTP :" +"term:`session` hooks specified by :arg:`id`. This means that :arg:`contp` " +"is called back for every transaction within the session, at the point " +"specified by the hook ID. Since :arg:`contp` is added to a session, it is " +"not possible to call :func:`TSHttpSsnHookAdd` from the plugin " +"initialization routine; the plugin needs a handle to an HTTP session." +msgstr "" +":func:`TSHttpSsnHookAdd` は :arg:`contp` を :arg:`id` で指定された HTTP :" +"term:`session` フックのリストの最後に追加します。これは :arg:`contp` がフッ" +"ク ID で指定された場所において、セッション中のすべてのトランザクションで呼び" +"出されることを意味します。:arg:`contp` がセッションに追加されるので、プラグ" +"インの初期化ルーチンから :func:`TSHttpSsnHookAdd` を呼び出すことはできませ" +"ん。プラグインは HTTP セッションを取り扱う必要があります。" + +#: ../../reference/api/TSHttpHookAdd.en.rst:55 +msgid "" +":func:`TSHttpTxnHookAdd` adds :arg:`contp` to the end of the list of HTTP " +"transaction hooks specified by :arg:`id`. Since :arg:`contp` is added to a " +"transaction, it is not possible to call :func:`TSHttpTxnHookAdd` from the " +"plugin initialization routine but only when the plugin has a handle to an " +"HTTP transaction." +msgstr "" +":func:`TSHttpTxnHookAdd` は :arg:`contp` を :arg:`id` で指定された HTTP トラ" +"ンザクションフックのリストの最後に追加します。:arg:`contp` がトランザクショ" +"ンに追加されるので、プラグインの初期化ルーチンから :func:`TSHttpTxnHookAdd` " +"を呼び出すことはできず、プラグインが HTTP トランザクションを取り扱うときのみ" +"呼び出せます。" + +#: ../../reference/api/TSHttpHookAdd.en.rst:63 +msgid "Return values" +msgstr "戻り値" + +#: ../../reference/api/TSHttpHookAdd.en.rst:65 +msgid "None. Adding hooks is always successful." +msgstr "無し。フックの追加は常に成功します。" + +#: ../../reference/api/TSHttpHookAdd.en.rst:68 +msgid "Examples" +msgstr "例" + +#: ../../reference/api/TSHttpHookAdd.en.rst:70 +msgid "" +"The following example demonstrates how to add global, session and " +"transaction hooks::" +msgstr "" +"次の例はどのようにグローバル、セッション、トランザクションフックを追加するか" +"を紹介しています。" + +#: ../../reference/api/TSHttpHookAdd.en.rst:110 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSHttpHookAdd.en.rst:111 +msgid "" +":manpage:`TSAPI(3ts)`, :manpage:`TSContCreate(3ts)`, :manpage:" +"`TSLifecycleHookAdd(3ts)`" +msgstr "" +":manpage:`TSAPI(3ts)`, :manpage:`TSContCreate(3ts)`, :manpage:" +"`TSLifecycleHookAdd(3ts)`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpOverridableConfig.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpOverridableConfig.en.po new file mode 100644 index 00000000000..387964ba8fd --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpOverridableConfig.en.po @@ -0,0 +1,93 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:24 +msgid "TSHttpOverridableConfig" +msgstr "TSHttpOverridableConfig" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:27 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:28 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:41 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:43 +msgid "" +"Some of the values that are set in :file:`records.config` can be changed " +"for a specific transaction. It is important to note that these functions " +"change the configuration values stored for the transation, which is not " +"quite the same as changing the actual operating values of the transaction. " +"The critical effect is the value must be changed before it is used by the " +"transaction - after that, changes will not have any effect." +msgstr "" +":file:`records.config` に設定されるいくつかの値は特定のトランザクションにに" +"おいて変更することが可能です。これらの関数はトランザクション用に格納された設" +"定値を変更すること、つまりトランザクションが実際に処理する際の値を変更するの" +"とまったく同じではないことに注意することが大切です。その重要な影響は値がトラ" +"ンザクションで使用される前に変更されていなければならないことです。使用された" +"後だった場合、変更は何の効果も持ちません。" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:48 +msgid "" +"All of the ``...Get`` functions store the internal value in the storage " +"indicated by the :arg:`value` argument. For strings :arg:`length*` will " +"receive the length of the string." +msgstr "" +"すべての ``...Get`` 関数は :arg:`value` 引数で示された記憶領域に内部値を格納" +"します。文字列では :arg:`length*` は文字列の長さを受け取ります。" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:50 +msgid "" +"The values are identified by the enumeration :type:" +"`TSOverridableConfigKey`. String values can be used indirectly by first " +"passing them to :func:`TSHttpTxnConfigFind` which, if the string matches an " +"overridable value, return the key and data type." +msgstr "" +"値は列挙型 :type:`TSOverridableConfigKey` で特定されます。文字列値は最初に :" +"func:`TSHttpTxnConfigFind` に渡すことで間接的に使用でき、この関数は文字列が" +"上書き可能な値に一致した場合にキーとデータ型を返します。" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:139 +msgid "Examples" +msgstr "例" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:141 +msgid "" +"Enable :ref:`transaction buffer control ` " +"with a high water mark of 262144 and a low water mark of 65536. ::" +msgstr "" +":ref:`transaction-buffering-control` を high water マーク 262144 と low " +"water マーク 65536 で有効化します。\\ ::" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:153 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:154 +msgid ":manpage:`TSAPI(3ts)`" +msgstr ":manpage:`TSAPI(3ts)`" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:55 +msgid "Configurations" +msgstr "設定" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:57 +msgid "" +"The following configurations (from ``records.config``) are overridable: ::" +msgstr "次の (``records.config`` の ) 設定は上書き可能です。" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpParserCreate.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpParserCreate.en.po new file mode 100644 index 00000000000..c9f7ff98cd8 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpParserCreate.en.po @@ -0,0 +1,107 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSHttpParserCreate.en.rst:22 +msgid "TSHttpParserCreate" +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:36 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:38 +msgid "" +":func:`TSHttpParserCreate` creates an HTTP parser object. The parser's data " +"structure contains information about the header being parsed. A single HTTP " +"parser can be used multiple times, though not simultaneously. Before being " +"used again, the parser must be cleared by calling :func:`TSHttpParserClear`." +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:44 +msgid "" +":func:`TSHttpHdrParseReq` parses an HTTP request header. The HTTP header :" +"data:`offset` must already be created, and must reside inside the marshal " +"buffer :data:`bufp`. The :data:`start` argument points to the current " +"position of the string buffer being parsed and the :data:`end` argument " +"points to one byte after the end of the buffer to be parsed. On return, :" +"data:`start` is modified to point past the last character parsed." +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:52 +msgid "" +"It is possible to parse an HTTP request header a single byte at a time " +"using repeated calls to :func:`TSHttpHdrParseReq`. As long as an error does " +"not occur, the :func:`TSHttpHdrParseReq` function will consume that single " +"byte and ask for more. :func:`TSHttpHdrParseReq` should be called after :" +"data:`TS_HTTP_READ_REQUEST_HDR_HOOK`." +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:58 +msgid "" +":func:`TSHttpHdrParseResp` operates in the same manner as :func:" +"`TSHttpHdrParseReq` except it parses an HTTP response header. It should be " +"called after :data:`TS_HTTP_READ_RESPONSE_HDR_HOOK`." +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:62 +msgid "" +":func:`TSHttpParserClear` clears the specified HTTP parser so it may be " +"used again." +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:65 +msgid "" +":func:`TSHttpParserDestroy` destroys the TSHttpParser object pointed to by :" +"data:`parser`. The :data:`parser` pointer must not be NULL." +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:69 +msgid "Return values" +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:71 +msgid "" +":func:`TSHttpHdrParseReq` and :func:`TSHttpHdrParseResp` both return a :" +"type:`TSParseResult` value. :data:`TS_PARSE_ERROR` is returned on error, :" +"data:`TS_PARSE_CONT` is returned if parsing of the header stopped because " +"the end of the buffer was reached, and :data:`TS_PARSE_DONE` or :data:" +"`TS_PARSE_OK` when a \\\\r\\\\n\\\\r\\\\n pattern is encountered, " +"indicating the end of the header." +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:79 +msgid "Bugs" +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:81 +msgid "" +"The distinction between the :data:`TS_PARSE_DONE` and :data:`TS_PARSE_OK` " +"results is not well-defined. Plugins should expect both status codes and " +"treat them equivalently." +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:86 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSHttpParserCreate.en.rst:87 +msgid ":manpage:`TSAPI(3ts)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpTxnMilestoneGet.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpTxnMilestoneGet.en.po new file mode 100644 index 00000000000..ff9349d8d78 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpTxnMilestoneGet.en.po @@ -0,0 +1,244 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:22 +msgid "TSHttpTxnMilestoneGet" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:32 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:34 +msgid "" +":func:`TSHttpTxnMilestoneGet` will fetch a specific :arg:`milestone` timer " +"value for the transaction :arg:`txnp`. These timers are calculated during " +"the lifetime of a transaction and are measured in nanoseconds from the " +"beginning of the transaction. :arg:`time` is used a pointer to storage to " +"update if the call is successful." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:41 +msgid "Value" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:41 +msgid "Milestone" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:43 +msgid ":const:`TS_MILESTONE_UA_BEGIN`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:43 +msgid "The client connection is accepted." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:44 +msgid ":const:`TS_MILESTONE_UA_READ_HEADER_DONE`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:44 +msgid "The request header from the client has been read and parsed." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:45 +msgid ":const:`TS_MILESTONE_UA_BEGIN_WRITE`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:45 +msgid "The response header write to the client starts." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:46 +msgid ":const:`TS_MILESTONE_UA_CLOSE`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:46 +msgid "Last I/O activity on the client socket, or connection abort." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:47 +msgid ":const:`TS_MILESTONE_SERVER_FIRST_CONNECT`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:47 +msgid "" +"First time origin server connect attempted or shared shared session " +"attached." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:48 +msgid ":const:`TS_MILESTONE_SERVER_CONNECT`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:48 +msgid "" +"Most recent time origin server connect attempted or shared session attached." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:49 +msgid ":const:`TS_MILESTONE_SERVER_CONNECT_END`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:49 +msgid "More recent time a connection attempt was resolved." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:50 +msgid ":const:`TS_MILESTONE_SERVER_BEGIN_WRITE`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:50 +msgid "First byte is written to the origin server connection." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:51 +msgid ":const:`TS_MILESTONE_SERVER_FIRST_READ`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:51 +msgid "First byte is read from connection to origin server." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:52 +msgid ":const:`TS_MILESTONE_SERVER_READ_HEADER_DONE`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:52 +msgid "Origin server response has been read and parsed." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:53 +msgid ":const:`TS_MILESTONE_SERVER_CLOSE`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:53 +msgid "Last I/O activity on origin server connection." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:54 +msgid ":const:`TS_MILESTONE_CACHE_OPEN_READ_BEGIN`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:54 +msgid "Initiate read of the cache." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:55 +msgid ":const:`TS_MILESTONE_CACHE_OPEN_READ_END`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:55 +msgid "Initial cache read has resolved." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:56 +msgid ":const:`TS_MILESTONE_CACHE_OPEN_WRITE_BEGIN`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:56 +msgid "Start open for cache write." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:57 +msgid ":const:`TS_MILESTONE_CACHE_OPEN_WRITE_END`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:57 +msgid "Cache has been opened for write." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:58 +msgid ":const:`TS_MILESTONE_DNS_LOOKUP_BEGIN`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:58 +msgid "Initiate host resolution in HostDB" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:59 +msgid ":const:`TS_MILESTONE_DNS_LOOKUP_END`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:59 +msgid "Host resolution resolves." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:60 +msgid ":const:`TS_MILESTONE_SM_START`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:60 +msgid "Transaction state machine is initialized." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:61 +msgid ":const:`TS_MILESTONE_SM_FINISH`" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:61 +msgid "Transaction has finished, state machine final logging has started." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:64 +msgid "" +"The server connect times predate the transmission of the ``SYN`` packet. " +"That is, before a connection to the origin server is completed." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:67 +msgid "" +"A connection attempt is *resolved* when no more connection related activity " +"remains to be done, and the connection is either established or has failed." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:70 +msgid "" +":const:`TS_MILESTONE_UA_CLOSE` and :const:`TS_MILESTONE_SERVER_CLOSE` are " +"updated continuously during the life of the transaction, every time there " +"is I/O activity. The updating stops when the corresponding connection is " +"closed, leaving the last I/O time as the final value." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:74 +msgid "" +"The cache ``OPEN`` milestones time only the initial setup, the \"open\", " +"not the full read or write." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:77 +msgid "Return values" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:79 +msgid "" +":const:`TS_SUCCESS` if successful and :arg:`time` was updated, otherwise :" +"const:`TS_ERROR`." +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:82 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSHttpTxnMilestoneGet.en.rst:83 +msgid ":manpage:`TSAPI(3ts)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSIOBufferCreate.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSIOBufferCreate.en.po new file mode 100644 index 00000000000..3b18163e5db --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSIOBufferCreate.en.po @@ -0,0 +1,108 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSIOBufferCreate.en.rst:22 +msgid "TSIOBufferCreate" +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:26 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:37 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:39 +msgid "" +"The :type:`TSIOBuffer` data structure is the building block of the TSVConn " +"abstraction. An IO buffer is composed of a list of buffer blocks which are " +"reference counted so that they can reside in multiple buffers at the same " +"time. This makes it extremely efficient to copy data from one IO buffer to " +"another using :func:`TSIOBufferCopy` since Traffic Server only needs to " +"copy pointers and adjust reference counts appropriately and not actually " +"copy any data; however applications should still strive to ensure data " +"blocks are a reasonable size." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:48 +msgid "" +"The IO buffer abstraction provides for a single writer and multiple " +"readers. In order for the readers to have no knowledge of each other, they " +"manipulate IO buffers through the :type:`TSIOBufferReader` data structure. " +"Since only a single writer is allowed, there is no corresponding :type:" +"`TSIOBufferWriter` data structure. The writer simply modifies the IO buffer " +"directly." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:55 +msgid ":func:`TSIOBufferCreate` creates an empty :type:`TSIOBuffer`." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:57 +msgid "" +":func:`TSIOBufferSizedCreate` creates an empty :type:`TSIOBuffer` with an " +"initial capacity of index bytes." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:60 +msgid "" +":func:`TSIOBufferDestroy` destroys the IO buffer bufp. Since multiple IO " +"buffers can share data, this does not necessarily free all of the data " +"associated with the IO buffer but simply decrements the appropriate " +"reference counts." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:64 +msgid "" +":func:`TSIOBufferWrite` appends length bytes from the buffer buf to the IO " +"buffer bufp and returns the number of bytes successfully written into the " +"IO buffer." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:68 +msgid "" +":func:`TSIOBufferProduce` makes nbytes of data available for reading in the " +"IO buffer bufp. A common pattern for writing to an IO buffer is to copy " +"data into a buffer block and then call INKIOBufferProduce to make the new " +"data visible to any readers." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:73 +msgid "" +"The watermark of an TSIOBuffer is the minimum number of bytes of data that " +"have to be in the buffer before calling back any continuation that has " +"initiated a read operation on this buffer. As a writer feeds data into the " +"TSIOBuffer, no readers are called back until the amount of data reaches the " +"watermark. Setting a watermark can improve performance because it avoids " +"frequent callbacks to read small amounts of data. :func:" +"`TSIOBufferWaterMarkGet` gets the current watermark for the IO buffer bufp." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:82 +msgid "" +":func:`TSIOBufferWaterMarkSet` gets the current watermark for the IO buffer " +"bufp to water_mark bytes." +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:86 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSIOBufferCreate.en.rst:88 +msgid ":manpage:`TSAPI(3ts)`, :manpage:`TSIOBufferReaderAlloc(3ts)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSInstallDirGet.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSInstallDirGet.en.po new file mode 100644 index 00000000000..d91089c0a37 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSInstallDirGet.en.po @@ -0,0 +1,69 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSInstallDirGet.en.rst:22 +msgid "TSInstallDirGet" +msgstr "TSInstallDirGet" + +#: ../../reference/api/TSInstallDirGet.en.rst:25 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSInstallDirGet.en.rst:27 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSInstallDirGet.en.rst:34 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSInstallDirGet.en.rst:36 +msgid "" +":func:`TSInstallDirGet` returns the path to the root of the Traffic Server " +"installation. :func:`TSConfigDirGet` and :func:`TSPluginDirGet` return the " +"complete, absolute path to the configuration directory and the plugin " +"installation directory respectively." +msgstr "" +":func:`TSInstallDirGet` は インストール済みの Traffic Server のルートディレ" +"クトリのパスを返します。:func:`TSConfigDirGet` と :func:`TSPluginDirGet` は" +"それぞれ設定ディレクトリとインストール済みのプラグインディレクトリへの完全な" +"絶対パスを返します。" + +#: ../../reference/api/TSInstallDirGet.en.rst:42 +msgid "Return values" +msgstr "戻り値" + +#: ../../reference/api/TSInstallDirGet.en.rst:44 +msgid "" +"These functions all return a NUL-terminated string that must not be " +"modified or freed." +msgstr "" +"これらの関数はすべて変更や解放をしてはならない NULL 終端文字列を返します。" + +#: ../../reference/api/TSInstallDirGet.en.rst:47 +msgid "Examples" +msgstr "例" + +#: ../../reference/api/TSInstallDirGet.en.rst:49 +msgid "" +"To load a file that is located in the Traffic Server configuration " +"directory::" +msgstr "Traffic Server 設定ディレクトリにあるファイルを読み込むためには::" + +#: ../../reference/api/TSInstallDirGet.en.rst:58 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSInstallDirGet.en.rst:59 +msgid ":manpage:`TSAPI(3ts)`" +msgstr ":manpage:`TSAPI(3ts)`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSLifecycleHookAdd.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSLifecycleHookAdd.en.po new file mode 100644 index 00000000000..43543ab7dfb --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSLifecycleHookAdd.en.po @@ -0,0 +1,177 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:24 +msgid "TSLifecycleHookAdd" +msgstr "TSLifecycleHookAdd" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:27 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:28 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:33 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:35 +msgid "" +":func:`TSLifecycleHookAdd` adds :arg:`contp` to the list of lifecycle hooks " +"specified by :arg:`id`. Lifecycle hooks are based on the Traffic Server " +"process, not on any specific transaction or session. These will typically " +"be called only once during the execution of the Traffic Server process and " +"therefore should be added in :func:`TSPluginInit` (which could itself be " +"considered a lifecyle hook). Unlike other hooks, lifecycle hooks may not " +"have a well defined ordering and use of them should not assume that one of " +"the hooks is always called before another unless specifically mentioned." +msgstr "" +":func:`TSLifecycleHookAdd` は :arg:`contp` を :arg:`id` で指定されるライフサ" +"イクルフックのリストに追加します。ライフサイクルフックは特定のトランザクショ" +"ンやセッションではなく Traffic Server プロセスのもとに成り立ちます。これらは" +"一般的に Traffic Server プロセスの実行中に一度だけ呼び出されるので、( それ自" +"体もライフサイクルフックとみなされる ) :func:`TSPluginInit` の中で追加される" +"べきです。他のフックと違い、ライフサイクルフックは明確な順序を持たず、使用に" +"あたっては特に言及されていない限りフックのうちの一つが常に他のどれかより前に" +"呼び出されると仮定すべきではありません。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:45 +msgid "`TS_LIFECYCLE_PORTS_INITIALIZED_HOOK`" +msgstr "`TS_LIFECYCLE_PORTS_INITIALIZED_HOOK`" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:40 +msgid "" +"Called after the :ts:cv:`proxy server port ` data structures have been initialized but before connections " +"are accepted on those ports. The sockets corresponding to the ports may or " +"may not be open depending on how the :program:`traffic_server` process was " +"invoked. Other API functions that depend on server ports should be called " +"from this hook and not :func:`TSPluginInit`." +msgstr "" +":ts:cv:`プロキシーサーバーポート ` データ構" +"造が初期化された後、接続がそれらのポート上で accept される前に呼ばれます。" +"ポートに対応するソケットは :program:`traffic_server` プロセスがどのように起" +"動されたかによって open されることもされないこともあります。サーバーポートに" +"依存するその他の API 関数は :func:`TSPluginInit` ではなくこのフックから呼ば" +"れるべきです。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:45 +msgid "" +"Invoked with the event `TS_EVENT_LIFECYCLE_PORTS_INITIALIZED` and `NULL` " +"data." +msgstr "" +"`TS_EVENT_LIFECYCLE_PORTS_INITIALIZED` イベントと `NULL` データとともに呼び" +"出されます。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:53 +msgid "`TS_LIFECYCLE_PORTS_READY_HOOK`" +msgstr "`TS_LIFECYCLE_PORTS_READY_HOOK`" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:48 +msgid "" +"Called after enabling connections on the proxy server ports. Because " +"Traffic Server is threaded this may or may not be called before any " +"connections are accepted. The hook code may assume that any connection to " +"Traffic Server started after this hook is called will be accepted by " +"Traffic Server, making this a convenient place to signal external processes " +"of that." +msgstr "" +"プロキシーサーバーポート上での接続の有効化の後に呼ばれます。Traffic Server " +"はスレッドで動作するので、接続を受け付ける前に呼ばれることも、そうでないこと" +"もあります。フックコードはこのフックが呼ばれた後に開始された Traffic Server " +"に対する接続が Traffic Server によって accept されると仮定し、そのことを外部" +"プロセスに通知する便利な場所とできます。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:53 +msgid "" +"Invoked with the event `TS_EVENT_LIFECYCLE_PORTS_READY` and `NULL` data." +msgstr "" +"`TS_EVENT_LIFECYCLE_PORTS_READY` イベントと `NULL` データとともに呼び出され" +"ます。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:58 +msgid "`TS_LIFECYCLE_CACHE_READY_HOOK`" +msgstr "`TS_LIFECYCLE_CACHE_READY_HOOK`" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:56 +msgid "Called after Traffic Server cache initialization has finished." +msgstr "Traffic Server のキャッシュの初期化が完了した後に呼ばれます。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:58 +msgid "" +"Invoked with the event `TS_EVENT_LIFECYCLE_CACHE_READY` and `NULL` data." +msgstr "" +"`TS_EVENT_LIFECYCLE_CACHE_READY` イベントと `NULL` データとともに呼び出され" +"ます。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:61 +msgid "Ordering" +msgstr "順番" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:63 +msgid "" +"`TS_LIFECYCLE_PORTS_INITIALIZED_HOOK` will always be called before " +"`TS_LIFECYCLE_PORTS_READY_HOOK`." +msgstr "" +"`TS_LIFECYCLE_PORTS_INITIALIZED_HOOK` は常に " +"`TS_LIFECYCLE_PORTS_READY_HOOK` の前に呼び出されます。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:66 +msgid "Examples" +msgstr "例" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:68 +msgid "" +"The following example demonstrates how to correctly use :func:" +"`TSNetAcceptNamedProtocol`, which requires the proxy ports to be " +"initialized and therefore does not work if called from :func:`TSPluginInit` " +"directly. ::" +msgstr "" +"次の例は :func:`TSNetAcceptNamedProtocol` を正しく使用する方法、つまりプロキ" +"シーポートが初期化され :func:`TSPluginInit` から直接呼び出された場合に動作し" +"ないようにする方法を説明しています。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:100 +msgid "History" +msgstr "歴史" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:102 +msgid "" +"Lifecycle hooks were introduced to solve process initialization ordering " +"issues (`TS-1487 `_). " +"Different API calls required different modules of Traffic Server to be " +"initialized for the call to work, but others did not work that late in " +"initialization, which was problematic because all of them could effectively " +"only be called from :func:`TSPluginInit` . The solution was to move :func:" +"`TSPluginInit` as early as possible in the process initialization and " +"provide hooks for API calls that needed to be invoked later which served " +"essentially as additional pluging initialization points." +msgstr "" +"ライフサイクルフックはプロセスの初期化順の課題を解決するために登場しました " +"(`TS-1487 `_) 。異なる API の" +"呼び出しは Traffic Server の異なるモジュールが初期化されることを要求していま" +"したが、初期化の終盤のものは動作せず、事実上 :func:`TSPluginInit` からのみ呼" +"び出すことが可能だったので問題となっていました。その解決方法は :func:" +"`TSPluginInit` をプロセスの初期化の可能な限り早い位置に移し、本来は追加のプ" +"ラグイン初期化ポイントとして提供され後で呼び出される必要のあった API 呼び出" +"しのためにフックを提供することでした。" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:108 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:109 +msgid ":manpage:`TSAPI(3ts)`, :manpage:`TSContCreate(3ts)`" +msgstr ":manpage:`TSAPI(3ts)` 、\\ :manpage:`TSContCreate(3ts)`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSMBufferCreate.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSMBufferCreate.en.po new file mode 100644 index 00000000000..039edf9bb04 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSMBufferCreate.en.po @@ -0,0 +1,104 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSMBufferCreate.en.rst:21 +msgid "TSMBufferCreate" +msgstr "TSMBufferCreate" + +#: ../../reference/api/TSMBufferCreate.en.rst:24 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSMBufferCreate.en.rst:26 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSMBufferCreate.en.rst:33 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSMBufferCreate.en.rst:35 +msgid "" +"The marshal buffer or :type:`TSMBuffer` is a heap data structure that " +"stores parsed URLs, MIME headers and HTTP headers. You can allocate new " +"objects out of marshal buffers, and change the values within the marshal " +"buffer. Whenever you manipulate an object, you require the handle to the " +"object (:type:`TSMLoc`) and the marshal buffer containing the object (:type:" +"`TSMBuffer`)." +msgstr "" +"マーシャルバッファー すなわち :type:`TSMBuffer` はパースされた URL 、MIME " +"ヘッダー、HTTP ヘッダーを格納するヒープデータ構造です。マーシャルバッファー" +"の外で新しいオブジェクトを割り当て、その値をマーシャルバッファー内で変更する" +"ことができます。オブジェクトを操作するときにはいつでも、オブジェクト (:type:" +"`TSMLoc`) のハンドルとオブジェクトを含んでいるマーシャルバッファー (:type:" +"`TSMBuffer`) が必要になります。" + +#: ../../reference/api/TSMBufferCreate.en.rst:41 +msgid "" +"Any marshal buffer fetched by :func:`TSHttpTxn*Get` will be used by other " +"parts of the system. Be careful not to destroy these shared, transaction " +"marshal buffers." +msgstr "" +":func:`TSHttpTxn*Get` によって取得されたすべてのマーシャルバッファーはシステ" +"ムの他の場所で使用されます。これらの共有されたトランザクションマーシャルバッ" +"ファーを破棄さないよう気をつけてください。" + +#: ../../reference/api/TSMBufferCreate.en.rst:44 +msgid "" +":func:`TSMBufferCreate` creates a new marshal buffer and initializes the " +"reference count. :func:`TSMBufferDestroy` Ignores the reference count and " +"destroys the marshal buffer bufp. The internal data buffer associated with " +"the marshal buffer is also destroyed if the marshal buffer allocated it." +msgstr "" +":func:`TSMBufferCreate` は新しいマーシャルバッファーを作成し参照数を初期化し" +"ます。:func:`TSMBufferDestroy` は参照数を無視してマーシャルバッファー bufp " +"を破棄します。マーシャルバッファーに紐付けられた内部データバッファーがマー" +"シャルバッファーによって割り当てられていた場合はそれも破棄されます。" + +#: ../../reference/api/TSMBufferCreate.en.rst:50 +msgid "" +":func:`TSHandleMLocRelease` Releases the :type:`TSMLoc` mloc created from " +"the :type:`TSMLoc` parent. If a :type:`TSMLoc` is obtained from a " +"transaction, it does not have a parent :type:`TSMLoc`. Use the the " +"constant :data:`TS_NULL_MLOC` as its parent." +msgstr "" +":func:`TSHandleMLocRelease` は :type:`TSMLoc` parent で作成された :type:" +"`TSMLoc` mloc を解放します。:type:`TSMLoc` がトランザクションから取得された" +"場合は parent :type:`TSMLoc` を持っていません。定数 :data:`TS_NULL_MLOC` を " +"parent として使用してください。" + +#: ../../reference/api/TSMBufferCreate.en.rst:56 +msgid "Return values" +msgstr "戻り値" + +#: ../../reference/api/TSMBufferCreate.en.rst:58 +msgid "" +":func:`TSMBufferDestroy` and :func:`TSHandleMLocRelease` return :data:" +"`TS_SUCCESS` on success, or :data:`TS_ERROR` on failure. :func:" +"`TSMBufferCreate` returns the new :type:`TSMBuffer`." +msgstr "" +":func:`TSMBufferDestroy` と :func:`TSHandleMLocRelease` は 成功時に :data:" +"`TS_SUCCESS` を返し、失敗時には :data:`TS_ERROR` を返します。:func:" +"`TSMBufferCreate` は新しい :type:`TSMBuffer` を返します。" + +#: ../../reference/api/TSMBufferCreate.en.rst:63 +msgid "Examples" +msgstr "例" + +#: ../../reference/api/TSMBufferCreate.en.rst:93 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSMBufferCreate.en.rst:95 +msgid ":manpage:`TSAPI(3ts)`" +msgstr ":manpage:`TSAPI(3ts)`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSMimeHdrFieldValueStringGet.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSMimeHdrFieldValueStringGet.en.po new file mode 100644 index 00000000000..a134a55b678 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSMimeHdrFieldValueStringGet.en.po @@ -0,0 +1,117 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-15 22:31+0900\n" +"PO-Revision-Date: 2014-02-01 15:41+0900\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:21 +msgid "TSMimeHdrFieldValueStringGet" +msgstr "TSMimeHdrFieldValueStringGet" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:25 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:27 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:37 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:39 +msgid "" +"MIME headers and fields can be components of request headers, response " +"headers, or standalone headers created within a Traffic Server plugin. The " +"functions here are all used to access header values of specific types, but " +"it is up to the caller to know if a header has appropriate semantics for " +"the API used. For all but :func:`TSMimeHdrFieldValueStringGet`, an " +"appropriate data conversion algorithm is applied to the header field string." +msgstr "" +"MIME ヘッダーとフィールドはリクエストヘッダーやレスポンスヘッダー、または " +"Traffic Server プラグイン中で作られたスタンドアローンヘッダーを構成すること" +"ができます。この関数は全て特定の型のヘッダーの値にアクセスするために使用され" +"ますが、ヘッダーが API の使用に適切な意味を持つかどうかは呼び出し元によりま" +"す。 :func:`TSMimeHdrFieldValueStringGet` 以外では適切なデータ変換アルゴリズ" +"ムがヘッダーフィールド文字列に適用されます。" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:47 +msgid "" +"All the APIs take a :type:`TSMBuffer` marshal buffer argument, and a :type:" +"`TSMLoc` argument indicating the location of the HTTP headers. The " +"required :data:`field` argument is the locator of a specific header value, " +"as returned by an accessor function such as :func:`TSMimeHdrFieldFind`." +msgstr "" +"全ての API は :type:`TSMBuffer` マーシャルバッファー引数と HTTP ヘッダーの場" +"所を指し示す :type:`TSMLoc` 引数を受け取ります。必須の :data:`field` 引数" +"は :func:`TSMimeHdrFieldFind` のようなアクセッサ関数から返される特定のヘッ" +"ダーの値を保管するものです。" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:53 +msgid "" +"Within the header field, comma-separated values can be retrieved with an " +"index (:data:`idx`) ranging from 0 to the maximum number of fields for this " +"value; this maximum is retrieved using :func:`TSMimeHdrFieldValuesCount`. " +"An :data:`idx` value of ``-1`` has the semantics of retrieving the entire " +"header value, regardless of how many comma-separated values there are. If a " +"header is not comma-separated, an :data:`idx` of :data:`0` or :data:`-1` " +"are the same, but the latter is preferred." +msgstr "" +"ヘッダーフィールドの中で、コンマで分けられた値は 0 からこの値のフィールドの" +"最大値の間のインデックス ( :data:`idx` ) で取得することができます。この最大" +"値は :func:`TSMimeHdrFieldValuesCount` で取得されます。 ``-1`` の :data:" +"`idx` 値はコンマで分けられた値がいくつあるかを考慮せずに、全てのヘッダーの値" +"を取得する意味を持ちます。ヘッダーがコンマで分けられていない場合、:data:`0` " +"と :data:`-1` の :data:`idx` は同じですが、後者が好ましいです。" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:61 +msgid "" +":func:`TSMimeHdrFieldValueStringGet` returns a pointer to the header value, " +"and populated :data:`value_len_ptr` with the length of the value in bytes. " +"The returned header value is not NUL-terminated." +msgstr "" +":func:`TSMimeHdrFieldValueStringGet` はヘッダーの値へのポインターとバイト単" +"位での値の長さで満たされた :data:`value_len_ptr` を返します。返されたヘッ" +"ダーの値は NUL 終端ではありません。" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:66 +msgid "Return values" +msgstr "戻り値" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:68 +msgid "" +"All functions returns the header value with a type matching the respective " +"function name. Using :func:`TSMimeHdrFieldValueDateGet` on a header which " +"does not have date-time semantics always returns :data:`0`." +msgstr "" +"全ての関数はヘッダーの値をそれぞれの関数名にマッチした型で返します。 date-" +"time セマンティクスを持たないヘッダーでの :func:" +"`TSMimeHdrFieldValueDateGet` の使用は常に :data:`0` を返します。" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:73 +msgid "Examples" +msgstr "例" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:75 +msgid "This examples show how to retrieve and copy a specific header." +msgstr "この例はどのように特定のヘッダーを取得しコピーするかを示しています。" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:109 +msgid "See also" +msgstr "参照" + +#: ../../reference/api/TSMimeHdrFieldValueStringGet.en.rst:111 +msgid "" +":manpage:`TSAPI(3ts)`, :manpage:`TSMBufferCreate(3ts)`, :manpage:" +"`TSMimeHdrFieldValuesCount(3ts)`" +msgstr "" +":manpage:`TSAPI(3ts)`, :manpage:`TSMBufferCreate(3ts)`, :manpage:" +"`TSMimeHdrFieldValuesCount(3ts)`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSPluginInit.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSPluginInit.en.po new file mode 100644 index 00000000000..8847384c594 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSPluginInit.en.po @@ -0,0 +1,77 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSPluginInit.en.rst:21 +msgid "TSPluginInit" +msgstr "TSPluginInit" + +#: ../../reference/api/TSPluginInit.en.rst:24 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSPluginInit.en.rst:26 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSPluginInit.en.rst:32 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSPluginInit.en.rst:34 +msgid "" +":func:`TSPluginInit` must be defined by all plugins. Traffic Server calls " +"this initialization routine when it loads the plugin and sets argc and argv " +"appropriately based on the values in plugin.config. argc is a count of the " +"number of arguments in the argument vector, argv. The count is at least one " +"because the first argument in the argument vector is the plugins name, " +"which must exist in order for the plugin to be loaded. argv is the vector " +"of arguments. The number of arguments in the vector is argc, and argv[0] " +"always contains the name of the plugin shared library. :func:" +"`TSPluginRegister` registers the appropriate SDK version for your plugin. " +"Use this function to make sure that the version of Traffic Server on which " +"your plugin is running supports the plugin." +msgstr "" +":func:`TSPluginInit` はすべてのプラグインで定義されなければなりません。 " +"Traffic Server はプラグインを読み込み argc と argv を plugin.config の値をも" +"とに適切に設定する際にこの初期化ルーチンを呼びます。argc は引数配列 argv に" +"ある引数の数です。引数配列の最初の引数はプラグイン名であり、プラグインが読み" +"込まれるために必ず存在するのでこの数は少なくとも一つになります。argv は引数" +"の配列です。配列内の引数の数は argc となり、argv[0] は常にプラグイン共有ライ" +"ブラリの名前を含んでいます。:func:`TSPluginRegister` はプラグインにとって適" +"切な SDK のバージョンを登録します。プラグインが動作する Traffic Server の" +"バージョンがそのプラグインをサポートすることを確認するためにこの関数を使用し" +"てください。" + +#: ../../reference/api/TSPluginInit.en.rst:48 +msgid "Return values" +msgstr "戻り値" + +#: ../../reference/api/TSPluginInit.en.rst:50 +msgid "" +":func:`TSPluginRegister` returns :const:`TS_ERROR` if the plugin " +"registration failed." +msgstr "" +":func:`TSPluginRegister` はプラグインの登録に失敗すると :const:`TS_ERROR` を" +"返します。" + +#: ../../reference/api/TSPluginInit.en.rst:53 +msgid "Examples" +msgstr "例" + +#: ../../reference/api/TSPluginInit.en.rst:73 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSPluginInit.en.rst:75 +msgid ":manpage:`TSAPI(3ts)`, :manpage:`TSInstallDirGet(3ts)`" +msgstr ":manpage:`TSAPI(3ts)`, :manpage:`TSInstallDirGet(3ts)`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSRemap.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSRemap.en.po new file mode 100644 index 00000000000..8efc1ab33f9 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSRemap.en.po @@ -0,0 +1,130 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSRemap.en.rst:21 +msgid "TSRemapInit" +msgstr "TSRemapInit" + +#: ../../reference/api/TSRemap.en.rst:24 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSRemap.en.rst:26 +msgid "`#include ` `#include `" +msgstr "`#include ` `#include `" + +#: ../../reference/api/TSRemap.en.rst:37 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSRemap.en.rst:49 +msgid "" +":func:`TSRemapInit` is a required entry point. This function will be called " +"once when Traffic Server loads the plugin. If the optional :func:" +"`TSRemapDone` entry point is available, Traffic Server will call then when " +"unloading the remap plugin." +msgstr "" +":func:`TSRemapInit` は必須のエントリーポイントです。この関数は Traffic " +"Serverがプラグインをロードする際に一度だけ呼ばれます。省略可能な :func:" +"`TSRemapDone` 関数がある場合、Traffic Server は remap プラグインをアンロード" +"するときにそれを呼び出します。" + +#: ../../reference/api/TSRemap.en.rst:54 +msgid "" +"A remap plugin may be invoked for different remap rules. Traffic Server " +"will call the entry point each time a plugin is specified in a remap rule. " +"When a remap plugin instance is no longer required, Traffic Server will " +"call :func:`TSRemapDeleteInstance`." +msgstr "" +"remap プラグインは異なる remap ルールのために呼び出されます。Traffic Server " +"はプラグインが remap ルールに指定されるたびにエントリーポイントを呼び出しま" +"す。remap プラグインインスタンスが必要なくなると、Traffic Server は :func:" +"`TSRemapDeleteInstance` を呼び出します。" + +#: ../../reference/api/TSRemap.en.rst:59 +msgid "" +":func:`TSRemapDoRemap` is called for each HTTP transaction. This is a " +"mandatory entry point. In this function, the remap plugin may examine and " +"modify the HTTP transaction." +msgstr "" +":func:`TSRemapDoRemap` は各 HTTP トランザクションで呼び出されます。これは必" +"須のエントリーポイントです。この関数では remap プラグインが HTTP トランザク" +"ションを検査し変更するかもしれません。" + +#: ../../reference/api/TSRemap.en.rst:64 +msgid "Return values" +msgstr "戻り値" + +#: ../../reference/api/TSRemap.en.rst:66 +msgid "" +":func:`TSRemapInit` and :func:`TSRemapNewInstance` should return :data:" +"`TS_SUCCESS` on success, and :data:`TS_ERROR` otherwise. A return value of :" +"data:`TS_ERROR` is unrecoverable." +msgstr "" +":func:`TSRemapInit` と :func:`TSRemapNewInstance` は成功時に :data:" +"`TS_SUCCESS` を、それ以外の時には :data:`TS_ERROR` を返すべきです。戻り値 :" +"data:`TS_ERROR` は回復不可能です。" + +#: ../../reference/api/TSRemap.en.rst:70 +msgid "" +":func:`TSRemapDoRemap` returns a status code that indicates whether the " +"HTTP transaction has been modified and whether Traffic Server should " +"continue to evaluate the chain of remap plugins. If the transaction was " +"modified, the plugin should return :data:`TSREMAP_DID_REMAP` or :data:" +"`TSREMAP_DID_REMAP_STOP`; otherwise it should return :data:" +"`TSREMAP_NO_REMAP` or :data:`TSREMAP_NO_REMAP_STOP`. If Traffic Server " +"should not send the transaction to subsequent plugins in the remap chain, " +"return :data:`TSREMAP_NO_REMAP_STOP` or :data:`TSREMAP_DID_REMAP_STOP`. " +"Returning :data:`TSREMAP_ERROR` causes Traffic Server to stop evaluating " +"the remap chain and respond with an error." +msgstr "" +":func:`TSRemapDoRemap` は HTTP トランザクションが変更されたかどうか、そして " +"Traffic Server が remap プラグインの評価を続けるべきかどうかを示すステータス" +"コードを返します。トランザクションが変更されていた場合、プラグインは:data:" +"`TSREMAP_DID_REMAP` または :data:`TSREMAP_DID_REMAP_STOP` を返すべきです。そ" +"れ以外の場合は :data:`TSREMAP_NO_REMAP` または :data:" +"`TSREMAP_NO_REMAP_STOP` を返すべきです。Traffic Server がトランザクションを " +"remap チェーンの続きのプラグインに送信すべきではない場合は、:data:" +"`TSREMAP_NO_REMAP_STOP` または :data:`TSREMAP_DID_REMAP_STOP` を返します。:" +"data:`TSREMAP_ERROR` を返すと Traffic Server に remap チェーンの評価を止めさ" +"せ、エラーを返させます。" + +#: ../../reference/api/TSRemap.en.rst:83 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSRemap.en.rst:85 +msgid ":manpage:`TSAPI(3ts)`" +msgstr ":manpage:`TSAPI(3ts)`" + +#: ../../reference/api/TSRemap.en.rst:39 +msgid "" +"The Traffic Server remap interface provides a simplified mechanism for " +"plugins to manipulate HTTP transactions. A remap plugin is not global; it " +"is configured on a per-remap rule basis, which enables you to customize how " +"URLs are redirected based on individual rules in the remap.config file. " +"Writing a remap plugin consists of implementing one or more of the remap " +"entry points and configuring the remap.config configuration file to route " +"the transaction through your plugin. Multiple remap plugins can be " +"specified for a single remap rule, resulting in a remap plugin chain where " +"each plugin is given an opportunity to examine the HTTP transaction." +msgstr "" +"Traffic Server の remap インターフェースはプラグインが HTTP トランザク" +"ションを操作するための簡素な仕組みを提供します。remap プラグインは大域的" +"ではありません。それは remap ルール毎に設定され、remap.config ファイル内" +"の個々のルールに基づいて URL がどのようにリダイレクトされるかをカスタマイ" +"ズできるようにしています。一つ以上の remap エントリーポイントを満たすこと" +"と、トランザクションがプラグインを通るように remap.config を設定すること" +"から remap プラグインを書くことは成り立っています。複数の remap プラグイ" +"ンが一つの remap ルールに指定されることもあり、HTTP トランザクションを検" +"査する機会が各プラグインに与えられる remap プラグインチェーンとなります。" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSTrafficServerVersionGet.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSTrafficServerVersionGet.en.po new file mode 100644 index 00000000000..04b3f482f3c --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSTrafficServerVersionGet.en.po @@ -0,0 +1,53 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:21 +msgid "TSTrafficServerVersionGet" +msgstr "TSTrafficServerVersionGet" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:24 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:26 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:34 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:36 +msgid "" +":func:`TSTrafficServerVersionGet` returns a pointer to a string of " +"characters that indicates the Traffic Server release version. This string " +"must not be modified." +msgstr "" +":func:`TSTrafficServerVersionGet` は Traffic Server のリリースバージョンを示" +"す文字列へのポインターを返します。この文字列は変更してはいけません。" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:40 +msgid "The other APIs return an integer version number." +msgstr "その他の API は整数のバージョン番号を返します。" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:43 +msgid "Example" +msgstr "例" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:96 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:98 +msgid ":manpage:`TSAPI(3ts)`" +msgstr ":manpage:`TSAPI(3ts)`" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSTypes.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSTypes.en.po new file mode 100644 index 00000000000..b3bd8149667 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSTypes.en.po @@ -0,0 +1,106 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSTypes.en.rst:21 +msgid "TSAPI Types" +msgstr "TSAPI 型" + +#: ../../reference/api/TSTypes.en.rst:24 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSTypes.en.rst:25 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSTypes.en.rst:26 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSTypes.en.rst:29 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSTypes.en.rst:31 +msgid "" +"The Apache Traffic Server API provides large number of types. Many of them " +"are specific to a particular API function or function group, but others are " +"used more widely. Those are described on this page." +msgstr "" +"Apache Traffic Server API は多数の型を提供します。それらの多くは特定の API " +"関数や関数グループに固有のものですが、それ以外はより広範囲で使用されます。そ" +"れらはこのページで解説されます。" + +#: ../../reference/api/TSTypes.en.rst:36 +msgid "An opaque type that represents a Traffic Server :term:`continuation`." +msgstr "Traffic Server の\\ :term:`継続`\\ を表現する不明瞭な型。" + +#: ../../reference/api/TSTypes.en.rst:40 +msgid "" +"An enumeration that identifies a specific type of hook for HTTP " +"transactions." +msgstr "HTTP トランザクション用の特定のタイプのフックを特定する列挙型。" + +#: ../../reference/api/TSTypes.en.rst:44 +msgid "An opaque type that represents a Traffic Server :term:`session`." +msgstr "Traffic Server :term:`session` を表現する不明瞭な型。" + +#: ../../reference/api/TSTypes.en.rst:48 +msgid "\"High Resolution Time\"" +msgstr "\"高精度の時間\"" + +#: ../../reference/api/TSTypes.en.rst:50 +msgid "A 64 bit time value, measured in nanoseconds." +msgstr "ナノ秒で計られた 64 ビットの時間値。" + +#: ../../reference/api/TSTypes.en.rst:54 +msgid "" +"An opaque type that represents a Traffic Server HTTP :term:`transaction`." +msgstr "Traffic Server HTTP :term:`transaction` を表現する不明瞭な型。" + +#: ../../reference/api/TSTypes.en.rst:58 +msgid "" +"An enumeration that identifies a :ref:`life cycle hook `." +msgstr ":ref:`life cycle hook ` を識別する列挙型。" + +#: ../../reference/api/TSTypes.en.rst:62 +msgid "" +"An indicator of the results of an API call. A value of :const:`TS_SUCCESS` " +"means the call was successful. Any other value indicates a failure and is " +"specific to the API call." +msgstr "" +"API 呼び出しの結果。:const:`TS_SUCCESS` は呼び出しの成功を意味します。その他" +"の値は失敗を意味し、API 呼び出しに固有のものです。" + +#: ../../reference/api/TSTypes.en.rst:67 +msgid "" +"An enumeration that specifies the type of a value in an internal data " +"structure that is accessible via the API." +msgstr "API からアクセス可能な内部データ構造の値の型を表現する列挙型。" + +#: ../../reference/api/TSTypes.en.rst:71 +msgid "" +"The type used internally for an integer. This corresponds to the value :" +"const:`TS_RECORDDATATYPE_INT` for :type:`TSRecordDataType`." +msgstr "" +"内部で整数として使われる型。これは :type:`TSRecordDataType` の :const:" +"`TS_RECORDDATATYPE_INT` に相当します。" + +#: ../../reference/api/TSTypes.en.rst:76 +msgid "" +"The type used internally for a floating point value. This corresponds to " +"the value :const:`TS_RECORDDATATYPE_FLOAT` for :type:`TSRecordDataType`." +msgstr "" +"内部で浮動小数点の値として使われる型。これは :type:`TSRecordDataType` の :" +"const:`TS_RECORDDATATYPE_FLOAT` に相当します。" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlCreate.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlCreate.en.po new file mode 100644 index 00000000000..3d93329e3f8 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlCreate.en.po @@ -0,0 +1,98 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSUrlCreate.en.rst:22 +msgid "TSUrlCreate" +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:35 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:78 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:37 +msgid "" +"The URL data structure is a parsed version of a standard internet URL. The " +"Traffic Server URL API provides access to URL data stored in marshal " +"buffers. The URL functions can create, copy, retrieve or delete entire " +"URLs, and retrieve or modify parts of URLs, such as their host, port or " +"scheme information." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:43 +msgid "" +":func:`TSUrlCreate` creates a new URL within the marshal buffer :data:" +"`bufp`. Release the resulting handle with a call to :func:" +"`TSHandleMLocRelease`." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:47 +msgid "" +":func:`TSUrlClone` copies the contents of the URL at location :data:" +"`src_url` within the marshal buffer :data:`src_bufp` to a location within " +"the marshal buffer :data:`dest_bufp`. Release the returned handle with a " +"call to :func:`TSHandleMLocRelease`." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:52 +msgid "" +":func:`TSUrlCopy` copies the contents of the URL at location :data:" +"`src_url` within the marshal buffer :data:`src_bufp` to the location :data:" +"`dest_url` within the marshal buffer dest_bufp. :func:`TSUrlCopy` works " +"correctly even if :data:`src_bufp` and :data:`dest_bufp` point to different " +"marshal buffers. It is important for the destination URL (its marshal " +"buffer and :type:`TSMLoc`) to have been created before copying into it." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:59 +msgid "" +":func:`TSUrlParse` parses a URL. The :data:`start` pointer is both an input " +"and an output parameter and marks the start of the URL to be parsed. After " +"a successful parse, the :data:`start` pointer equals the :data:`end` " +"pointer. The :data:`end` pointer must be one byte after the last character " +"you want to parse. The URL parsing routine assumes that everything between :" +"data:`start` and :data:`end` is part of the URL. It is up to higher level " +"parsing routines, such as :func:`TSHttpHdrParseReq`, to determine the " +"actual end of the URL." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:69 +msgid "Return values" +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:71 +msgid "" +"The :func:`TSUrlParse` function returns a :type:`TSParseResult`, where :" +"data:`TS_PARSE_ERROR` indicates an error. Success is indicated by one of :" +"data:`TS_PARSE_DONE`, :data:`TS_PARSE_OK` or :data:`TS_PARSE_CONT`. The " +"other APIs all return a :type:`TSReturnCode`, indicating success (:data:" +"`TS_SUCCESS`) or failure (:data:`TS_ERROR`) of the operation." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:80 +msgid "" +":manpage:`TSAPI(3ts)`, :manpage:`TSMBufferCreate(3ts)`, :manpage:" +"`TSUrlHostGet(3ts)`, :manpage:`TSUrlHostSet(3ts)`, :manpage:" +"`TSUrlStringGet(3ts)`, :manpage:`TSUrlPercentEncode(3ts)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlHostGet.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlHostGet.en.po new file mode 100644 index 00000000000..904a905dc16 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlHostGet.en.po @@ -0,0 +1,85 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-15 22:31+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSUrlHostGet.en.rst:22 +msgid "TSUrlHostGet" +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:40 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:42 +msgid "" +"The URL data structure is a parsed version of a standard internet URL. The " +"Traffic Server URL API provides access to URL data stored in marshal " +"buffers. The URL functions can create, copy, retrieve or delete entire " +"URLs, and retrieve or modify parts of URLs, such as their host, port or " +"scheme information." +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:48 +msgid "" +":func:`TSUrlSchemeGet`, :func:`TSUrlUserGet`, :func:`TSUrlPasswordGet`, :" +"func:`TSUrlHostGet`, :func:`TSUrlHttpParamsGet`, :func:`TSUrlHttpQueryGet` " +"and :func:`TSUrlHttpFragmentGet` each retrieve an internal pointer to the " +"specified portion of the URL from the marshall buffer :data:`bufp`. The " +"length of the returned string is placed in :data:`length` and a pointer to " +"the URL portion is returned." +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:55 +msgid "" +":func:`TSUrlPortGet` retrieves the port number portion of the URL located " +"at :data:`offset` within the marshal buffer :data:`bufp`. If there is no " +"explicit port number in the URL, a canonicalized valued is returned based " +"on the URL scheme." +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:61 +msgid "Return values" +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:63 +msgid "" +"All APIs except :func:`TSUrlPortGet` returns a string, which is not " +"guaranteed to be NULL terminated. You must therefore always use the :data:" +"`length` value to determine the actual length of the returned string." +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:67 +msgid "" +":func:`TSUrlPortGet` simply returns the port number as an integer, possibly " +"canonicalized with :data:`80` for HTTP and :data:`443` for HTTPS schemes. " +"If there is neither port nor scheme information available in the URL, :data:" +"`0` is returned." +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:73 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSUrlHostGet.en.rst:75 +msgid "" +":manpage:`TSAPI(3ts)`, :manpage:`TSUrlCreate(3ts)`, :manpage:" +"`TSUrlHostSet(3ts)`, :manpage:`TSUrlStringGet(3ts)`, :manpage:" +"`TSUrlPercentEncode(3ts)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlHostSet.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlHostSet.en.po new file mode 100644 index 00000000000..098bd4cbf8e --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlHostSet.en.po @@ -0,0 +1,77 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-15 22:31+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSUrlHostSet.en.rst:22 +msgid "TSUrlHostSet" +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:40 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:42 +msgid "" +"The URL data structure is a parsed version of a standard internet URL. The " +"Traffic Server URL API provides access to URL data stored in marshal " +"buffers. The URL functions can create, copy, retrieve or delete entire " +"URLs, and retrieve or modify parts of URLs, such as their host, port or " +"scheme information." +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:48 +msgid "" +":func:`TSUrlSchemeSet`, :func:`TSUrlUserSet`, :func:`TSUrlPasswordSet`, :" +"func:`TSUrlHostSet`, :func:`TSUrlHttpParamsSet`, :func:`TSUrlHttpQuerySet` " +"and :func:`TSUrlHttpFragmentSet` each set the specified portion of the URL " +"located at offset within the marshal buffer :data:`bufp` to the string " +"value. If :data:`length` is :data:`-1` then these functions assume that " +"value is NULL-terminated. Otherwise, the length of the :data:`string` value " +"is taken to be the value of :data:`length`. These functions copy the string " +"to within :data:`bufp`, so it can be subsequently modified or deleted." +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:57 +msgid "" +":func:`TSUrlPortSet` sets the port number portion of the URL located at :" +"data:`offset` within the marshal buffer :data:`bufp` to the value port. " +"Normal canonicalization based on the URL scheme still applies." +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:62 +msgid "Return values" +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:64 +msgid "" +"All these APIs returns a :type:`TSReturnCode`, indicating success (:data:" +"`TS_SUCCESS`) or failure (:data:`TS_ERROR`) of the operation." +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:68 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSUrlHostSet.en.rst:70 +msgid "" +":manpage:`TSAPI(3ts)`, :manpage:`TSUrlCreate(3ts)`, :manpage:" +"`TSUrlHostGet(3ts)`, :manpage:`TSUrlStringGet(3ts)`, :manpage:" +"`TSUrlPercentEncode(3ts)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlPercentEncode.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlPercentEncode.en.po new file mode 100644 index 00000000000..d637a3eb6f8 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlPercentEncode.en.po @@ -0,0 +1,76 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-15 22:31+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:22 +msgid "TSUrlPercentEncode" +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:34 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:36 +msgid "" +"The URL data structure is a parsed version of a standard internet URL. The " +"Traffic Server URL API provides access to URL data stored in marshal " +"buffers. The URL functions can create, copy, retrieve or delete entire " +"URLs, and retrieve or modify parts of URLs, such as their host, port or " +"scheme information." +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:42 +msgid "" +":func:`TSUrlPercentEncode` performs percent-encoding of the URL object, " +"storing the new string in the :data:`dst` buffer. The :data:`length` " +"parameter will be set to the new (encoded) string length, or :data:`0` if " +"the encoding failed. :func:`TSStringPercentEncode` is similar but operates " +"on a string. If the optional :data:`map` parameter is provided (not :data:" +"`NULL`) , it should be a map of characters to encode." +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:49 +msgid "" +":func:`TSStringPercentDecode` perform percent-decoding of the string in " +"the :data:`str` buffer, writing to the :data:`dst` buffer. The source and " +"destination can be the same, in which case they overwrite. The decoded " +"string is always guaranteed to be no longer than the source string." +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:55 +msgid "Return values" +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:57 +msgid "" +"All these APIs returns a :type:`TSReturnCode`, indicating success (:data:" +"`TS_SUCCESS`) or failure (:data:`TS_ERROR`) of the operation." +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:61 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSUrlPercentEncode.en.rst:63 +msgid "" +":manpage:`TSAPI(3ts)`, :manpage:`TSUrlCreate(3ts)`, :manpage:" +"`TSUrlHostGet(3ts)`, :manpage:`TSUrlHostSet(3ts)`, :manpage:" +"`TSUrlStringGet(3ts)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlStringGet.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlStringGet.en.po new file mode 100644 index 00000000000..31169572a41 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlStringGet.en.po @@ -0,0 +1,73 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-15 22:31+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSUrlStringGet.en.rst:22 +msgid "TSUrlStringGet" +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:35 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:37 +msgid "" +"The URL data structure is a parsed version of a standard internet URL. The " +"Traffic Server URL API provides access to URL data stored in marshal " +"buffers. The URL functions can create, copy, retrieve or delete entire " +"URLs, and retrieve or modify parts of URLs, such as their host, port or " +"scheme information." +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:43 +msgid "" +":func:`TSUrlStringGet` constructs a string representation of the URL " +"located at :data:`offset` within the marshal buffer :data:`bufp`. :func:" +"`TSUrlStringGet` stores the length of the allocated string in the " +"parameter :data:`length`. This is the same length that :func:" +"`TSUrlLengthGet` returns. The returned string is allocated by a call to :" +"func:`TSmalloc` and must be freed by a call to :func:`TSfree`. If length " +"is :data:`NULL` then no attempt is made to de-reference it." +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:51 +msgid "" +":func:`TSUrlLengthGet` calculates the length of the URL located at :data:" +"`offset` within the marshal buffer bufp as if it were returned as a string. " +"This length will be the same as the length returned by :func:" +"`TSUrlStringGet`." +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:56 +msgid "" +":func:`TSUrlPrint` formats a URL stored in an :type:`TSMBuffer` to an :type:" +"`TSIOBuffer`." +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:60 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSUrlStringGet.en.rst:62 +msgid "" +":manpage:`TSAPI(3ts)`, :manpage:`TSmalloc(3ts)`, :manpage:" +"`TSUrlCreate(3ts)`, :manpage:`TSUrlHostGet(3ts)`, :manpage:" +"`TSUrlHostSet(3ts)`, :manpage:`TSUrlPercentEncode(3ts)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/TSmalloc.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/TSmalloc.en.po new file mode 100644 index 00000000000..099f3b8351d --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSmalloc.en.po @@ -0,0 +1,122 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/TSmalloc.en.rst:22 +msgid "TSmalloc" +msgstr "TSmalloc" + +#: ../../reference/api/TSmalloc.en.rst:25 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/api/TSmalloc.en.rst:27 +msgid "`#include `" +msgstr "`#include `" + +#: ../../reference/api/TSmalloc.en.rst:38 +msgid "Description" +msgstr "解説" + +#: ../../reference/api/TSmalloc.en.rst:40 +msgid "" +"Traffic Server provides a number of routines for allocating and freeing " +"memory. These routines correspond to similar routines in the C library. For " +"example, :func:`TSrealloc` behaves like the C library routine :func:" +"`realloc`. There are two reasons to use the routines provided by Traffic " +"Server. The first is portability. The Traffic Server API routines behave " +"the same on all of Traffic Servers supported platforms. For example, :func:" +"`realloc` does not accept an argument of :data:`NULL` on some platforms. " +"The second reason is that the Traffic Server routines actually track the " +"memory allocations by file and line number. This tracking is very " +"efficient, is always turned on, and is useful for tracking down memory " +"leaks." +msgstr "" +"Traffic Server はメモリの割り当てと解放のための多数のルーチンを提供します。" +"これらのルーチンは C ライブラリの似たものに対応します。例えば、:func:" +"`TSrealloc` は C ライブラリルーチンの :func:`realloc` のように振る舞います。" +"Traffic Server によって提供されるルーチンを使う理由は二つあります。一つ目は" +"移植性です。Traffic Server API ルーチンは Traffic Server が対応するすべての" +"プラットフォーム上で同様に振る舞います。例えば、:func:`realloc` はいくつかの" +"プラットフォームで :data:`NULL` の引数を受け付けません。二つ目の理由は " +"Traffic Server ルーチンが実はファイルと行番号でメモリの割り当てを追跡してい" +"ることです。この追跡はとても優れており、常に有効化され、メモリーリークを探し" +"出すのに便利です。" + +#: ../../reference/api/TSmalloc.en.rst:51 +msgid "" +":func:`TSmalloc` returns a pointer to size bytes of memory allocated from " +"the heap. Traffic Server uses :func:`TSmalloc` internally for memory " +"allocations. Always use :func:`TSfree` to release memory allocated by :func:" +"`TSmalloc`; do not use :func:`free`." +msgstr "" +":func:`TSmalloc` はヒープに割り当てられた size バイトのメモリを指すポイン" +"ターを返します。Traffic Server メモリ割り当てのために内部で :func:" +"`TSmalloc` を使用します。:func:`TSmalloc` で割り当てられたメモリーを解放する" +"には常に :func:`TSfree` を使用し、:func:`free` は使用しないでください。" + +#: ../../reference/api/TSmalloc.en.rst:67 +msgid "" +":func:`TSstrlcpy` copies up to size - 1 characters from the NUL-terminated " +"string src to dst, NUL-terminating the result." +msgstr "" +":func:`TSstrlcpy` は NUL 終端文字列 src から dst に size - 1 文字までコピー" +"し、結果を NUL 終端します。`" + +#: ../../reference/api/TSmalloc.en.rst:70 +msgid "" +":func:`TSstrlcat` appends the NUL-terminated string src to the end of dst. " +"It will append at most size - strlen(dst) - 1 bytes, NUL-terminating the " +"result." +msgstr "" +":func:`TSstrlcat` は NUL 終端文字列 src を dst の終わりに追加します。これは" +"最大で size - strlen(dst) - 1 を追加し、結果を NUL 終端します。" + +#: ../../reference/api/TSmalloc.en.rst:74 +msgid "" +":func:`TSfree` releases the memory allocated by :func:`TSmalloc` or :func:" +"`TSrealloc`. If ptr is :data:`NULL`, :func:`TSfree` does no operation." +msgstr "" +":func:`TSfree` は :func:`TSmalloc` または :func:`TSrealloc` によって割り当て" +"られたメモリーを解放します。ptr が :data:`NULL` の場合、:func:`TSfree` は何" +"も行いません。" + +#: ../../reference/api/TSmalloc.en.rst:78 +msgid "See also" +msgstr "参考" + +#: ../../reference/api/TSmalloc.en.rst:79 +msgid ":manpage:`TSAPI(3ts)`" +msgstr ":manpage:`TSAPI(3ts)`" + +#: ../../reference/api/TSmalloc.en.rst:56 +msgid "" +":func:`TSstrdup` returns a pointer to a new string that is a duplicate of " +"the string pointed to by str. The memory for the new string is allocated " +"using :func:`TSmalloc` and should be freed by a call to :func:`TSfree`. :" +"func:`TSstrndup` returns a pointer to a new string that is a duplicate of " +"the string pointed to by str and size bytes long. The new string will be " +"NUL-terminated. This API is very useful for transforming non NUL-terminated " +"string values returned by APIs such as :func:`TSMimeHdrFieldValueStringGet` " +"into NUL-terminated string values. The memory for the new string is " +"allocated using :func:`TSmalloc` and should be freed by a call to :func:" +"`TSfree`." +msgstr "" +":func:`TSstrdup` は str で指し示された文字列を複製した新しい文字列を指す" +"ポインターを返します。新しい文字列のメモリーは :func:`TSmalloc` を使用し" +"て割り当てられ、:func:`TSfree` の呼び出しに酔って解放されるべきです。:" +"func:`TSstrndup` は size バイトの長さの str で指し示された文字列を複製し" +"た新しい文字列を指すポインターを返します。新しい文字列は NUL 終端されま" +"す。この API は :func:`TSMimeHdrFieldValueStringGet` などによって返された" +"非 NUL 終端文字列値を NUL 終端文字列値に変換するのにとても便利です。新し" +"い文字列のメモリーは :func:`TSmalloc` を使用して割り当てられ、:func:" +"`TSfree` の呼び出しに酔って解放されるべきです。" diff --git a/doc/locale/ja/LC_MESSAGES/reference/api/index.en.po b/doc/locale/ja/LC_MESSAGES/reference/api/index.en.po new file mode 100644 index 00000000000..8e22c932df4 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/index.en.po @@ -0,0 +1,16 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/api/index.en.rst:2 +msgid "API Reference" +msgstr "API リファレンス" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/index.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/index.en.po new file mode 100644 index 00000000000..d042fa46b7e --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/index.en.po @@ -0,0 +1,16 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: 2014-01-11 20:10+0900\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/index.en.rst:19 +msgid "Command Reference" +msgstr "コマンドリファレンス" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_cop.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_cop.en.po new file mode 100644 index 00000000000..765a2bfacc0 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_cop.en.po @@ -0,0 +1,69 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/traffic_cop.en.rst:20 +msgid "traffic_cop" +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:25 +msgid "Description" +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:27 +msgid "" +":program:`traffic_cop` is a watchdog program that is responsible for " +"starting :program:`traffic_manager` and :program:`traffic_server` and " +"monitoring them for responsiveness. If either of these processes are " +"determined to be unresponsive, :program:`traffic_cop` will kill and restart " +"them." +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:33 +msgid "" +"On Linux, :program:`traffic_cop` will also monitor available memory and " +"swap space, restarting the watched processes if the available memory falls " +"below a minimum threshold. The memory thresholds can be configured with " +"the :ts:cv:`proxy.config.cop.linux_min_swapfree_kb` and :ts:cv:`proxy." +"config.cop.linux_min_memfree_kb` variables." +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:39 +msgid "The following options are available:" +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:43 +msgid "" +"Kill children using ``SIGSTOP`` instead of ``SIGKILL``. This option is " +"primarily for debugging." +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:48 +msgid "Print version information and exit." +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:50 +msgid "" +":program:`traffic_cop` ordinarily logs to syslog, however for debugging " +"purposes, the ``--enable-cop-debug`` build option causes it to log trace " +"messages to :file:`/tmp/traffic_cop.trace`." +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:56 +msgid "See also" +msgstr "" + +#: ../../reference/commands/traffic_cop.en.rst:58 +msgid "" +":manpage:`syslog(1)`, :manpage:`traffic_manager(8)`, :manpage:" +"`traffic_server(8)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_line.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_line.en.po new file mode 100644 index 00000000000..c80d2455586 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_line.en.po @@ -0,0 +1,202 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: 2014-01-15 23:12+0900\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/traffic_line.en.rst:20 +msgid "traffic_line" +msgstr "traffic_line" + +#: ../../reference/commands/traffic_line.en.rst:23 +msgid "Synopsis" +msgstr "概要" + +#: ../../reference/commands/traffic_line.en.rst:26 +msgid ":program:`traffic_line` [options]" +msgstr ":program:`traffic_line` [options]" + +#: ../../reference/commands/traffic_line.en.rst:31 +msgid "Description" +msgstr "解説" + +#: ../../reference/commands/traffic_line.en.rst:33 +msgid "" +":program:`traffic_line` is used to execute individual Traffic Server " +"commands and to script multiple commands in a shell." +msgstr "" +":program:`traffic_line` はシェルの中で単一の Traffic Server コマンドを実行し" +"たり、複数のコマンドを書くために使われます。" + +#: ../../reference/commands/traffic_line.en.rst:37 +msgid "Options" +msgstr "オプション" + +#: ../../reference/commands/traffic_line.en.rst:43 +msgid "" +"Bounce all Traffic Server nodes in the cluster. Bouncing Traffic Server " +"shuts down and immediately restarts Traffic Server, node-by-node." +msgstr "" +"クラスター内の全ての Traffic Server ノードを再起動します。ノードからノード" +"へ Traffic Server のバウンシングはシャットダウンし、すぐに Traffic Server を" +"再起動します。" + +#: ../../reference/commands/traffic_line.en.rst:49 +msgid "" +"Bounce Traffic Server on the local node. Bouncing Traffic Server shuts down " +"and immediately restarts the Traffic Server node." +msgstr "" +"ローカルノードで Traffic Server を再起動させます。Traffic Server のバウンス" +"はシャットダウンし、すぐに Traffic Server ノードを再起動します。" + +#: ../../reference/commands/traffic_line.en.rst:54 +msgid "Clears accumulated statistics on all nodes in the cluster." +msgstr "クラスター内の全てのノードに蓄積された統計をクリアします。" + +#: ../../reference/commands/traffic_line.en.rst:58 +msgid "Clears accumulated statistics on the local node." +msgstr "ローカルノードに蓄積された統計をクリアします。" + +#: ../../reference/commands/traffic_line.en.rst:62 +msgid "Print usage information and exit." +msgstr "使い方の情報を表示し、終了します。" + +#: ../../reference/commands/traffic_line.en.rst:66 +msgid "" +"Restart the :program:`traffic_manager` and :program:`traffic_server` " +"processes on the local node." +msgstr "" +"ローカルノードの :program:`traffic_manager` と :program:`traffic_server` プ" +"ロセスを再起動します。" + +#: ../../reference/commands/traffic_line.en.rst:71 +msgid "" +"Restart the :program:`traffic_manager` process and the :program:" +"`traffic_server` process on all the nodes in a cluster." +msgstr "" +"クラスター内の全てのノードの :program:`traffic_manager` プロセスと :program:" +"`traffic_server` プロセスを再起動します。" + +#: ../../reference/commands/traffic_line.en.rst:76 +msgid "" +"Display specific performance statistics or a current configuration setting." +msgstr "特定のパフォーマンス統計や現在の設定を表示します。" + +#: ../../reference/commands/traffic_line.en.rst:81 +msgid "" +"Set the configuration variable named `VAR`. The value of the configuration " +"variable is given by the :option:`traffic_line -v` option. Refer to the :" +"file:`records.config` documentation for a list of the configuration " +"variables you can specify." +msgstr "" +"`VAR` という名前の設定変数をセットします。設定変数の値は :option:" +"`traffic_line -v` オプションで与えられます。記述できる設定変数のリストについ" +"ては :file:`records.config` のドキュメントを参照してください。" + +#: ../../reference/commands/traffic_line.en.rst:88 +msgid "Shut down Traffic Server on the local node." +msgstr "ローカルノードの Traffic Server をシャットダウンします。" + +#: ../../reference/commands/traffic_line.en.rst:92 +msgid "Start Traffic Server on the local node." +msgstr "ローカルノードの Traffic Server を起動します。" + +#: ../../reference/commands/traffic_line.en.rst:96 +msgid "Specify the value to set when setting a configuration variable." +msgstr "設定変数を設定する際の値を記述します。" + +#: ../../reference/commands/traffic_line.en.rst:100 +msgid "Print version information and exit." +msgstr "バージョン情報を表示して、終了します。" + +#: ../../reference/commands/traffic_line.en.rst:104 +msgid "" +"Initiate a Traffic Server configuration file reread. Use this command to " +"update the running configuration after any configuration file modification." +msgstr "" +"Traffic Server 設定ファイルの再読み込みを始めます。設定ファイルを変更した後" +"で、実行する設定を更新するのにこのコマンドを使用してください。" + +#: ../../reference/commands/traffic_line.en.rst:110 +msgid "Reset performance statistics to zero across the cluster." +msgstr "クラスター内のパフォーマンス統計をゼロにリセットします。" + +#: ../../reference/commands/traffic_line.en.rst:114 +msgid "Reset performance statistics to zero on the local node." +msgstr "ローカルノードのパフォーマンス統計をゼロにリセットします。" + +#: ../../reference/commands/traffic_line.en.rst:141 +msgid "Performance Statistics" +msgstr "パフォーマンス統計" + +#: ../../reference/commands/traffic_line.en.rst:145 +msgid "" +"The :option:`traffic_line -r` option accepts the following variable names::" +msgstr ":option:`traffic_line -r` オプションは次の変数名を受け入れます。" + +#: ../../reference/commands/traffic_line.en.rst:797 +msgid "Examples" +msgstr "例" + +#: ../../reference/commands/traffic_line.en.rst:799 +msgid "Configure Traffic Server to log in Squid format::" +msgstr "Squid フォーマットでログを取るように Traffic Server を設定するには" + +#: ../../reference/commands/traffic_line.en.rst:806 +msgid "Files" +msgstr "ファイル" + +#: ../../reference/commands/traffic_line.en.rst:808 +msgid ":file:`records.config`, :file:`ssl_multicert.config`" +msgstr ":file:`records.config`、 :file:`ssl_multicert.config`" + +#: ../../reference/commands/traffic_line.en.rst:811 +msgid "See also" +msgstr "参照" + +#: ../../reference/commands/traffic_line.en.rst:813 +msgid ":manpage:`records.config(5)`" +msgstr ":manpage:`records.config(5)`" + +#: ../../reference/commands/traffic_line.en.rst:118 +msgid "" +"Mark a cache storage device as offline. The storage is identified by a " +"*path* which must match exactly a path specified in :file:`storage.config`. " +"This removes the storage from the cache and redirects requests that would " +"have used this storage to other storage. This has exactly the same effect " +"as a disk failure for that storage. This does not persist across restarts " +"of the :program:`traffic_server` process." +msgstr "" +"キャッシュストレージデバイスをオフラインとしてマークします。ストレージは " +":file:`storage.config` 内で指定されているパスと完全に一致している \\ *パス*\\ " +"によって特定されます。これはストレージをキャッシュから取り除き、このストレージ" +"ではなく他のストレージを使うようにリクエストをリダイレクトします。これはその" +"ストレージが故障したときとまったく同じ効果を持っています。これは " +":program:`traffic_server` プロセスのリスタートをまたいで持続しません。" + +#: ../../reference/commands/traffic_line.en.rst:125 +msgid "List all alarm events that have not been acknowledged (cleared)." +msgstr "承認 ( 消去 ) されていないすべてのアラームイベントを一覧表示します。" + +#: ../../reference/commands/traffic_line.en.rst:129 +msgid "" +"Clear (acknowledge) an alarm event. The arguments are \"all\" for all " +"current alarms, a specific alarm number (e.g. ''1''), or an alarm string " +"identifier (e.g. ''MGMT_ALARM_PROXY_CONFIG_ERROR'')." +msgstr "" +"アラームイベントを消去 ( 承認 ) します。引数は \"all\" で現在のすべての" +"アラーム、特定のアラーム番号 ( 例 ``1``) 、もしくはアラーム文字列識別子 " +"( 例 ''MGMT_ALARM_PROXY_CONFIG_ERROR'') です。" + +#: ../../reference/commands/traffic_line.en.rst:135 +msgid "" +"Show the current proxy server status, indicating if we're running or not." +msgstr "" +"プロキシーサーバーが実行中かどうかを示している現在の状態を表示します。" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_logcat.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_logcat.en.po new file mode 100644 index 00000000000..82ba2373cfe --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_logcat.en.po @@ -0,0 +1,116 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/traffic_logcat.en.rst:20 +msgid "traffic_logcat" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:23 +msgid "Synopsis" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:25 +msgid "" +":program:`traffic_logcat` [-o output-file | -a] [-CEhSVw2] [input-file ...]" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:31 +msgid "Description" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:33 +msgid "" +"To analyse a binary log file using standard tools, you must first convert " +"it to ASCII. :program:`traffic_logcat` does exactly that." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:37 +msgid "Options" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:41 +msgid "Specifies where the command output is directed." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:45 +msgid "" +"Automatically generates the output filename based on the input filename. If " +"the input is from stdin, then this option is ignored. For example::" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:51 +msgid "generates::" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:57 +msgid "Follows the file, like :manpage:`tail(1)` ``-f``" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:61 +msgid "" +"Attempts to transform the input to Netscape Common format, if possible." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:65 +msgid "" +"Attempts to transform the input to Netscape Extended format, if possible." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:69 +msgid "Attempts to transform the input to Squid format, if possible." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:73 +msgid "" +"Attempt to transform the input to Netscape Extended-2 format, if possible." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:81 +msgid "Print usage information and exit." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:85 +msgid "Print version information and exit." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:88 +msgid "" +"Use only one of the following options at any given time: ``-S``, ``-C``, ``-" +"E``, or ``-2``." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:90 +msgid "" +"If no input files are specified, then :program:`traffic_logcat` reads from " +"the standard input (``stdin``). If you do not specify an output file, then :" +"program:`traffic_logcat` writes to the standard output (``stdout``)." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:94 +msgid "" +"For example, to convert a binary log file to an ASCII file, you can use " +"the :program:`traffic_logcat` command with either of the following options " +"below::" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:101 +msgid "The binary log file is not modified by this command." +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:104 +msgid "See Also" +msgstr "" + +#: ../../reference/commands/traffic_logcat.en.rst:106 +msgid ":manpage:`tail(1)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_logstats.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_logstats.en.po new file mode 100644 index 00000000000..1685383db39 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_logstats.en.po @@ -0,0 +1,28 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/traffic_logstats.en.rst:20 +msgid "traffic_logstats" +msgstr "" + +#: ../../reference/commands/traffic_logstats.en.rst:25 +msgid "Description" +msgstr "" + +#: ../../reference/commands/traffic_logstats.en.rst:63 +msgid "Print usage information and exit." +msgstr "" + +#: ../../reference/commands/traffic_logstats.en.rst:67 +msgid "Print version information and exit." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_manager.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_manager.en.po new file mode 100644 index 00000000000..589a016db88 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_manager.en.po @@ -0,0 +1,24 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/traffic_manager.en.rst:20 +msgid "traffic_manager" +msgstr "" + +#: ../../reference/commands/traffic_manager.en.rst:25 +msgid "Description" +msgstr "" + +#: ../../reference/commands/traffic_manager.en.rst:43 +msgid "Environment" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_server.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_server.en.po new file mode 100644 index 00000000000..667c7e99e37 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_server.en.po @@ -0,0 +1,32 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/traffic_server.en.rst:20 +msgid "traffic_server" +msgstr "" + +#: ../../reference/commands/traffic_server.en.rst:25 +msgid "Description" +msgstr "" + +#: ../../reference/commands/traffic_server.en.rst:69 +msgid "Print usage information and exit." +msgstr "" + +#: ../../reference/commands/traffic_server.en.rst:73 +msgid "Print version information and exit." +msgstr "" + +#: ../../reference/commands/traffic_server.en.rst:76 +msgid "Environment" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_shell.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_shell.en.po new file mode 100644 index 00000000000..83b5fb30e88 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_shell.en.po @@ -0,0 +1,24 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/traffic_shell.en.rst:20 +msgid "traffic_shell" +msgstr "" + +#: ../../reference/commands/traffic_shell.en.rst:25 +msgid "Description" +msgstr "" + +#: ../../reference/commands/traffic_shell.en.rst:29 +msgid "Print version information and exit." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_top.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_top.en.po new file mode 100644 index 00000000000..b0e8765d78a --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_top.en.po @@ -0,0 +1,20 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.2\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-15 22:31+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/traffic_top.en.rst:20 +msgid "traffic_top" +msgstr "" + +#: ../../reference/commands/traffic_top.en.rst:25 +msgid "Description" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/tspush.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/tspush.en.po new file mode 100644 index 00000000000..2f7b1324ac0 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/tspush.en.po @@ -0,0 +1,24 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/tspush.en.rst:20 +msgid "tspush" +msgstr "" + +#: ../../reference/commands/tspush.en.rst:25 +msgid "Description" +msgstr "" + +#: ../../reference/commands/tspush.en.rst:35 +msgid "Print usage information and exit." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/tstop.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/tstop.en.po new file mode 100644 index 00000000000..48d0b043228 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/tstop.en.po @@ -0,0 +1,20 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/tstop.en.rst:20 +msgid "tstop" +msgstr "" + +#: ../../reference/commands/tstop.en.rst:25 +msgid "Description" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/commands/tsxs.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/tsxs.en.po new file mode 100644 index 00000000000..c69d6660f85 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/tsxs.en.po @@ -0,0 +1,24 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/commands/tsxs.en.rst:20 +msgid "tsxs" +msgstr "" + +#: ../../reference/commands/tsxs.en.rst:25 +msgid "Description" +msgstr "" + +#: ../../reference/commands/tsxs.en.rst:47 +msgid "Print usage information and exit." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/cache.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/cache.config.en.po new file mode 100644 index 00000000000..e5ffb245511 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/cache.config.en.po @@ -0,0 +1,294 @@ +# +msgid "" +msgstr "" +"Project-Id-Version: Apache Traffic Server 4.1\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2013-11-08 17:57+0900\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../reference/configuration/cache.config.en.rst:22 +msgid "cache.config" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:24 +msgid "" +"The :file:`cache.config` file defines how Traffic Server caches web " +"objects. You can add caching rules to specify the following: - Not to cache " +"objects from specific IP addresses - How long to pin particular objects in " +"the cache - How long to consider cached objects as fresh - Whether to " +"ignore no-cache directives from the server" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:32 +msgid "" +"After you modify the :file:`cache.config` file, navigate to the Traffic " +"Server bin directory; then run the :option:`traffic_line -x` command to " +"apply changes. When you apply the changes to a node in a cluster, Traffic " +"Server automatically applies the changes to all other nodes in the cluster." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:39 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:41 +msgid "" +"Each line in the :file:`cache.config` file contains a caching rule. Traffic " +"Server recognizes three space-delimited tags::" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:46 +msgid "" +"You can use more than one secondary specifier in a rule. However, you " +"cannot repeat a secondary specifier. The following list shows the possible " +"primary destinations with allowed values." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:54 +msgid "``dest_domain``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:53 +msgid "" +"A requested domain name. Traffic Server matches the domain name of the " +"destination from the URL in the request." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:60 +msgid "``dest_host``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:59 +msgid "" +"A requested hostname. Traffic Server matches the hostname of the " +"destination from the URL in the request." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:66 +msgid "``dest_ip``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:65 +msgid "" +"A requested IP address. Traffic Server matches the IP address of the " +"destination in the request." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:71 +msgid "``url_regex``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:71 +msgid "A regular expression (regex) to be found in a URL." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:73 +msgid "" +"The secondary specifiers are optional in the :file:`cache.config` file. The " +"following list shows possible secondary specifiers with allowed values." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:79 +msgid "``port``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:79 +msgid "A requested URL port." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:84 +msgid "``scheme``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:84 +msgid "A request URL protocol: http or https." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:89 +msgid "``prefix``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:89 +msgid "A prefix in the path part of a URL." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:94 +msgid "``suffix``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:94 +msgid "A file suffix in the URL." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:99 +msgid "``method``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:99 +msgid "A request URL method: get, put, post, trace." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:104 +msgid "``time``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:104 +msgid "A time range, such as 08:00-14:00." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:109 +msgid "``src_ip``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:109 +msgid "A client IP address." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:111 +msgid "The following list shows possible actions and their allowed values." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:128 +msgid "``action``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:117 +msgid "One of the following values:" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:119 +msgid "" +"``never-cache`` configures Traffic Server to never cache specified objects." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:121 +msgid "" +"``ignore-no-cache`` configures Traffic Server to ignore all ``Cache-" +"Control: no-cache`` headers." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:123 +msgid "" +"``ignore-client-no-cache`` configures Traffic Server to ignore ``Cache-" +"Control: no-cache`` headers from client requests." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:125 +msgid "" +"``ignore-server-no-cache`` configures Traffic Server to ignore ``Cache-" +"Control: no-cache`` headers from origin server responses." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:127 +msgid "" +"``cluster-cache-local`` configures the cluster cache to allow for this " +"content to be stored locally on every cluster node." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:158 +msgid "``pin-in-cache``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:154 +msgid "``d`` for days; for example: 2d" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:155 +msgid "``h`` for hours; for example: 10h" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:156 +msgid "``m`` for minutes; for example: 5m" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:157 +msgid "``s`` for seconds; for example: 20s" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:158 +msgid "mixed units; for example: 1h15m20s" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:164 +msgid "``revalidate``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:172 +msgid "``ttl-in-cache``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:175 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:177 +msgid "" +"The following example configures Traffic Server to revalidate ``gif`` and " +"``jpeg`` objects in the domain ``mydomain.com`` every 6 hours, and all " +"other objects in ``mydomain.com`` every hour. The rules are applied in the " +"order listed. ::" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:138 +msgid "``cache-responses-to-cookies``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:133 +msgid "" +"Change the style of caching with regard to cookies. This effectively " +"overrides the configuration parameter :ref:`proxy.config.http.cache." +"cache_responses_to_cookies` and uses the same values with the same " +"semantics. The override happens only for requests that match." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:143 +msgid "" +"Preserves objects in cache, preventing them from being overwritten. Does " +"not affect objects that are determined not to be cacheable. This setting " +"can have performance issues, and severely affect the cache. For instance, " +"if the primary destination matches all objects, once the cache is full, no " +"new objects could get written as nothing would be evicted. Similarly, for " +"each cache-miss, each object would incur extra checks to determine if the " +"object it would replace could be overwritten." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:151 +msgid "" +"The value is the amount of time you want to keep the object(s) in the " +"cache. The following time formats are allowed:" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:163 +msgid "" +"For objects that are in cache, overrides the the amount of time the " +"object(s) are to be considered fresh. Use the same time formats as ``pin-in-" +"cache``." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:169 +msgid "" +"Forces object(s) to become cached, as if they had a Cache-Control: max-age:" +"