forked from apache/trafficserver
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
3ede19c
commit 5146724
Showing
30 changed files
with
12,298 additions
and
11,183 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
167 changes: 167 additions & 0 deletions
167
doc/locale/ja/LC_MESSAGES/admin-guide/configuration/transparent-proxy.en.po
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,167 @@ | ||
# SOME DESCRIPTIVE TITLE. | ||
# Copyright (C) 2015, dev@trafficserver.apache.org | ||
# This file is distributed under the same license as the Apache Traffic | ||
# Server package. | ||
# FIRST AUTHOR <EMAIL@ADDRESS>, 2016. | ||
# | ||
#, fuzzy | ||
msgid "" | ||
msgstr "" | ||
"Project-Id-Version: Apache Traffic Server 6.2\n" | ||
"Report-Msgid-Bugs-To: \n" | ||
"POT-Creation-Date: 2016-01-15 00:13+0900\n" | ||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||
"Language-Team: LANGUAGE <LL@li.org>\n" | ||
"MIME-Version: 1.0\n" | ||
"Content-Type: text/plain; charset=utf-8\n" | ||
"Content-Transfer-Encoding: 8bit\n" | ||
"Generated-By: Babel 2.2.0\n" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:4 | ||
msgid "Transparent Proxying" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/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 "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:35 | ||
msgid "" | ||
"The general network structure that will be used in this documentation is " | ||
"shown in the following figure." | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:42 | ||
msgid "ATS basic traffic flow of Transparent Proxy" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:44 | ||
msgid "" | ||
"There must be a gateway device through which all network traffic passes " | ||
"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 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 "" | ||
|
||
#: ../../../admin-guide/configuration/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 "" | ||
|
||
#: ../../../admin-guide/configuration/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 "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:65 | ||
msgid "" | ||
"In most situations these two types of transparency are combined, but that " | ||
"is not required. Traffic Server supports transparency independently on the " | ||
"two sides." | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:71 | ||
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 "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:77 | ||
msgid "TPROXY" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:78 | ||
msgid "POSIX capabilities" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:80 | ||
msgid "" | ||
"In addition the specialized routing will require using ``iptables`` and in " | ||
"some cases ``ebtables``." | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:83 | ||
msgid "" | ||
"Standard build procedures should work for transparency support but if not " | ||
"consult these :ref:`more detailed instructions <building-ats-for-" | ||
"transparency>`." | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:86 | ||
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 "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:95 | ||
msgid "" | ||
"In the first case use the attribute character (replacing the default 'X')" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:98 | ||
msgid "**Attribute** **Transparency Style** **Reverse Proxy**" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:101 | ||
msgid "=" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:101 | ||
msgid "Full transparency: either" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:104 | ||
msgid ">" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:104 | ||
msgid "Inbound (client) transparency: enabled" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:107 | ||
msgid "<" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:107 | ||
msgid "Outbound (origin server) transparency: either" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:109 | ||
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 "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:113 | ||
msgid "Some tested scenarios --" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:115 | ||
msgid ":doc:`transparent-proxy/bridge.en`" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:116 | ||
msgid ":doc:`transparent-proxy/router-inline.en`" | ||
msgstr "" | ||
|
||
#: ../../../admin-guide/configuration/transparent-proxy.en.rst:117 | ||
msgid ":doc:`transparent-proxy/wccp-configuration.en`" | ||
msgstr "" |
Oops, something went wrong.