1# Licensed to the Apache Software Foundation (ASF) under one
2# or more contributor license agreements.  See the NOTICE file
3# distributed with this work for additional information
4# regarding copyright ownership.  The ASF licenses this file
5# to you under the Apache License, Version 2.0 (the
6# "License"); you may not use this file except in compliance
7# with the License.  You may obtain a copy of the License at
8#
9#      http://www.apache.org/licenses/LICENSE-2.0
10#
11# Unless required by applicable law or agreed to in writing, software
12# distributed under the License is distributed on an "AS IS" BASIS,
13# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14# See the License for the specific language governing permissions and
15# limitations under the License.
16#
17#, fuzzy
18msgid ""
19msgstr ""
20"Project-Id-Version: Apache Traffic Server 6.2\n"
21"Report-Msgid-Bugs-To: \n"
22"POT-Creation-Date: 2016-01-02 21:32+0000\n"
23"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
24"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
25"Language-Team: LANGUAGE <LL@li.org>\n"
26"Language: ja_JP\n"
27"MIME-Version: 1.0\n"
28"Content-Type: text/plain; charset=utf-8\n"
29"Content-Transfer-Encoding: 8bit\n"
30"Generated-By: Babel 2.1.1\n"
31
32#: ../../admin-guide/configuration/hierachical-caching.en.rst:31
33msgid ""
34"A cache hierarchy consists of cache levels that communicate with each "
35"other. Traffic Server supports several types of cache hierarchies. All "
36"cache hierarchies recognize the concept of *parent* and *child*. A parent "
37"cache is a cache higher up in the hierarchy, to which Traffic Server can "
38"forward requests. A child cache is a cache for which Traffic Server is a "
39"parent."
40msgstr ""
41
42#: ../../admin-guide/configuration/hierachical-caching.en.rst:23
43msgid "Hierarchical Caching"
44msgstr ""
45
46#: ../../admin-guide/configuration/hierachical-caching.en.rst:43
47msgid ""
48"If a Traffic Server node cannot find a requested object in its cache, then "
49"it searches a parent cache (which itself can search other caches) before "
50"finally retrieving the object from the origin server. You can configure a "
51"Traffic Server node to use multiple parent caches so that if one parent is "
52"unavailable, the other parent caches will be checked in turn until either "
53"the request is serviced properly or no further parent caches are available "
54"and the origin server is contacted. This is called `Parent Failover`_. "
55"Traffic Server supports parent caching for both HTTP and HTTPS requests."
56msgstr ""
57
58#: ../../admin-guide/configuration/hierachical-caching.en.rst:74
59msgid ""
60"If the request is a cache miss on the parent, then the parent retrieves the "
61"content from the origin server (or from another cache, depending on the "
62"parent's configuration). The parent caches the content and then sends a "
63"copy to Traffic Server (its child), where it is cached and served to the "
64"client."
65msgstr ""
66
67#: ../../admin-guide/configuration/hierachical-caching.en.rst:41
68msgid "Parent Caching"
69msgstr ""
70
71#: ../../admin-guide/configuration/hierachical-caching.en.rst:38
72msgid "Traffic Server supports the following hierarchical caching options:"
73msgstr ""
74
75#: ../../admin-guide/configuration/hierachical-caching.en.rst:82
76msgid ""
77"If remap rules are required (:ts:cv:`proxy.config.reverse_proxy.enabled`), "
78"when a request comes in to a child node, its :file:`remap.config` is "
79"evaluated before parent selection. This means that the client request is "
80"translated according to the remap rule, and therefore, any parent selection "
81"should be made against the remapped host name. This is true regardless of "
82"pristine host headers (:ts:cv:`proxy.config.url_remap.pristine_host_hdr`) "
83"being enabled or not. The parent node will receive the translated request "
84"(and thus needs to be configured to accept it)."
85msgstr ""
86
87#: ../../admin-guide/configuration/hierachical-caching.en.rst:52
88msgid ""
89"If you do not want all requests to go to the parent cache, then simply "
90"configure Traffic Server to route certain requests (such as requests "
91"containing specific URLs) directly to the origin server. This may be "
92"achieved by setting parent proxy rules in :file:`parent.config`."
93msgstr ""
94
95#: ../../admin-guide/configuration/hierachical-caching.en.rst:132
96msgid "Configuring Traffic Server to Use a Parent Cache"
97msgstr ""
98
99#: ../../admin-guide/configuration/hierachical-caching.en.rst:92
100msgid "Example"
101msgstr "例"
102
103#: ../../admin-guide/configuration/hierachical-caching.en.rst:97
104msgid "If the child's :file:`remap.config` contains"
105msgstr ""
106
107#: ../../admin-guide/configuration/hierachical-caching.en.rst:80
108msgid "Interaction with Remap.config"
109msgstr ""
110
111#: ../../admin-guide/configuration/hierachical-caching.en.rst:115
112msgid "Parent Failover"
113msgstr ""
114
115#: ../../admin-guide/configuration/hierachical-caching.en.rst:72
116msgid "Parent caching"
117msgstr ""
118
119#: ../../admin-guide/configuration/hierachical-caching.en.rst:93
120msgid ""
121"The client makes a request to Traffic Server for http://example.com. The "
122"origin server for the request is http://origin.example.com; the parent node "
123"is ``parent1.example.com``, and the child node is configured as a reverse "
124"proxy."
125msgstr ""
126
127#: ../../admin-guide/configuration/hierachical-caching.en.rst:57
128msgid ""
129"The figure below illustrates a simple cache hierarchy with a Traffic Server "
130"node configured to use a parent cache. In the following scenario, a client "
131"sends a request to a Traffic Server node that is a child in the cache "
132"hierarchy (because it's configured to forward missed requests to a parent "
133"cache). The request is a cache miss, so Traffic Server then forwards the "
134"request to the parent cache where it is a cache hit. The parent sends a "
135"copy of the content to the Traffic Server, where it is cached and then "
136"served to the client. Future requests for this content can now be served "
137"directly from the Traffic Server cache (until the data is stale or expired)."
138msgstr ""
139
140#: ../../admin-guide/configuration/hierachical-caching.en.rst:164
141msgid ""
142"The following example configures Traffic Server to direct all missed "
143"requests with URLs beginning with ``http://host1`` to the parent cache "
144"``parent1``. If ``parent1`` cannot serve the requests, then requests are "
145"forwarded to ``parent2``. Because ``round-robin=true``, Traffic Server goes "
146"through the parent cache list in a round-robin based on client IP address.::"
147msgstr ""
148
149#: ../../admin-guide/configuration/hierachical-caching.en.rst:154
150msgid ""
151"Edit :file:`parent.config` to set parent proxy rules which will specify the "
152"parent cache to which you want missed requests to be forwarded."
153msgstr ""
154
155#: ../../admin-guide/configuration/hierachical-caching.en.rst:149
156msgid ""
157"Identify the parent cache you want to use to service missed requests. To "
158"use parent failover, you must identify more than one parent cache so that "
159"when a parent cache is unavailable, requests are sent to another parent "
160"cache."
161msgstr ""
162
163#: ../../admin-guide/configuration/hierachical-caching.en.rst:157
164msgid ""
165"The following example configures Traffic Server to route all requests "
166"containing the regular expression ``politics`` and the path ``/viewpoint`` "
167"directly to the origin server (bypassing any parent hierarchies): ::"
168msgstr ""
169
170#: ../../admin-guide/configuration/hierachical-caching.en.rst:99
171msgid "``map http://example.com http://origin.example.com``"
172msgstr ""
173
174#: ../../admin-guide/configuration/hierachical-caching.en.rst:134
175msgid ""
176"To configure Traffic Server to use one or more parent caches, you must "
177"perform the configuration adjustments detailed below."
178msgstr ""
179
180#: ../../admin-guide/configuration/hierachical-caching.en.rst:117
181msgid ""
182"Traffic Server supports use of several parent caches. This ensures that if "
183"one parent cache is not available, another parent cache can service client "
184"requests."
185msgstr ""
186
187#: ../../admin-guide/configuration/hierachical-caching.en.rst:29
188msgid "Understanding Cache Hierarchies"
189msgstr ""
190
191#: ../../admin-guide/configuration/hierachical-caching.en.rst:121
192msgid ""
193"When you configure your Traffic Server to use more than one parent cache, "
194"Traffic Server detects when a parent is not available and sends missed "
195"requests to another parent cache. If you specify more than two parent "
196"caches, then the order in which the parent caches are queried depends upon "
197"the parent proxy rules configured in the :file:`parent.config` "
198"configuration file. By default, the parent caches are queried in the order "
199"they are listed in the configuration file."
200msgstr ""
201
202#: ../../admin-guide/configuration/hierachical-caching.en.rst:103
203msgid ""
204"``dest_domain=origin.example.com method=get parent=\"parent1.example."
205"com:80`` )"
206msgstr ""
207
208#: ../../admin-guide/configuration/hierachical-caching.en.rst:110
209msgid ""
210"With this example, if parent1.example.com is down, the child node would "
211"automatically directly contact the ``origin.example.com`` on a cache miss."
212msgstr ""
213
214#: ../../admin-guide/configuration/hierachical-caching.en.rst:108
215msgid "``map http://origin.example.com http://origin.example.com``"
216msgstr ""
217
218#: ../../admin-guide/configuration/hierachical-caching.en.rst:105
219msgid ""
220"and parent cache (parent1.example.com) would need to have a :file:`remap."
221"config` line similar to"
222msgstr ""
223
224#: ../../admin-guide/configuration/hierachical-caching.en.rst:173
225#: ../../admin-guide/configuration/hierachical-caching.en.rst:221
226msgid ""
227"Run the command :option:`traffic_ctl config reload` to apply the "
228"configuration changes."
229msgstr ""
230
231#: ../../admin-guide/configuration/hierachical-caching.en.rst:139
232msgid ""
233"You need to configure the child cache only. Assuming the parent nodes are "
234"configured to serve the child's origin server, no additional configuration "
235"is needed for the nodes acting as Traffic Server parent caches."
236msgstr ""
237
238#: ../../admin-guide/configuration/hierachical-caching.en.rst:101
239msgid "with the child's :file:`parent.config` containing"
240msgstr ""
241