From dac67d2264d1a6babc4a2efe7d3a6e8816d18ea6 Mon Sep 17 00:00:00 2001 From: Masaori Koshiba Date: Fri, 8 Nov 2013 18:00:20 +0900 Subject: [PATCH 01/67] Doc: Generate *.po files for Japanese translations --- .../ja/LC_MESSAGES/admin/cluster-howto.en.po | 228 ++ .../LC_MESSAGES/admin/configuring-cache.en.po | 569 ++++ .../admin/configuring-traffic-server.en.po | 92 + .../admin/event-logging-formats.en.po | 887 +++++ .../admin/explicit-proxy-caching.en.po | 108 + doc/locale/ja/LC_MESSAGES/admin/faqs.en.po | 544 +++ .../ja/LC_MESSAGES/admin/forward-proxy.en.po | 114 + .../LC_MESSAGES/admin/getting-started.en.po | 269 ++ .../admin/hierachical-caching.en.po | 169 + .../admin/http-proxy-caching.en.po | 1424 ++++++++ doc/locale/ja/LC_MESSAGES/admin/index.en.po | 444 +++ .../admin/monitoring-traffic.en.po | 142 + .../admin/reverse-proxy-http-redirects.en.po | 447 +++ .../LC_MESSAGES/admin/security-options.en.po | 380 +++ .../admin/traffic-server-error-messages.en.po | 709 ++++ .../LC_MESSAGES/admin/transparent-proxy.en.po | 161 + .../admin/transparent-proxy/bridge.en.po | 199 ++ .../admin/transparent-proxy/build.en.po | 69 + .../transparent-proxy/router-inline.en.po | 118 + .../wccp-configuration.en.po | 208 ++ .../LC_MESSAGES/admin/working-log-files.en.po | 1438 ++++++++ .../admin/working-log-files/log-formats.en.po | 530 +++ .../ja/LC_MESSAGES/arch/cache/cache-api.en.po | 48 + .../arch/cache/cache-appendix.en.po | 226 ++ .../LC_MESSAGES/arch/cache/cache-arch.en.po | 1686 +++++++++ .../arch/cache/cache-data-structures.en.po | 228 ++ .../ja/LC_MESSAGES/arch/cache/cache.en.po | 20 + .../LC_MESSAGES/arch/cache/tier-storage.en.po | 208 ++ doc/locale/ja/LC_MESSAGES/arch/index.en.po | 33 + .../LC_MESSAGES/arch/proposals/hostdb.en.po | 358 ++ doc/locale/ja/LC_MESSAGES/glossary.en.po | 114 + doc/locale/ja/LC_MESSAGES/index.po | 58 + .../ja/LC_MESSAGES/reference/api/TSAPI.en.po | 239 ++ .../LC_MESSAGES/reference/api/TSDebug.en.po | 83 + .../reference/api/TSHttpHookAdd.en.po | 93 + .../api/TSHttpOverridableConfig.en.po | 71 + .../reference/api/TSHttpParserCreate.en.po | 107 + .../reference/api/TSHttpTxnMilestoneGet.en.po | 244 ++ .../reference/api/TSIOBufferCreate.en.po | 109 + .../reference/api/TSInstallDirGet.en.po | 64 + .../reference/api/TSLifecycleHookAdd.en.po | 138 + .../reference/api/TSMBufferCreate.en.po | 84 + .../reference/api/TSPluginInit.en.po | 65 + .../LC_MESSAGES/reference/api/TSRemap.en.po | 97 + .../api/TSTrafficServerVersionGet.en.po | 51 + .../LC_MESSAGES/reference/api/TSTypes.en.po | 97 + .../reference/api/TSUrlCreate.en.po | 154 + .../LC_MESSAGES/reference/api/TSmalloc.en.po | 92 + .../ja/LC_MESSAGES/reference/api/index.en.po | 16 + .../reference/commands/index.en.po | 16 + .../reference/commands/traffic_cop.en.po | 69 + .../reference/commands/traffic_line.en.po | 150 + .../reference/commands/traffic_logcat.en.po | 116 + .../reference/commands/traffic_logstats.en.po | 28 + .../reference/commands/traffic_manager.en.po | 24 + .../reference/commands/traffic_server.en.po | 32 + .../reference/commands/traffic_shell.en.po | 24 + .../reference/commands/tspush.en.po | 24 + .../reference/commands/tstop.en.po | 20 + .../LC_MESSAGES/reference/commands/tsxs.en.po | 24 + .../configuration/cache.config.en.po | 254 ++ .../configuration/congestion.config.en.po | 304 ++ .../configuration/hosting.config.en.po | 110 + .../reference/configuration/icp.config.en.po | 163 + .../reference/configuration/index.en.po | 16 + .../configuration/ip_allow.config.en.po | 79 + .../configuration/log_hosts.config.en.po | 68 + .../configuration/logs_xml.config.en.po | 507 +++ .../configuration/parent.config.en.po | 259 ++ .../configuration/plugin.config.en.po | 46 + .../configuration/records.config.en.po | 3010 +++++++++++++++++ .../configuration/remap.config.en.po | 441 +++ .../configuration/splitdns.config.en.po | 180 + .../configuration/ssl_multicert.config.en.po | 154 + .../configuration/storage.config.en.po | 239 ++ .../configuration/update.config.en.po | 423 +++ .../configuration/volume.config.en.po | 74 + .../reference/plugins/balancer.en.po | 140 + .../reference/plugins/buffer_upload.en.po | 111 + .../reference/plugins/cacheurl.en.po | 80 + .../reference/plugins/combo_handler.en.po | 95 + .../reference/plugins/conf_remap.en.po | 348 ++ .../LC_MESSAGES/reference/plugins/esi.en.po | 20 + .../reference/plugins/geoip_acl.en.po | 101 + .../LC_MESSAGES/reference/plugins/gzip.en.po | 125 + .../reference/plugins/header_filter.en.po | 131 + .../LC_MESSAGES/reference/plugins/hipes.en.po | 111 + .../LC_MESSAGES/reference/plugins/index.en.po | 59 + .../reference/plugins/metafilter.en.po | 150 + .../reference/plugins/mysql_remap.en.po | 92 + .../reference/plugins/regex_remap.en.po | 132 + .../plugins/stale_while_revalidate.en.po | 20 + .../reference/plugins/stats_over_http.en.po | 51 + .../ja/LC_MESSAGES/sdk/actions-guide.en.po | 104 + .../sdk/actions-guide/hosts-lookup-api.en.po | 38 + .../LC_MESSAGES/sdk/adding-statistics.en.po | 72 + .../coupled-statistics.en.po | 115 + ...iewing-statistics-using-traffic-line.en.po | 35 + .../ja/LC_MESSAGES/sdk/continuations.en.po | 163 + .../how-to-activate-continuations.en.po | 41 + .../writing-handler-functions.en.po | 388 +++ .../ja/LC_MESSAGES/sdk/getting-started.en.po | 325 ++ .../sdk/getting-started/a-simple-plugin.en.po | 134 + .../getting-started/naming-conventions.en.po | 68 + ...in-registration-and-version-checking.en.po | 44 + .../sdk/header-based-plugin-examples.en.po | 93 + .../basic-authorization-plugin.en.po | 41 + ...-getting-a-handle-to-the-transaction.en.po | 22 + .../setting-a-transaction-hook.en.po | 59 + .../working-with-http-headers.en.po | 33 + .../blacklist-plugin.en.po | 84 + ...sing-the-transaction-being-processed.en.po | 53 + .../setting-a-global-hook.en.po | 38 + .../setting-up-a-transaction-hook.en.po | 72 + .../working-with-http-header-functions.en.po | 33 + .../how-to-create-trafficserver-plugins.en.po | 292 ++ .../roadmap-for-creating-plugins.en.po | 132 + .../ja/LC_MESSAGES/sdk/http-headers.en.po | 158 + ...-to-trafficserver-http-header-system.en.po | 47 + ...licate-mime-fields-are-not-coalesced.en.po | 33 + ...-belong-to-an-associated-mime-header.en.po | 55 + .../release-marshal-buffer-handles.en.po | 76 + .../sdk/http-headers/http-headers.en.po | 460 +++ .../sdk/http-headers/marshal-buffers.en.po | 99 + .../sdk/http-headers/mime-headers.en.po | 931 +++++ .../LC_MESSAGES/sdk/http-headers/urls.en.po | 214 ++ .../sdk/http-hooks-and-transactions.en.po | 94 + .../adding-hooks.en.po | 251 ++ .../http-alternate-selection.en.po | 137 + .../http-sessions.en.po | 75 + .../http-transactions.en.po | 171 + .../initiate-http-connection.en.po | 28 + .../intercepting-http-transactions.en.po | 32 + .../sdk/http-transformation-plugin.en.po | 184 + .../append-transform-plugin.en.po | 208 ++ ...-buffered-null-transformation-plugin.en.po | 177 + .../sample-null-transformation-plugin.en.po | 175 + doc/locale/ja/LC_MESSAGES/sdk/index.en.po | 55 + doc/locale/ja/LC_MESSAGES/sdk/io-guide.en.po | 284 ++ .../sdk/io-guide/guide-to-cache-api.en.po | 63 + .../io-guide/guide-to-cache-api/errors.en.po | 36 + .../io-guide/guide-to-cache-api/example.en.po | 70 + .../how-to-do-a-cache-remove.en.po | 35 + .../how-to-do-a-cache-write.en.po | 38 + .../LC_MESSAGES/sdk/io-guide/io-buffers.en.po | 61 + .../sdk/io-guide/net-vconnections.en.po | 37 + .../sdk/io-guide/transformations.en.po | 205 ++ .../ja/LC_MESSAGES/sdk/io-guide/vios.en.po | 105 + .../sdk/misc-interface-guide.en.po | 73 + .../memory-allocation.en.po | 68 + .../thread-functions.en.po | 54 + .../misc-interface-guide/tsfopen-family.en.po | 78 + .../ja/LC_MESSAGES/sdk/mutex-guide.en.po | 308 ++ .../sdk/new-protocol-plugins.en.po | 523 +++ .../sdk/plugin-configurations.en.po | 92 + .../LC_MESSAGES/sdk/plugin-management.en.po | 20 + .../guide-to-the-logging-api.en.po | 140 + ...rafficserver-settings-and-statistics.en.po | 78 + doc/locale/ja/LC_MESSAGES/sdk/preface.en.po | 43 + .../sdk/preface/how-to-use-this-book.en.po | 205 ++ .../preface/typographical-conventions.en.po | 54 + .../ja/LC_MESSAGES/sdk/remap-plugin.en.po | 97 + .../remap-plugin/example-query-remap.en.po | 92 + .../LC_MESSAGES/sdk/sample-source-code.en.po | 60 + .../sdk/troubleshooting-tips.en.po | 47 + .../debugging-memory-leaks.en.po | 30 + .../unable-to-debug-tags.en.po | 144 + .../unable-to-load-plugins.en.po | 50 + .../using-a-debugger.en.po | 40 + 169 files changed, 32021 insertions(+) create mode 100644 doc/locale/ja/LC_MESSAGES/admin/cluster-howto.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/configuring-cache.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/configuring-traffic-server.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/event-logging-formats.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/explicit-proxy-caching.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/faqs.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/forward-proxy.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/getting-started.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/hierachical-caching.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/http-proxy-caching.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/index.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/monitoring-traffic.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/reverse-proxy-http-redirects.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/security-options.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/traffic-server-error-messages.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/transparent-proxy.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/bridge.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/build.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/router-inline.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/wccp-configuration.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/arch/cache/cache-arch.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/arch/cache/cache-data-structures.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/arch/cache/cache.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/arch/cache/tier-storage.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/arch/index.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/arch/proposals/hostdb.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/glossary.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/index.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSAPI.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSDebug.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSHttpHookAdd.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSHttpOverridableConfig.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSHttpParserCreate.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSHttpTxnMilestoneGet.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSIOBufferCreate.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSInstallDirGet.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSLifecycleHookAdd.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSMBufferCreate.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSPluginInit.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSRemap.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSTrafficServerVersionGet.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSTypes.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSUrlCreate.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/TSmalloc.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/api/index.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/index.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/traffic_cop.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/traffic_line.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/traffic_logcat.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/traffic_logstats.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/traffic_manager.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/traffic_server.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/traffic_shell.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/tspush.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/tstop.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/commands/tsxs.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/cache.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/congestion.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/hosting.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/icp.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/index.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/ip_allow.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/log_hosts.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/logs_xml.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/parent.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/plugin.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/records.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/remap.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/splitdns.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/ssl_multicert.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/storage.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/update.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/configuration/volume.config.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/balancer.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/buffer_upload.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/cacheurl.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/combo_handler.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/conf_remap.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/esi.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/geoip_acl.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/gzip.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/header_filter.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/hipes.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/index.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/metafilter.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/mysql_remap.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/regex_remap.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/stale_while_revalidate.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/reference/plugins/stats_over_http.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/actions-guide.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/actions-guide/hosts-lookup-api.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/adding-statistics.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/adding-statistics/coupled-statistics.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/adding-statistics/viewing-statistics-using-traffic-line.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/continuations.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/continuations/how-to-activate-continuations.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/continuations/writing-handler-functions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/getting-started.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/getting-started/a-simple-plugin.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/getting-started/naming-conventions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/getting-started/plugin-registration-and-version-checking.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/basic-authorization-plugin.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/basic-authorization-plugin/implementing-the-handler-and-getting-a-handle-to-the-transaction.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/basic-authorization-plugin/setting-a-transaction-hook.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/basic-authorization-plugin/working-with-http-headers.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/blacklist-plugin.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/blacklist-plugin/accessing-the-transaction-being-processed.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/blacklist-plugin/setting-a-global-hook.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/blacklist-plugin/setting-up-a-transaction-hook.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/header-based-plugin-examples/blacklist-plugin/working-with-http-header-functions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/how-to-create-trafficserver-plugins.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/how-to-create-trafficserver-plugins/roadmap-for-creating-plugins.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers/guide-to-trafficserver-http-header-system.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers/guide-to-trafficserver-http-header-system/duplicate-mime-fields-are-not-coalesced.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers/guide-to-trafficserver-http-header-system/release-marshal-buffer-handles.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers/http-headers.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers/marshal-buffers.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers/mime-headers.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-headers/urls.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-hooks-and-transactions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-hooks-and-transactions/adding-hooks.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-hooks-and-transactions/http-alternate-selection.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-hooks-and-transactions/http-sessions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-hooks-and-transactions/http-transactions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-hooks-and-transactions/initiate-http-connection.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-hooks-and-transactions/intercepting-http-transactions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/append-transform-plugin.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-null-transformation-plugin.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/index.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/errors.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/example.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-remove.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-write.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/io-buffers.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/net-vconnections.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/transformations.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/io-guide/vios.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/memory-allocation.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/thread-functions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/tsfopen-family.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/mutex-guide.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/new-protocol-plugins.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/plugin-configurations.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/plugin-management.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/plugin-management/guide-to-the-logging-api.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/plugin-management/reading-trafficserver-settings-and-statistics.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/preface.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/preface/how-to-use-this-book.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/preface/typographical-conventions.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/remap-plugin.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/remap-plugin/example-query-remap.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/sample-source-code.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/troubleshooting-tips.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/troubleshooting-tips/debugging-memory-leaks.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/troubleshooting-tips/unable-to-debug-tags.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/troubleshooting-tips/unable-to-load-plugins.en.po create mode 100644 doc/locale/ja/LC_MESSAGES/sdk/troubleshooting-tips/using-a-debugger.en.po 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..11e9a85e08f --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/cluster-howto.en.po @@ -0,0 +1,228 @@ +# +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 "" + +#: ../../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 "" + +#: ../../admin/cluster-howto.en.rst:32 +msgid "Understanding Traffic Server Clusters" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/cluster-howto.en.rst:88 +msgid "Have same kernel, e.g.: 2.6.18-194.17.1.el5" +msgstr "" + +#: ../../admin/cluster-howto.en.rst:89 +msgid "The same architecture, e.g.: ``x86_64``" +msgstr "" + +#: ../../admin/cluster-howto.en.rst:91 +msgid "You have the same version of Traffic Server installed" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/cluster-howto.en.rst:99 +msgid "" +"setup the same cluster name, with :ts:cv:`proxy.config.proxy_name`, e.g. " +"MyCluster." +msgstr "" + +#: ../../admin/cluster-howto.en.rst:101 +msgid "" +"Set :ts:cv:`proxy.local.cluster.type` to ``1``, to enable cluster mode." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/cluster-howto.en.rst:153 +msgid "" +"with these tweaks, we can archive about 10gbps traffic for the internal " +"cluster transfer speed." +msgstr "" 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..97b09323e99 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/configuring-cache.en.po @@ -0,0 +1,569 @@ +# +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:60 +msgid "The RAM Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:62 +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:68 +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*). 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:73 +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:79 +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:93 +msgid "Changing the Size of the RAM Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:95 +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:102 +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:109 +msgid "To change the RAM cache size:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:111 +#: ../../admin/configuring-cache.en.rst:136 +#: ../../admin/configuring-cache.en.rst:149 +msgid "Stop Traffic Server." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:112 +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:116 +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:123 +msgid "Changing Cache Capacity" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:125 +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:130 +msgid "Increasing Cache Capacity" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:132 +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:137 +msgid "Add hardware, if necessary." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:138 +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:140 +#: ../../admin/configuring-cache.en.rst:153 +#: ../../admin/configuring-cache.en.rst:182 +msgid "Restart Traffic Server." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:143 +msgid "Reducing Cache Capacity" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:145 +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:150 +msgid "Remove hardware, if necessary." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:151 +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:155 +msgid "" +"In :file:`storage.config`, a formatted or raw disk must be at least 128 MB." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:160 +msgid "Partitioning the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:162 +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:169 +msgid "Creating Cache Partitions for Specific Protocols" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:171 +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:178 +msgid "To partition the cache according to protocol:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:180 +msgid "" +"Enter a line in the :file:`volume.config` file for each volume you want to " +"create" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:185 +msgid "Making Changes to Partition Sizes and Protocols" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:187 +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:191 +msgid "" +"You must stop Traffic Server before you change the cache volume size and " +"protocol assignment." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:193 +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:196 +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:198 +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:200 +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:205 +msgid "Partitioning the Cache According to Origin Server or Domain" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:207 +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:222 +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:228 +msgid "To partition the cache according to hostname and domain:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:230 +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:232 +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:236 +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:238 +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:243 +#: ../../admin/configuring-cache.en.rst:256 +msgid "" +"Run the command :option:`traffic_line -x` to apply the configuration " +"changes." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:247 +msgid "Configuring the Cache Object Size Limit" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:249 +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:253 +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:262 +msgid "Clearing the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:264 +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:269 +msgid "To clear the cache:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:271 +msgid "" +"Stop Traffic Server (refer to :ref:`Stopping Traffic Server `)" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:272 +msgid "Enter the following command to clear the cache: ::" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:276 +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:280 +msgid "" +"Restart Traffic Server (refer to :ref:`Starting Traffic Server `)." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:283 +msgid "Removing an Object From the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:285 +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:291 +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:310 +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:314 +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:321 +msgid "Inspecting the Cache" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:323 +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 ``@scr_ip`` option in :file:`remap.config`." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:330 +msgid "Accessing the Cache Inspector Utility" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:332 +msgid "To access the Cache Inspector utility, follow the steps below:" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:334 +msgid "Set :ts:cv:`proxy.config.http_ui_enabled` to ``1``." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:335 +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:342 +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:344 +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:349 +msgid "The Cache page opens." +msgstr "" + +#: ../../admin/configuring-cache.en.rst:352 +msgid "Using the Cache Page" +msgstr "" + +#: ../../admin/configuring-cache.en.rst:354 +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:357 +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:362 +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:364 +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:369 +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:372 +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:380 +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 "" 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..10e9108994f --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/configuring-traffic-server.en.po @@ -0,0 +1,92 @@ +# +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 "" + +#: ../../admin/configuring-traffic-server.en.rst:24 +msgid "Traffic Server provides several options for configuring the system." +msgstr "" + +#: ../../admin/configuring-traffic-server.en.rst:32 +msgid "Configure Traffic Server Using Traffic Line" +msgstr "" + +#: ../../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 "" + +#: ../../admin/configuring-traffic-server.en.rst:39 +msgid "View Configuration Options in Traffic Line" +msgstr "" + +#: ../../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 "" + +#: ../../admin/configuring-traffic-server.en.rst:49 +msgid "Change Configuration Options in Traffic Line" +msgstr "" + +#: ../../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 "" + +#: ../../admin/configuring-traffic-server.en.rst:61 +msgid "Configure Traffic Server Using Configuration Files" +msgstr "" + +#: ../../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 "" + +#: ../../admin/configuring-traffic-server.en.rst:71 +msgid "The following is a sample portion of the :file:`records.config` file:" +msgstr "" + +#: ../../admin/configuring-traffic-server.en.rst:78 +msgid "Sample records.config file" +msgstr "" + +#: ../../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 "" 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..d0b2e80e784 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/event-logging-formats.en.po @@ -0,0 +1,887 @@ +# +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/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 "" + +#: ../../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 "" + +#: ../../admin/event-logging-formats.en.rst:43 +msgid "``{HTTP header field name}cqh``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/event-logging-formats.en.rst:48 +msgid "``{HTTP header field name}pqh``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/event-logging-formats.en.rst:53 +msgid "``{HTTP header field name}psh``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/event-logging-formats.en.rst:58 +msgid "``{HTTP header field name}ssh``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/event-logging-formats.en.rst:62 +#: ../../admin/event-logging-formats.en.rst:329 +#: ../../admin/event-logging-formats.en.rst:344 +#: ../../admin/event-logging-formats.en.rst:361 +#: ../../admin/event-logging-formats.en.rst:387 +msgid "``caun``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:61 +msgid "" +"The client authenticated username; result of the RFC931/ident lookup of the " +"client username." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:67 +#: ../../admin/event-logging-formats.en.rst:402 +msgid "``cfsc``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/event-logging-formats.en.rst:70 +#: ../../admin/event-logging-formats.en.rst:324 +#: ../../admin/event-logging-formats.en.rst:343 +#: ../../admin/event-logging-formats.en.rst:360 +#: ../../admin/event-logging-formats.en.rst:386 +msgid "``chi``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:70 +msgid "The IP address of the client's host machine." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:73 +msgid "``chih``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:73 +msgid "The IP address of the client's host machine in hexadecimal." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:77 +#: ../../admin/event-logging-formats.en.rst:368 +#: ../../admin/event-logging-formats.en.rst:394 +msgid "``cqbl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:76 +msgid "" +"The client request transfer length; the body length in the client request to" +" Traffic Server (in bytes)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:81 +#: ../../admin/event-logging-formats.en.rst:370 +#: ../../admin/event-logging-formats.en.rst:396 +msgid "``cqhl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:80 +msgid "" +"The client request header length; the header length in the client request to" +" Traffic Server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:85 +#: ../../admin/event-logging-formats.en.rst:327 +msgid "``cqhm``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:84 +msgid "" +"The HTTP method in the client request to Traffic Server: ``GET``, ``POST``, " +"and so on (subset of ``cqtx``)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:88 +msgid "``cqhv``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:88 +msgid "The client request HTTP version." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:93 +msgid "``cqtd``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:91 +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 "" + +#: ../../admin/event-logging-formats.en.rst:97 +msgid "``cqtn``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:96 +msgid "" +"The client request timestamp; date and time of the client's request (in the " +"Netscape timestamp format)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:100 +msgid "``cqtq``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:100 +msgid "The client request timestamp, with millisecond resolution." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:105 +#: ../../admin/event-logging-formats.en.rst:322 +msgid "``cqts``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:103 +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 "" + +#: ../../admin/event-logging-formats.en.rst:111 +msgid "``cqtt``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:108 +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 "" + +#: ../../admin/event-logging-formats.en.rst:120 +msgid "``cqtx``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:114 +msgid "The full HTTP client request text, minus headers; for example, ::" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:118 +#: ../../admin/event-logging-formats.en.rst:126 +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 "" + +#: ../../admin/event-logging-formats.en.rst:129 +msgid "``cqu``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:123 +msgid "" +"The universal resource identifier (URI) of the request from client to " +"Traffic Server (subset of ``cqtx`` )." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:138 +#: ../../admin/event-logging-formats.en.rst:328 +msgid "``cquc``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:132 +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 "" + +#: ../../admin/event-logging-formats.en.rst:138 +msgid "See `cquuc`_." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:146 +msgid "``cqup``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:141 +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 "" + +#: ../../admin/event-logging-formats.en.rst:146 +msgid "See `cquup`_." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:149 +msgid "``cqus``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:149 +msgid "The client request URL scheme." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:155 +msgid "``cquuc``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:154 +msgid "" +"The client request unmapped URL canonical. This field records a URL before " +"it is remapped (reverse proxy mode)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:161 +msgid "``cquup``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:160 +msgid "" +"The client request unmapped URL path. This field records a URL path before " +"it is remapped (reverse proxy mode)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:167 +msgid "``cquuh``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:166 +msgid "" +"The client request unmapped URL host. This field records a URL's host before" +" it is remapped (reverse proxy mode)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:170 +msgid "``crat``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:170 +msgid "The Retry-After time in seconds, if specified by the origin server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:174 +#: ../../admin/event-logging-formats.en.rst:404 +#: ../../admin/event-logging-formats.en.rst:404 +msgid "``crc``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:173 +msgid "" +"The cache result code; specifies how the cache responded to the request " +"(``HIT``, ``MISS``, and so on)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:178 +msgid "``csscl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:177 +msgid "" +"The cached response length (in bytes) from origin server to Traffic Server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:182 +msgid "``csshl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:181 +msgid "" +"The cached header length in the origin server response to Traffic Server (in" +" bytes)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:185 +msgid "``csshv``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:185 +msgid "The cached server response HTTP version (1.0, 1.1, etc.)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:189 +msgid "``csssc``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:188 +msgid "" +"The cached HTTP response status code from origin server to Traffic Server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:192 +msgid "``cwr``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:192 +msgid "" +"The cache write result (``-``, ``WL_MISS``, ``INTR```, ``ERR`` or ``FIN``)" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:195 +msgid "``cwtr``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:195 +msgid "The cache write transform result" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:198 +msgid "``fsiz``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:198 +msgid "The size of the file (*n* bytes) as seen by the origin server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:203 +#: ../../admin/event-logging-formats.en.rst:403 +msgid "``pfsc``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:201 +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 "" + +#: ../../admin/event-logging-formats.en.rst:207 +msgid "``phn``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:206 +msgid "" +"The hostname of the Traffic Server that generated the log entry in collated " +"log files." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:211 +msgid "``phi``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:210 +msgid "" +"The IP of the Traffic Server that generated the log entry in collated log " +"files." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:215 +#: ../../admin/event-logging-formats.en.rst:401 +msgid "``phr``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:214 +msgid "" +"The proxy hierarchy route; the route Traffic Server used to retrieve the " +"object." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:219 +#: ../../admin/event-logging-formats.en.rst:369 +#: ../../admin/event-logging-formats.en.rst:395 +msgid "``pqbl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:218 +msgid "" +"The proxy request transfer length; the body length in Traffic Server's " +"request to the origin server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:223 +#: ../../admin/event-logging-formats.en.rst:372 +#: ../../admin/event-logging-formats.en.rst:398 +msgid "``pqhl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:222 +msgid "" +"The proxy request header length; the header length in Traffic Server's " +"request to the origin server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:227 +msgid "``pqsi``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:226 +msgid "" +"The proxy request server IP address (0 on cache hits and parent-ip for " +"requests to parent proxies)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:231 +msgid "``pqsn``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:230 +msgid "" +"The proxy request server name; the name of the server that fulfilled the " +"request." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:234 +#: ../../admin/event-logging-formats.en.rst:348 +#: ../../admin/event-logging-formats.en.rst:365 +#: ../../admin/event-logging-formats.en.rst:391 +msgid "``pscl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:234 +msgid "The length of the Traffic Server response to the client (in bytes)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:238 +#: ../../admin/event-logging-formats.en.rst:331 +msgid "``psct``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:237 +msgid "" +"The content type of the document from server response header: (for example, " +"``img/gif`` )." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:241 +#: ../../admin/event-logging-formats.en.rst:371 +#: ../../admin/event-logging-formats.en.rst:397 +msgid "``pshl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:241 +msgid "The header length in Traffic Server's response to the client." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:245 +#: ../../admin/event-logging-formats.en.rst:326 +msgid "``psql``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:244 +msgid "" +"The proxy response transfer length in Squid format (includes header and " +"content length)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:248 +#: ../../admin/event-logging-formats.en.rst:347 +#: ../../admin/event-logging-formats.en.rst:364 +#: ../../admin/event-logging-formats.en.rst:390 +msgid "``pssc``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:248 +msgid "The HTTP response status code from Traffic Server to the client." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:259 +msgid "``shi``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:251 +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 "" + +#: ../../admin/event-logging-formats.en.rst:255 +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 "" + +#: ../../admin/event-logging-formats.en.rst:262 +msgid "``shn``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:262 +msgid "The hostname of the origin server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:265 +#: ../../admin/event-logging-formats.en.rst:367 +#: ../../admin/event-logging-formats.en.rst:393 +msgid "``sscl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:265 +msgid "The response length (in bytes) from origin server to Traffic Server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:269 +#: ../../admin/event-logging-formats.en.rst:373 +#: ../../admin/event-logging-formats.en.rst:399 +msgid "``sshl``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:268 +msgid "" +"The header length in the origin server response to Traffic Server (in " +"bytes)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:272 +msgid "``sshv``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:272 +msgid "The server response HTTP version (1.0, 1.1, etc.)." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:275 +#: ../../admin/event-logging-formats.en.rst:366 +#: ../../admin/event-logging-formats.en.rst:392 +msgid "``sssc``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:275 +msgid "The HTTP response status code from origin server to Traffic Server." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:281 +#: ../../admin/event-logging-formats.en.rst:323 +msgid "``ttms``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:278 +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 "" + +#: ../../admin/event-logging-formats.en.rst:284 +msgid "``ttmsh``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:284 +msgid "Same as ``ttms`` but in hexadecimal." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:295 +msgid "``ttmsf``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:287 +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 "" + +#: ../../admin/event-logging-formats.en.rst:293 +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 "" + +#: ../../admin/event-logging-formats.en.rst:302 +#: ../../admin/event-logging-formats.en.rst:374 +#: ../../admin/event-logging-formats.en.rst:400 +msgid "``tts``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:298 +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 "" + +#: ../../admin/event-logging-formats.en.rst:307 +msgid "Logging Format Cross-Reference" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:309 +msgid "" +"The following sections illustrate the correspondence between Traffic Server " +"logging fields and standard logging fields for the Squid and Netscape " +"formats." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:314 +msgid "Squid Logging Formats" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:316 +msgid "" +"The following is a list of the Squid logging fields and the corresponding " +"logging field symbols." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:320 +msgid "Squid" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:320 +#: ../../admin/event-logging-formats.en.rst:341 +#: ../../admin/event-logging-formats.en.rst:358 +#: ../../admin/event-logging-formats.en.rst:384 +msgid "Field Symbols" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:322 +msgid "``time``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:323 +msgid "``elapsed``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:324 +msgid "``client``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:325 +msgid "``action/code``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:325 +msgid "``crc/pssc``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:326 +msgid "``size``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:327 +msgid "``method``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:328 +msgid "``url``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:329 +msgid "``ident``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:330 +msgid "``hierarchy/from``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:330 +msgid "``phr/pqsn``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:331 +msgid "``content``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:335 +msgid "Netscape Common Logging Formats" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:337 +msgid "" +"The following is a list of the Netscape Common logging fields and the " +"corresponding Traffic Server logging field symbols." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:341 +msgid "Netscape Common" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:343 +#: ../../admin/event-logging-formats.en.rst:360 +#: ../../admin/event-logging-formats.en.rst:386 +msgid "``host``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:344 +#: ../../admin/event-logging-formats.en.rst:361 +#: ../../admin/event-logging-formats.en.rst:387 +msgid "``usr``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:345 +#: ../../admin/event-logging-formats.en.rst:362 +#: ../../admin/event-logging-formats.en.rst:388 +msgid "``[time]``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:345 +#: ../../admin/event-logging-formats.en.rst:362 +#: ../../admin/event-logging-formats.en.rst:388 +msgid "``[cqtn]``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:346 +#: ../../admin/event-logging-formats.en.rst:363 +#: ../../admin/event-logging-formats.en.rst:389 +msgid "``\"req\"``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:346 +#: ../../admin/event-logging-formats.en.rst:363 +#: ../../admin/event-logging-formats.en.rst:389 +msgid "``\"cqtx\"``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:347 +#: ../../admin/event-logging-formats.en.rst:364 +#: ../../admin/event-logging-formats.en.rst:390 +msgid "``s1``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:348 +#: ../../admin/event-logging-formats.en.rst:365 +#: ../../admin/event-logging-formats.en.rst:391 +msgid "``c1``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:352 +msgid "Netscape Extended Logging Formats" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:354 +msgid "" +"The following table lists the Netscape Extended logging fields and the " +"corresponding Traffic Server logging field symbols." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:358 +msgid "Netscape Extended" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:366 +#: ../../admin/event-logging-formats.en.rst:392 +msgid "``s2``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:367 +#: ../../admin/event-logging-formats.en.rst:393 +msgid "``c2``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:368 +#: ../../admin/event-logging-formats.en.rst:394 +msgid "``b1``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:369 +#: ../../admin/event-logging-formats.en.rst:395 +msgid "``b2``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:370 +#: ../../admin/event-logging-formats.en.rst:396 +msgid "``h1``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:371 +#: ../../admin/event-logging-formats.en.rst:397 +msgid "``h2``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:372 +#: ../../admin/event-logging-formats.en.rst:398 +msgid "``h3``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:373 +#: ../../admin/event-logging-formats.en.rst:399 +msgid "``h4``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:374 +#: ../../admin/event-logging-formats.en.rst:400 +msgid "``xt``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:378 +msgid "Netscape Extended-2 Logging Formats" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:380 +msgid "" +"The following is a list of the Netscape Extended-2 logging fields and the " +"corresponding Traffic Server logging field symbols." +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:384 +msgid "Netscape Extended-2" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:401 +msgid "``route``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:402 +msgid "``pfs``" +msgstr "" + +#: ../../admin/event-logging-formats.en.rst:403 +msgid "``ss``" +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..5bb0eb459e2 --- /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..9d8647bdb43 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/faqs.en.po @@ -0,0 +1,544 @@ +# +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 "" + +#: ../../admin/faqs.en.rst:27 +msgid "FAQs" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:57 +msgid "" +"Can Traffic Server cache Java applets, JavaScript programs, or other " +"application files like VBScript?" +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:67 +msgid "" +"In Squid- and Netscape-format log files, what do the cache result codes " +"mean?" +msgstr "" + +#: ../../admin/faqs.en.rst:69 +msgid "" +"This is described in detail in the :ref:`log-formats-squid-format` " +"documentation." +msgstr "" + +#: ../../admin/faqs.en.rst:72 +msgid "What is recorded by the ``cqtx`` field in a custom log file?" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:91 +msgid "see :ts:cv:`proxy.config.hostdb.ttl_mode` for more info" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:105 +msgid "" +"Can Traffic Server run in forward proxy and reverse proxy modes at the same " +"time?" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:123 +msgid "How do I interpret the Via: header code?" +msgstr "" + +#: ../../admin/faqs.en.rst:125 +msgid "" +"Take a look at our `Via decoder Ring " +"`_." +msgstr "" + +#: ../../admin/faqs.en.rst:128 +msgid "Support for HTTP Expect: Header" +msgstr "" + +#: ../../admin/faqs.en.rst:130 +msgid "" +"Traffic Server currently does not handle request Expect: headers according " +"to the HTTP/1.1 spec." +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:141 +msgid "C (libcurl)::" +msgstr "" + +#: ../../admin/faqs.en.rst:147 +msgid "php::" +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:165 +msgid "You are unable to execute Traffic Line commands" +msgstr "" + +#: ../../admin/faqs.en.rst:167 +msgid "Traffic Line commands do not execute under the following conditions:" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:205 +msgid "Web browsers display an error document with a 'data missing' message" +msgstr "" + +#: ../../admin/faqs.en.rst:207 +msgid "A message similar to the following might display in web browsers: ::" +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:221 +msgid "Traffic Server does not resolve any websites" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:233 +msgid "" +"Check if the :manpage:`resolv.conf(5)` file contains valid IP addresses for " +"your DNS servers." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:246 +msgid "'Maximum document size exceeded' message in the system log file" +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:261 +msgid "'DrainIncomingChannel' message in the system log file" +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:279 +msgid "'No cop file' message in the system log file" +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:296 +msgid "command." +msgstr "" + +#: ../../admin/faqs.en.rst:300 +msgid "Warning in the system log file when manually editing vaddrs.config" +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:308 +msgid "" +"You can safely ignore this message; Traffic Server *does* apply your " +"configuration edits." +msgstr "" + +#: ../../admin/faqs.en.rst:312 +msgid "Traffic Server is running but no log files are created" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:332 +msgid "Traffic Server shows an error indicating too many network connections" +msgstr "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:343 +msgid "Connection throttle events can occur under the following conditions:" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/faqs.en.rst:372 +msgid "" +"Symptoms of extreme memory exhaustion include the following messages in the " +"system log files (``/var/log/messages``)::" +msgstr "" + +#: ../../admin/faqs.en.rst:381 +msgid "" +"To avoid memory exhaustion, add more RAM to the system or reduce the load on" +" Traffic Server." +msgstr "" + +#: ../../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 "" 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..64f2f50d140 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/forward-proxy.en.po @@ -0,0 +1,114 @@ +# +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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/forward-proxy.en.rst:52 +msgid "Configuration" +msgstr "" + +#: ../../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 "" + +#: ../../admin/forward-proxy.en.rst:57 +msgid ":ts:cv:`proxy.config.url_remap.remap_required` to ``0``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/forward-proxy.en.rst:67 +msgid ":ts:cv:`proxy.config.http.forward.proxy_auth_to_parent`" +msgstr "" + +#: ../../admin/forward-proxy.en.rst:68 +msgid ":ts:cv:`proxy.config.http.insert_squid_x_forwarded_for`" +msgstr "" + +#: ../../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 "" 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..c2256dede78 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/getting-started.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" + +#: ../../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 "" + +#: ../../admin/getting-started.en.rst:35 +msgid "A version is made of a version-triplet: ``MAJOR.MINOR.PATCH``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/getting-started.en.rst:61 +msgid "Building Traffic Server" +msgstr "" + +#: ../../admin/getting-started.en.rst:63 +msgid "" +"In order to build Traffic Server from source you will need the following " +"(development) packages:" +msgstr "" + +#: ../../admin/getting-started.en.rst:66 +msgid "pkgconfig" +msgstr "" + +#: ../../admin/getting-started.en.rst:67 +msgid "libtool" +msgstr "" + +#: ../../admin/getting-started.en.rst:68 +msgid "gcc (>= 4.3 or clang > 3.0)" +msgstr "" + +#: ../../admin/getting-started.en.rst:69 +msgid "make (GNU Make!)" +msgstr "" + +#: ../../admin/getting-started.en.rst:70 +msgid "openssl" +msgstr "" + +#: ../../admin/getting-started.en.rst:71 +msgid "tcl" +msgstr "" + +#: ../../admin/getting-started.en.rst:72 +msgid "expat" +msgstr "" + +#: ../../admin/getting-started.en.rst:73 +msgid "pcre" +msgstr "" + +#: ../../admin/getting-started.en.rst:74 +msgid "libcap" +msgstr "" + +#: ../../admin/getting-started.en.rst:75 +msgid "flex (for TPROXY)" +msgstr "" + +#: ../../admin/getting-started.en.rst:76 +msgid "hwloc" +msgstr "" + +#: ../../admin/getting-started.en.rst:77 +msgid "lua" +msgstr "" + +#: ../../admin/getting-started.en.rst:78 +msgid "curses" +msgstr "" + +#: ../../admin/getting-started.en.rst:79 +msgid "curl (both for tstop)" +msgstr "" + +#: ../../admin/getting-started.en.rst:81 +msgid "if you're building from a git clone, you'll also need" +msgstr "" + +#: ../../admin/getting-started.en.rst:83 +msgid "git" +msgstr "" + +#: ../../admin/getting-started.en.rst:84 +msgid "autoconf" +msgstr "" + +#: ../../admin/getting-started.en.rst:85 +msgid "automake" +msgstr "" + +#: ../../admin/getting-started.en.rst:87 +msgid "We will show-case a build from git::" +msgstr "" + +#: ../../admin/getting-started.en.rst:91 +msgid "Next, we ``cd trafficserver`` and run::" +msgstr "" + +#: ../../admin/getting-started.en.rst:95 +msgid "" +"This will generate a ``configure`` file from ``configure.ac``, so now we can" +" run that::" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/getting-started.en.rst:111 +msgid "" +"Most ``configure`` path-options accept a format of " +"``\"INCLUDE_PATH:LIBRARY_PATH\"``::" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/getting-started.en.rst:140 +msgid "Start Traffic Server" +msgstr "" + +#: ../../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 "" + +#: ../../admin/getting-started.en.rst:147 +msgid "To run the ``trafficserver start`` command, e.g.::" +msgstr "" + +#: ../../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 "" + +#: ../../admin/getting-started.en.rst:157 +msgid "Start Traffic Line" +msgstr "" + +#: ../../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 "" + +#: ../../admin/getting-started.en.rst:164 +msgid "Traffic Line commands take the following form::" +msgstr "" + +#: ../../admin/getting-started.en.rst:168 +msgid "For a list of :program:`traffic_line` commands, enter::" +msgstr "" + +#: ../../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 "" + +#: ../../admin/getting-started.en.rst:180 +msgid "Stop Traffic Server" +msgstr "" + +#: ../../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 "" 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..2b5bbd66516 --- /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: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 "" + +#: ../../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 "" 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..c65bfdd48fe --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/http-proxy-caching.en.po @@ -0,0 +1,1424 @@ +# +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/http-proxy-caching.en.rst:4 +msgid "HTTP Proxy Caching" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:44 +msgid "Traffic Server receives a client request for a web object." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:98 +msgid "HTTP Object Freshness" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:100 +msgid "" +"Traffic Server determines whether an HTTP object in the cache is fresh by:" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:103 +msgid "**Checking the** ``Expires`` **or** ``max-age`` **header**" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:110 +msgid "**Checking the** ``Last-Modified`` **/** ``Date`` **header**" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:134 +msgid "**Checking revalidate rules in the** :file:`cache.config` **file**" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:171 +msgid ":ts:cv:`proxy.config.http.cache.heuristic_max_lifetime`" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:188 +msgid "To configure Traffic Server to cache objects with specific headers" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:190 +msgid "" +"Change the value for :ts:cv:`proxy.config.http.cache.required_headers`." +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:198 +msgid "Cache-Control Headers" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:237 +msgid "Revalidating HTTP Objects" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:279 +msgid ":ts:cv:`proxy.config.http.cache.when_to_revalidate`" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:328 +msgid ":ts:cv:`proxy.config.update.retry_count`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:329 +msgid ":ts:cv:`proxy.config.update.retry_interval`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:330 +msgid ":ts:cv:`proxy.config.update.concurrent_updates`" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:349 +msgid "Make sure :ts:cv:`proxy.config.update.enabled` is set to 1." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:368 +msgid "Configuring Traffic Server for PUSH Requests" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:373 +msgid "To configure Traffic Server to accept ``PUSH`` requests" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:375 +msgid "Edit :file:`ip_allow.config` to allow ``PUSH``." +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:377 +msgid "" +"Edit the following variable in :file:`records.config`, enable the " +"push_method." +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:380 +msgid ":ts:cv:`proxy.config.http.push_method_enabled`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:386 +msgid "Understanding HTTP PUSH" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:429 +msgid ":ts:cv:`proxy.config.cache.permit.pinning`" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:448 +msgid "Caching HTTP Objects" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:460 +msgid "``Authorization``: header" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:462 +#: ../../admin/http-proxy-caching.en.rst:503 +msgid "``Cache-Control: no-store`` header" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:464 +msgid "``Cache-Control: no-cache`` header" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:469 +msgid "``Cookie``: header (for text objects)" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:478 +msgid "Configuring Traffic Server to Ignore Client no-cache Headers" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:488 +msgid "To configure Traffic Server to ignore client ``no-cache`` headers" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:492 +msgid ":ts:cv:`proxy.config.http.cache.ignore_client_no_cache`" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:504 +msgid "``Cache-Control: private`` header" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:505 +msgid "``WWW-Authenticate``: header" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:510 +msgid "``Set-Cookie``: header" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:511 +msgid "``Cache-Control: no-cache`` headers" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:516 +msgid "``Expires``: header with value of 0 (zero) or a past date" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:519 +msgid "Configuring Traffic Server to Ignore Server no-cache Headers" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:529 +msgid "To configure Traffic Server to ignore server ``no-cache`` headers" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:531 +msgid "" +"Edit the variable :ts:cv:`proxy.config.http.cache.ignore_server_no_cache`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:537 +msgid "Configuring Traffic Server to Ignore WWW-Authenticate Headers" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:552 +msgid "" +"To configure Traffic Server to ignore server ``WWW-Authenticate`` headers" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:555 +msgid "" +"Edit the variable :ts:cv:`proxy.config.http.cache.ignore_authentication`" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:567 +msgid "You can configure Traffic Server to do the following:" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:569 +msgid "" +"*Not* cache any HTTP objects (refer to `Disabling HTTP Object Caching`_)." +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:573 +msgid "" +"Cache objects served in response to the ``Cookie:`` header (refer to " +"`Caching Cookied Objects`_." +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:575 +msgid "Observe ``never-cache`` rules in the :file:`cache.config` file." +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:578 +msgid "Disabling HTTP Object Caching" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:586 +msgid "To disable HTTP object caching manually" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:588 +msgid "Set the variable :ts:cv:`proxy.config.http.enabled` to ``0``." +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:603 +msgid "" +"To configure Traffic Server's cache behaviour in regard to dynamic content" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:608 +msgid ":ts:cv:`proxy.config.http.cache.cache_urls_that_look_dynamic`" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:625 +msgid "You can reconfigure Traffic Server to:" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:633 +msgid "" +"Edit the variable " +":ts:cv:`proxy.config.http.cache.cache_responses_to_cookies`" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:656 +msgid "Caching HTTP Alternates" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:670 +msgid "Configuring How Traffic Server Caches Alternates" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:672 +msgid "" +"To configure how Traffic Server caches alternates, follow the steps below" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:677 +msgid ":ts:cv:`proxy.config.http.cache.enable_default_vary_headers`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:678 +msgid ":ts:cv:`proxy.config.http.cache.vary_default_text`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:679 +msgid ":ts:cv:`proxy.config.http.cache.vary_default_images`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:680 +msgid ":ts:cv:`proxy.config.http.cache.vary_default_other`" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:726 +msgid "Create rules in the :file:`congestion.config` file to specify:" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:727 +msgid "which origin servers Traffic Server tracks for congestion" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:728 +msgid "" +"the timeouts Traffic Server uses, depending on whether a server is congested" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:730 +msgid "" +"the page Traffic Server sends to the client when a server becomes congested" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:732 +msgid "" +"if Traffic Server tracks the origin servers per IP address or per hostname" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:769 +msgid "`TS_CONFIG_HTTP_FLOW_CONTROL_ENABLED`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:770 +msgid "Set high water" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:770 +msgid ":ts:cv:`proxy.config.http.flow_control.high_water`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:770 +msgid "`TS_CONFIG_HTTP_FLOW_CONTROL_HIGH_WATER`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:771 +msgid "Set low water" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:771 +msgid ":ts:cv:`proxy.config.http.flow_control.low_water`" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:771 +msgid "`TS_CONFIG_HTTP_FLOW_CONTROL_LOW_WATER`" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:782 +msgid "Reducing Origin Server Requests (Avoiding the Thundering Herd)" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:789 +msgid "Read While Writer" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:792 +msgid "The configurations necessary to enable this in ATS are:" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:794 +msgid "CONFIG :ts:cv:`proxy.config.cache.enable_read_while_writer` ``INT 1``" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:795 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.background_fill_active_timeout` ``INT 0``" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:796 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.background_fill_completed_threshold` " +"``FLOAT 0.000000``" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:797 +msgid "CONFIG :ts:cv:`proxy.config.cache.max_doc_size` ``INT 0``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:812 +msgid "Fuzzy Revalidation" +msgstr "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:815 +msgid "CONFIG :ts:cv:`proxy.config.http.cache.fuzz.time` ``INT 240``" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:816 +msgid "CONFIG :ts:cv:`proxy.config.http.cache.fuzz.min_time` ``INT 0``" +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:817 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.cache.fuzz.probability` ``FLOAT 0.005``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:827 +msgid "" +"These configurations are similar to Squid's refresh_stale_hit configuration " +"option." +msgstr "" + +#: ../../admin/http-proxy-caching.en.rst:831 +msgid "Open Read Retry Timeout" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/http-proxy-caching.en.rst:844 +msgid "" +"CONFIG :ts:cv:`proxy.config.http.cache.open_read_retry_time` ``INT 10``" +msgstr "" + +#: ../../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 "" 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..62cb3bfbc12 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/index.en.po @@ -0,0 +1,444 @@ +# +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/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 "" + +#: ../../admin/index.en.rst:27 +msgid "This chapter discusses how:" +msgstr "" + +#: ../../admin/index.en.rst:29 +msgid "Contents:" +msgstr "" + +#: ../../admin/index.en.rst:53 +msgid "What Is Apache Traffic Server?" +msgstr "" + +#: ../../admin/index.en.rst:55 +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 "" + +#: ../../admin/index.en.rst:63 +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 "" + +#: ../../admin/index.en.rst:72 +msgid "Traffic Server Deployment Options" +msgstr "" + +#: ../../admin/index.en.rst:74 +msgid "" +"To best suit your needs, Traffic Server can be deployed in several ways:" +msgstr "" + +#: ../../admin/index.en.rst:76 +msgid "As a web proxy cache" +msgstr "" + +#: ../../admin/index.en.rst:77 +msgid "As a reverse proxy" +msgstr "" + +#: ../../admin/index.en.rst:78 +msgid "In a cache hierarchy" +msgstr "" + +#: ../../admin/index.en.rst:80 +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 "" + +#: ../../admin/index.en.rst:86 +msgid "Traffic Server as a Web Proxy Cache" +msgstr "" + +#: ../../admin/index.en.rst:88 +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 "" + +#: ../../admin/index.en.rst:96 +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 "" + +#: ../../admin/index.en.rst:103 +msgid "Traffic Server as a Reverse Proxy" +msgstr "" + +#: ../../admin/index.en.rst:105 +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 "" + +#: ../../admin/index.en.rst:112 +msgid "Traffic Server in a Cache Hierarchy" +msgstr "" + +#: ../../admin/index.en.rst:114 +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 "" + +#: ../../admin/index.en.rst:121 +msgid "" +"Traffic Server supports ICP (Internet Cache Protocol) peering. Hierarchical " +"caching is described in more detail in :ref:`hierarchical-caching`." +msgstr "" + +#: ../../admin/index.en.rst:125 +msgid "Deployment Limitations" +msgstr "" + +#: ../../admin/index.en.rst:127 +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 "" + +#: ../../admin/index.en.rst:131 +msgid "" +"Load Balancing - note that there is an experimental plugin for this: :ref" +":`balancer-plugin`." +msgstr "" + +#: ../../admin/index.en.rst:134 +msgid "Traffic Server Components" +msgstr "" + +#: ../../admin/index.en.rst:136 +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 "" + +#: ../../admin/index.en.rst:141 +msgid "The Traffic Server Cache" +msgstr "" + +#: ../../admin/index.en.rst:143 +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 "" + +#: ../../admin/index.en.rst:152 +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 "" + +#: ../../admin/index.en.rst:161 +msgid "The RAM Cache" +msgstr "" + +#: ../../admin/index.en.rst:163 +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 "" + +#: ../../admin/index.en.rst:170 +msgid "The Host Database" +msgstr "" + +#: ../../admin/index.en.rst:172 +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 "" + +#: ../../admin/index.en.rst:178 +msgid "DNS information (for fast conversion of hostnames to IP addresses)" +msgstr "" + +#: ../../admin/index.en.rst:179 +msgid "" +"The HTTP version of each host (so advanced protocol features can be used " +"with hosts running modern servers)" +msgstr "" + +#: ../../admin/index.en.rst:181 +msgid "" +"Host reliability and availability information (so users will not wait for " +"servers that are not running)" +msgstr "" + +#: ../../admin/index.en.rst:185 +msgid "The DNS Resolver" +msgstr "" + +#: ../../admin/index.en.rst:187 +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 "" + +#: ../../admin/index.en.rst:195 +msgid "Traffic Server Processes" +msgstr "" + +#: ../../admin/index.en.rst:197 +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 "" + +#: ../../admin/index.en.rst:201 +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 "" + +#: ../../admin/index.en.rst:206 +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 "" + +#: ../../admin/index.en.rst:213 +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 "" + +#: ../../admin/index.en.rst:221 +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 "" + +#: ../../admin/index.en.rst:230 +msgid "The figure below illustrates the three Traffic Server processes." +msgstr "" + +#: ../../admin/index.en.rst:236 +msgid "Illustration of the three Traffic Server Processes" +msgstr "" + +#: ../../admin/index.en.rst:239 +msgid "Administration Tools" +msgstr "" + +#: ../../admin/index.en.rst:241 +msgid "Traffic Server offers the following administration options:" +msgstr "" + +#: ../../admin/index.en.rst:243 +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 "" + +#: ../../admin/index.en.rst:248 +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 "" + +#: ../../admin/index.en.rst:251 +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 "" + +#: ../../admin/index.en.rst:255 +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 "" + +#: ../../admin/index.en.rst:260 +msgid "Traffic Analysis Options" +msgstr "" + +#: ../../admin/index.en.rst:262 +msgid "" +"Traffic Server provides several options for network traffic analysis and " +"monitoring:" +msgstr "" + +#: ../../admin/index.en.rst:265 +msgid "" +"Traffic Line and Traffic Shell enable you to collect and process statistics " +"obtained from network traffic information." +msgstr "" + +#: ../../admin/index.en.rst:268 +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 "" + +#: ../../admin/index.en.rst:277 +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 "" + +#: ../../admin/index.en.rst:283 +msgid "" +"Traffic analysis options are described in more detail in :ref:`monitoring-" +"traffic`." +msgstr "" + +#: ../../admin/index.en.rst:285 +msgid "" +"Traffic Server logging options are described in :ref:`working-with-log-" +"files`." +msgstr "" + +#: ../../admin/index.en.rst:288 +msgid "Traffic Server Security Options" +msgstr "" + +#: ../../admin/index.en.rst:290 +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 "" + +#: ../../admin/index.en.rst:295 +msgid "Control client access to the Traffic Server proxy cache." +msgstr "" + +#: ../../admin/index.en.rst:296 +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 "" + +#: ../../admin/index.en.rst:302 +msgid "" +"Configure Traffic Server to verify that clients are authenticated before " +"they can access content from the Traffic Server cache." +msgstr "" + +#: ../../admin/index.en.rst:304 +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 "" + +#: ../../admin/index.en.rst:307 +msgid "Control access via SSL (Secure Sockets Layer)." +msgstr "" + +#: ../../admin/index.en.rst:309 +msgid "" +"Traffic Server security options are described in more detail in :ref" +":`security-options`." +msgstr "" 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..1f1eacd60c0 --- /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/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..f8e24bb658d --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/reverse-proxy-http-redirects.en.po @@ -0,0 +1,447 @@ +# +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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:55 +msgid "You can use Traffic Server in reverse proxy mode to:" +msgstr "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:77 +msgid "Traffic Server as reverse proxy for a pair of origin servers" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:125 +msgid "HTTP Reverse Proxy" +msgstr "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:135 +msgid "HTTP reverse proxy" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:152 +msgid "To configure HTTP reverse proxy, you must perform the following tasks:" +msgstr "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:160 +msgid "" +"Enable the reverse proxy option (refer to `Enabling HTTP Reverse Proxy`_)." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:182 +msgid "Using Mapping Rules for HTTP Requests" +msgstr "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:184 +msgid "Traffic Server uses two types of mapping rules for HTTP reverse proxy." +msgstr "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:198 +msgid "The scheme of both URLs must be the same" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:246 +msgid "Creating Mapping Rules for HTTP Requests" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:255 +msgid "Enabling HTTP Reverse Proxy" +msgstr "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:257 +msgid "To enable HTTP reverse proxy, follow the steps below." +msgstr "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:259 +msgid "Edit the following variable in :file:`records.config`" +msgstr "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:261 +msgid ":ts:cv:`proxy.config.reverse_proxy.enabled`" +msgstr "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:267 +msgid "Setting Optional HTTP Reverse Proxy Options" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/reverse-proxy-http-redirects.en.rst:286 +msgid "Redirecting HTTP Requests" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" 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..2289b309b3a --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/security-options.en.po @@ -0,0 +1,380 @@ +# +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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:41 +msgid "Configuring DNS Server Selection (Split DNS)" +msgstr "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:51 +msgid "To configure Split DNS, you must do the following:" +msgstr "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:56 +msgid "Enable the **Split DNS** option." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:69 +msgid "Using SSL Termination" +msgstr "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:75 +msgid "" +"The following sections describe how to enable and configure the SSL " +"termination option." +msgstr "" + +#: ../../admin/security-options.en.rst:78 +msgid "" +"Enable and configure SSL termination for client/Traffic Server connections: " +":ref:`client-and-traffic-server-connections`" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:89 +msgid "Client and Traffic Server Connections" +msgstr "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:100 +msgid "Client and Traffic Server communication using SSL termination" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:117 +#: ../../admin/security-options.en.rst:194 +msgid "Configure SSL termination options:" +msgstr "" + +#: ../../admin/security-options.en.rst:119 +msgid "" +"Set the port number used for SSL communication using " +":ts:cv:`proxy.config.http.server_ports`." +msgstr "" + +#: ../../admin/security-options.en.rst:120 +msgid "" +"Edit :file:`ssl_multicert.config` to specify the filename and location of " +"the SSL certificates and provate keys." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:139 +#: ../../admin/security-options.en.rst:217 +msgid ":ts:cv:`proxy.config.http.server_ports`" +msgstr "" + +#: ../../admin/security-options.en.rst:140 +msgid ":ts:cv:`proxy.config.ssl.client.certification_level`" +msgstr "" + +#: ../../admin/security-options.en.rst:141 +msgid ":ts:cv:`proxy.config.ssl.server.cert.path`" +msgstr "" + +#: ../../admin/security-options.en.rst:142 +msgid ":ts:cv:`proxy.config.ssl.server.private_key.path`" +msgstr "" + +#: ../../admin/security-options.en.rst:143 +msgid ":ts:cv:`proxy.config.ssl.CA.cert.path`" +msgstr "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:155 +msgid "Traffic Server and Origin Server Connections" +msgstr "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:165 +msgid "Traffic Server and origin server communication using SSL termination" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:195 +msgid "Enable the SSL termination option." +msgstr "" + +#: ../../admin/security-options.en.rst:197 +msgid "Set the port number used for SSL communication." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/security-options.en.rst:216 +msgid ":ts:cv:`proxy.config.ssl.auth.enabled`" +msgstr "" + +#: ../../admin/security-options.en.rst:218 +msgid ":ts:cv:`proxy.config.ssl.client.verify.server`" +msgstr "" + +#: ../../admin/security-options.en.rst:219 +msgid ":ts:cv:`proxy.config.ssl.client.cert.filename`" +msgstr "" + +#: ../../admin/security-options.en.rst:220 +msgid ":ts:cv:`proxy.config.ssl.client.cert.path`" +msgstr "" + +#: ../../admin/security-options.en.rst:221 +msgid ":ts:cv:`proxy.config.ssl.client.private_key.filename`" +msgstr "" + +#: ../../admin/security-options.en.rst:222 +msgid ":ts:cv:`proxy.config.ssl.client.private_key.path`" +msgstr "" + +#: ../../admin/security-options.en.rst:223 +msgid ":ts:cv:`proxy.config.ssl.client.CA.cert.filename`" +msgstr "" + +#: ../../admin/security-options.en.rst:224 +msgid ":ts:cv:`proxy.config.ssl.client.CA.cert.path`" +msgstr "" 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..3da00b21eb7 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/traffic-server-error-messages.en.po @@ -0,0 +1,709 @@ +# +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 "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:38 +msgid "``Accept port is not between 1 and 65535. Please check configuration``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:43 +msgid "``Self loop is detected in parent proxy configuration``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:46 +msgid "Traffic Server Warnings" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:49 +msgid "`` error: error_number``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:59 +msgid "``Could not rename log to ``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:72 +msgid "``Missing field for field marker``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:84 +msgid "``Too many errors accessing disk : declaring disk bad``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:89 +msgid "``No cache disks specified in storage.config file: cache disabled``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:92 +msgid "Traffic Server Alarm Messages" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:96 +msgid "``[Rollback::Rollback] Config file is read-only: ``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:100 +msgid "" +"``[Rollback::Rollback] Unable to read or write config file ``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:104 +msgid "``[Traffic Manager] Configuration File Update Failed: ``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:108 +msgid "``[Traffic Manager] Mgmt <==>Proxy conn. closed``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:107 +msgid "" +"An informational message to inform you that the :program:`traffic_server` " +"process is down." +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:114 +msgid "``Access logging suspended - configured space allocation exhausted.``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:128 +msgid "``Traffic Server could not open logfile ``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:140 +msgid "HTML Messages Sent to Clients" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:155 +msgid "``Access Denied``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:153 +msgid "" +"``403`` You are not allowed to access the document at location ``URL``. " +"``access#denied``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:160 +msgid "``Cache Read Error``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:158 +msgid "" +"``500`` Error reading from cache; please retry request. ``cache#read_error``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:165 +msgid "``Connection Timed Out``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:163 +msgid "" +"``504`` Too much time has elapsed since the server has sent data. " +"``timeout#inactivity``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:170 +msgid "``Content Length Required``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:175 +msgid "``Cycle Detected``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:180 +msgid "``Forbidden``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:190 +#: ../../admin/traffic-server-error-messages.en.rst:198 +msgid "``Host Header Required``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:204 +msgid "``HTTP Version Not Supported``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:209 +msgid "``Invalid HTTP Request``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:207 +msgid "" +"``400`` Could not process this ```` HTTP method request for " +"``URL``. ``request#syntax_error``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:214 +msgid "``Invalid HTTP Response``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:219 +msgid "``Malformed Server Response``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:224 +msgid "``Malformed Server Response Status``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:229 +msgid "``Maximum Transaction Time exceeded``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:227 +msgid "" +"``504`` Too much time has elapsed while transmitting document ``URL``. " +"``timeout#activity``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:234 +msgid "``No Response Header From Server``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:240 +msgid "``Not Cached``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:246 +msgid "``Not Found on Accelerator``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:251 +msgid "``NULL``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:256 +msgid "``Proxy Authentication Required``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:254 +msgid "" +"``407`` Please log in with username and password. " +"``access#proxy_auth_required``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:261 +msgid "``Server Hangup``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:259 +msgid "" +"``502`` The server ```` closed the connection before the " +"transaction was completed. ``connect#hangup``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:266 +msgid "``Temporarily Moved``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:271 +msgid "``Transcoding Not Available``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:276 +msgid "``Tunnel Connection Failed``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:274 +msgid "" +"``502`` Could not connect to the server ````. " +"``connect#failed_connect``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:281 +msgid "``Unknown Error``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:289 +msgid "``Unknown Host``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:296 +msgid "``Unsupported URL Scheme``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/traffic-server-error-messages.en.rst:301 +msgid "Standard HTTP Response Messages" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:303 +msgid "" +"The following standard HTTP response messages are provided for your " +"information." +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:307 +msgid "``200``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:307 +msgid "OK" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:310 +msgid "``202``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:310 +msgid "Accepted" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:313 +msgid "``204``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:313 +msgid "No Content" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:316 +msgid "``206``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:316 +msgid "Partial Content" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:319 +msgid "``300``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:319 +msgid "Multiple Choices" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:322 +msgid "``301``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:322 +msgid "Moved Permanently" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:325 +msgid "``302``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:325 +msgid "Found" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:328 +msgid "``303``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:328 +msgid "See Other" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:331 +msgid "``304``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:331 +msgid "Not Modified" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:334 +msgid "``400``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:334 +msgid "Bad Request" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:337 +msgid "``401``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:337 +msgid "Unauthorized; retry" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:340 +msgid "``403``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:340 +msgid "Forbidden" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:343 +msgid "``404``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:343 +msgid "Not Found" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:346 +msgid "``405``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:346 +msgid "Method Not Allowed" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:349 +msgid "``406``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:349 +msgid "Not acceptable" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:352 +msgid "``408``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:352 +msgid "Request Timeout" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:355 +msgid "``500``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:355 +msgid "Internal server error" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:358 +msgid "``501``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:358 +msgid "Not Implemented" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:361 +msgid "``502``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:361 +msgid "Bad Gateway" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:364 +msgid "``504``" +msgstr "" + +#: ../../admin/traffic-server-error-messages.en.rst:364 +msgid "Gateway Timeout" +msgstr "" 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..d2db9fd07e3 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy.en.po @@ -0,0 +1,161 @@ +# +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:33 +msgid "" +"Transparent Proxying is the ability of a proxy (such as ATS) to intercept " +"connections between clients and servers without being visible." +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:36 +msgid "" +"The general network structure that will be used in this documentation looks " +"like this --" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:43 +msgid "ATS basic traffic flow of Transparent Proxy" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:45 +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 "" + +#: ../../admin/transparent-proxy.en.rst:54 +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/transparent-proxy.en.rst:59 +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/transparent-proxy.en.rst:66 +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: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/transparent-proxy.en.rst:77 +msgid "TPROXY" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:78 +msgid "POSIX capabilities" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:80 +msgid "" +"In addition the specialized routing will require using ``iptables`` and in " +"some cases ``ebtables``." +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:83 +msgid "" +"Standard build procedures should work for transparency support but if not " +"consult these :ref:`more detailed instructions `" +msgstr "" + +#: ../../admin/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/transparent-proxy.en.rst:91 +msgid "" +"In the first case use the attribute character (replacing the default 'X')" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:94 +msgid "**Attribute** **Transparency Style** **Reverse Proxy**" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:97 +msgid "``=``" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:97 +msgid "Full transparency: either" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:100 +msgid "``>``" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:100 +msgid "Inbound (client) transparency: enabled" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:103 +msgid "``<``" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:103 +msgid "Outbound (origin server) transparency: either" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:105 +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/transparent-proxy.en.rst:109 +msgid "Some tested scenarios --" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:111 +msgid "`Transparent bridging `_" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:112 +msgid "`Inline router `_" +msgstr "" + +#: ../../admin/transparent-proxy.en.rst:113 +msgid "`WCCP Configuration `_" +msgstr "" 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..d6bfc2b8cb6 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/bridge.en.po @@ -0,0 +1,199 @@ +# +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 "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/bridge.en.rst:29 +msgid "Linux packages required:" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:31 +msgid "bridge-utils" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:32 +msgid "ebtables" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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]_(#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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/bridge.en.rst:125 +msgid "" +"To configure Traffic Server set the following values in " +":file:`records.config`" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:128 +msgid "" +":ts:cv:`proxy.config.http.server_ports` *value from* ``--on-port`` (see " +"below)" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:130 +msgid ":ts:cv:`proxy.config.reverse_proxy.enabled` ``1``" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:132 +msgid ":ts:cv:`proxy.config.url_remap.remap_required` ``0``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/bridge.en.rst:138 +msgid "Additional troubleshooting" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:140 +msgid "Check to make sure that ``iptables`` is not filtering (blocking)" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:141 +msgid "incoming HTTP connections." +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 "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/bridge.en.rst:157 +msgid "Verify that IP packet forwarding is enabled. You can check this with::" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:171 +msgid "Footnotes" +msgstr "" + +#: ../../admin/transparent-proxy/bridge.en.rst:173 +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 "" 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..032cbfadbd2 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/build.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" + +#: ../../admin/transparent-proxy/build.en.rst:4 +msgid "Building ATS for transparency" +msgstr "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/build.en.rst:34 +msgid "``--enable-posix-cap``" +msgstr "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/build.en.rst:52 +msgid "``--enable-tproxy[=value]``" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" 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..843d6a41a86 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/router-inline.en.po @@ -0,0 +1,118 @@ +# +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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:27 +msgid "Interface ``eth0`` is on the network 192.168.1.0/24" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:28 +msgid "Interface ``eth1`` is on the network 172.28.56.0/24" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:73 +msgid "" +"To configure Traffic Server set the following values in " +":file:`records.config`" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:78 +msgid "``proxy.config.http.server_port``" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:77 +msgid "``STRING`` Default: *value from* ```--on-port`` <#on_port>`_" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:80 +msgid "" +"proxy.config.http.server_port_attr {#proxy.config.http.server_port_attr}" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:82 +msgid "``STRING`` Default: ``=``" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:87 +msgid "``proxy.config.reverse_proxy.enabled``" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:86 +msgid "``INT`` Default: ``1``" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:91 +msgid "``proxy.config.url_remap.remap_required``" +msgstr "" + +#: ../../admin/transparent-proxy/router-inline.en.rst:90 +msgid "``INT`` Default: ``0``" +msgstr "" 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..04d275e1fc0 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/transparent-proxy/wccp-configuration.en.po @@ -0,0 +1,208 @@ +# +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 "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:31 +msgid "" +"If already have a router that supports WCCP inline you do not not have to " +"change your network topology." +msgstr "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:36 +msgid "" +"Use of WCCP only makes sense for client side transparency [1]_(#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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:79 +msgid "" +"Shared -- Traffic Server traffic shares an interface with client or server " +"traffic." +msgstr "" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:81 +msgid "Inside Shared -- Traffic Server and client traffic share an interface." +msgstr "" + +#: ../../admin/transparent-proxy/wccp-configuration.en.rst:83 +msgid "" +"`Outside Shared `_ -- Traffic Server and origin " +"server traffic share an interface." +msgstr "" + +#: ../../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]_(#2). " +"Click the links above for more detailed configuration information on a " +"specific topology." +msgstr "" + +#: ../../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: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]_(#3). Fortunately the GRE " +"tunnel used for packet forwarding and return can be used as the simulated " +"interface for Traffic Server." +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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" 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..bfd904a6fee --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po @@ -0,0 +1,1438 @@ +# +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..17a28be9559 --- /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..ca66d40f022 --- /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..39a82075e53 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po @@ -0,0 +1,226 @@ +# +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:73 +msgid "" +"These collisions are not of themselves good or bad. An administrator needs " +"to decide which is appropriate for his 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 used to invoke the " +"API call :c:func:`TSCacheUrlSet()` to provide a specific cache key." +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:79 +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:83 +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:85 +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:87 +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:91 +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:95 +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:97 +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 "" 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..7223cb43875 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-arch.en.po @@ -0,0 +1,1686 @@ +# +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: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 *object* in the cache. Each object " +"is identified by a globally unique value called a *cache key*. By default " +"this is generated by taking the `MD5 hash " +"`_ of the URI used to retrieve " +"the content from the origin server." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:32 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:38 +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:42 +msgid "Cache Layout" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:44 +msgid "" +"The first step in understanding cache operations is to understand the data " +"structures and layout of the cache." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:47 +msgid "Cache storage" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:49 +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 an " +"undifferentiated unit of storage." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:54 +msgid "Two cache spans" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:56 +msgid "" +"This storage organized in to a set of :term:`cache volume`\\ s which are " +"defined in :file:`volume.config`. 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:59 +msgid "If the cache volumes for the example cache spans were defined as" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:64 +msgid "then the actual layout would look like" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:69 +msgid "" +"A cached object is stored entirely in a single stripe, and therefore in a " +"single cache span - objects are never split across cache 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" +" 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:76 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:82 +msgid "Stripe Structure" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:84 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:91 +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:99 +msgid "Cache Directory" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:107 +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 a \"cache ID\" " +"as the key. A cache ID is a 128 bit (16 byte) value generated in various " +"ways depending on context. This ID is reduced and used as an index in to the" +" directory to locate an entry in the standard way." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:115 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:119 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:128 +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. Exact size data is stored in the fragment header " +"on disk." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:133 +msgid "" +"Data in HTTP headers cannot be examined without disk I/O. This includes the " +"original URL for the object. The original source of the cache ID is not " +"stored anywhere." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:139 +msgid "" +"The entries in a directory are grouped. The first level grouping is a " +"*bucket*. This is a fixed number (currently 4 - defined as ``DIR_DEPTH``) of" +" entries. The index generated from a cache ID is used as a bucket index (not" +" an entry index). Buckets are grouped in to *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 " +"exceeeding 65535 (2\\ :sup:`16`\\ -1) entries in a segment. Note that all " +"segments in the same stripe will have the same number of buckets." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:148 +msgid "" +"Each entry has a previous and next index value which is used to link the " +"entries in the same segment. The index size is 16 bits which suffices to " +"index any entry in the same segment. The stripe header contains an array of " +"entry indices which are used as the roots of a free list. 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 rooted in the " +"stripe header. In essence the first element of each fixed bucket is used as " +"a root for that bucket. The other entries in the fixed bucker are " +"preferentially preferred for adding to that 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. " +"This maximizes locality for bucket searching." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:161 +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 bucket (which also determines the segment). If the first " +"entry in the 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 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:169 +msgid "Storage Layout" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:171 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:181 +msgid "Each stripe has several values that describe its basic layout." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:185 +msgid "skip" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:184 +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:188 +msgid "start" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:188 +msgid "The offset for the start of the content, after the stripe metadata." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:191 +msgid "length" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:191 +msgid "Total number of bytes in the stripe. :cpp:member:`Vol::len`." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:194 +msgid "data length" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:194 +msgid "" +"Total number of blocks in the stripe available for content storage. " +":cpp:member:`Vol::data_blocks`." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:196 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:198 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:208 +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:217 +msgid "The write cursor and documents in the cache." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:219 +msgid "Cache data on disk is never updated." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:221 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:229 +msgid "Object Structure" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:231 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:235 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:245 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:254 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:261 +msgid "``Doc`` layout 3.2.0" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:263 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:270 +msgid "``Doc`` layout 4.0.1" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:272 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:276 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:284 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:287 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:298 +msgid "" +"where ``next_key`` is a global function that deterministically computes a " +"new cache key from an existing cache key." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:300 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:310 +msgid "Multi-alternate and multi-fragment object storage" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:314 +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:320 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:325 +msgid "" +"It could, under certain circumstances, be accurate for none of the " +"alternates." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:328 +msgid "Additional Notes" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:330 +msgid "Some general observations on the data structures." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:333 +msgid "Cyclone buffer" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:335 +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:341 +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:346 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:352 +msgid "Disk Failure" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:354 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:358 +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:361 +msgid "Implementation Details" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:364 +msgid "Stripe Directory" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:368 +msgid "The in memory volume directory entries are defined as described below." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:372 +msgid "Defined in |P-CacheDir.h|_." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:375 +msgid "Name" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:375 +msgid "Type" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:375 +msgid "Use" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:377 +msgid "offset" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:377 +msgid "unsigned int:24" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:377 +msgid "Offset of first byte of metadata (volume relative)" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:378 +msgid "big" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:378 +msgid "unsigned in:2" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:378 +msgid "Size multiplier" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:379 +msgid "size" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:379 +msgid "unsigned int:6" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:379 +msgid "Size" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:380 +msgid "tag" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:380 +msgid "unsigned int:12" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:380 +msgid "Partial key (fast collision check)" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:381 +msgid "phase" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:381 +#: ../../arch/cache/cache-arch.en.rst:382 +#: ../../arch/cache/cache-arch.en.rst:383 +#: ../../arch/cache/cache-arch.en.rst:384 +msgid "unsigned int:1" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:381 +msgid "Unknown" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:382 +msgid "head" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:382 +msgid "Flag: first fragment in an object" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:383 +#: ../../arch/cache/cache-arch.en.rst:312 +msgid "pinned" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:383 +msgid "Flag: document is pinned" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:384 +msgid "token" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:384 +msgid "Flag: Unknown" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:385 +msgid "next" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:385 +msgid "unsigned int:16" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:385 +msgid "Segment local index of next entry." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:386 +msgid "offset_high" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:386 +msgid "inku16" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:386 +msgid "High order offset bits" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:389 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:391 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:395 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:397 +msgid "" +"The computation of the approximate size of the fragment is defined as::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:401 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:405 +msgid "Because *big* is 2 bits the values for the multiplier of *size* are" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:410 +msgid "*big*" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:410 +msgid "Multiplier" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:410 +msgid "Maximum Size" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:412 +msgid "0" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:412 +msgid "512 (2^9)" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:412 +#: ../../arch/cache/cache-arch.en.rst:414 +msgid "32768 (2^15)" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:413 +msgid "1" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:413 +msgid "4096 (2^12)" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:413 +#: ../../arch/cache/cache-arch.en.rst:415 +msgid "262144 (2^18)" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:414 +msgid "2" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:414 +msgid "2097152 (2^21)" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:415 +msgid "3" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:415 +msgid "16777216 (2^24)" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:418 +msgid "" +"Note also that *size* is effectively offset by one, so a value of 0 " +"indicates a single unit of the multiplier." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:422 +msgid "The target fragment size can set with the :file:`records.config` value" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:424 +msgid "``proxy.config.cache.target_fragment_size``" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:426 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:432 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:438 +msgid "" +"The cache index entry size is used only for reading the fragment from disk. " +"The actual size on disk, and the" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:439 +msgid "" +"amount of cache space consumed, is the actual size of the content rounded up" +" to the disk sector size (default 512 bytes)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:444 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:448 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:451 +msgid "The comment in :file:`records.config` is simply wrong." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:456 +msgid "Directory Probing" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:458 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:463 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:467 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:478 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:486 +msgid "Cache Operations" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:488 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:490 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:492 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:494 +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:497 +msgid "Cacheability" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:499 +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:501 +msgid "The set of things which can affect cacheability are" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:503 +msgid "Built in constraints" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:504 +msgid "Settings in :file:`records.config`" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:505 +msgid "Settings in :file:`cache.config`" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:506 +msgid "Plugin operations" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:508 +msgid "" +"The initial internal checks, along with their :file:`records.config` " +"overrides[#]_, are done in::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:512 +msgid "The checks that are done are" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:517 +msgid "Cacheable Method" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:515 +msgid "" +"The request must be one of ``GET``, ``HEAD``, ``POST``, ``DELETE``, ``PUT``." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:517 +msgid "See ``HttpTransact::is_method_cache_lookupable()``." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:531 +msgid "Dynamic URL" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:520 +msgid "" +"|TS| tries to avoid caching dynamic content because it's dynamic. A URL is " +"considered dynamic if it" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:522 +msgid "is not ``HTTP`` or ``HTTPS``" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:523 +msgid "has query parameters" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:524 +msgid "ends in ``asp``" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:525 +msgid "has ``cgi`` in the path" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:527 +msgid "This check can be disabled by setting a non-zero value for::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:531 +msgid "" +"In addition if a TTL is set for rule that matches in :file:`cache.config` " +"then this check is not done." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:534 +msgid "Range Request" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:534 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:536 +msgid "" +"A plugin can call :c:func:`TSHttpTxnReqCacheableSet()` to force the request " +"to be viewed as cache valid." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:538 +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 "" + +#: ../../arch/cache/cache-arch.en.rst:541 +msgid "Cache Lookup" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:543 +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:545 +msgid "There are three basic steps to a cache lookup." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:547 +msgid "The cache key is computed." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:549 +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:551 +msgid "The cache stripe is determined (based on the cache key)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:553 +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:555 +msgid "" +"The cache stripe directory :ref:`is probed ` using the index key " +"computed from the cache key." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:557 +msgid "" +"Various other lookaside directories are checked as well, such as the " +":ref:`aggregation buffer `." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:559 +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:561 +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:563 +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:566 +msgid "Cache Read" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:568 +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:572 +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:574 +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:576 +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:578 +msgid "Most of this work is done in::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:582 +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:584 +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:586 +msgid "After these checks the object age is calculated by::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:590 +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:594 +msgid "" +"How this age is used is determined by the :file:`records.config` value::" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:598 +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:600 +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:602 +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:607 +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:612 +msgid "Cache Write" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:614 +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:623 +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:627 +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:634 +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:641 +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:646 +msgid "Update" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:648 +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:650 +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:651 +msgid "" +"An alternate of the object is retrieved from an origin server and added to " +"the object." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:652 +msgid "" +"An alternate of the object is removed (e.g., due to a ``DELETE`` request)." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:654 +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:664 +msgid "Aggregation Buffer" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:666 +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:674 +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:678 +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:685 +msgid "Evacuation Mechanics" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:687 +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:693 +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:704 +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:712 +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:717 +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:725 +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:732 +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:735 +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:740 +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:757 +msgid "Evacuation Operation" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:759 +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:761 +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:763 +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:766 +msgid "Initialization" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:768 +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:772 +msgid "File" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:773 +msgid "Directory" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:774 +msgid "Disk" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:775 +msgid "Raw device" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:777 +msgid "" +"After setting 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:781 +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:784 +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. This what is passed to the AIO threads to be called " +"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:790 +msgid "Footnotes" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:791 +msgid "" +"`Work is under way `_ on " +"extending this to include objects that are in the ram cache." +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:794 +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:797 +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:95 +msgid "cache directory" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:101 +msgid "directory entry" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:102 +msgid "fragment" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:103 +msgid "cache ID" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:243 +msgid "alternate" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:442 +msgid "DIR_DEPTH" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:442 +msgid "index segment" +msgstr "" + +#: ../../arch/cache/cache-arch.en.rst:442 +msgid "index buckets" +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..b00d00f27c0 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-data-structures.en.po @@ -0,0 +1,228 @@ +# +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 "" + +#: ../../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 "" + +#: ../../arch/cache/cache-data-structures.en.rst:45 +msgid "Holds the data from a line in :file:`cache.config`." +msgstr "" + +#: ../../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 "" + +#: ../../arch/cache/cache-data-structures.en.rst:53 +#: ../../arch/cache/cache-data-structures.en.rst:63 +msgid "Defined in |HTTP.h|_." +msgstr "" + +#: ../../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 "" + +#: ../../arch/cache/cache-data-structures.en.rst:59 +msgid "A typedef for :cpp:class:`HTTPInfo`." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../arch/cache/cache-data-structures.en.rst:102 +msgid "A cache volume as described in :file:`volume.config`." +msgstr "" + +#: ../../arch/cache/cache-data-structures.en.rst:106 +msgid "Defined in |P-CacheVol.h|_." +msgstr "" + +#: ../../arch/cache/cache-data-structures.en.rst:110 +msgid "Validity check value. Set to ``DOC_MAGIC`` for a valid document." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../arch/cache/cache-data-structures.en.rst:142 +msgid "Removed as of version 3.3.0." +msgstr "" + +#: ../../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 "" 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..76f7809bf1c --- /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/tier-storage.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/tier-storage.en.po new file mode 100644 index 00000000000..8b1d8b060c9 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/tier-storage.en.po @@ -0,0 +1,208 @@ +# +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:40 +msgid "" +"The design presumes that if a user has multiple tiers of storage and an " +"ordering for those tiers, he 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 "" + +#: ../../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 "" 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..9658b487530 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/index.en.po @@ -0,0 +1,33 @@ +# +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:2 +msgid "Architecture" +msgstr "" + +#: ../../arch/index.en.rst:22 +msgid "Introduction" +msgstr "" + +#: ../../arch/index.en.rst:24 +msgid "" +"The original architectural documents for Traffic Server were lost in the " +"transation 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 "" + +#: ../../arch/index.en.rst:28 +msgid "Contents:" +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..9f34b1dbded --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/arch/proposals/hostdb.en.po @@ -0,0 +1,358 @@ +# +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..00062b3ee67 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/glossary.en.po @@ -0,0 +1,114 @@ +# +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:48 +msgid "cache span" +msgstr "" + +#: ../../glossary.en.rst:50 +msgid "" +"The physical storage described by a single line in :file:`storage.config`." +msgstr "" + +#: ../../glossary.en.rst:44 +msgid "cache stripe" +msgstr "" + +#: ../../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." +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 "" + +#: ../../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 "" + +#: ../../glossary.en.rst:54 +msgid "revalidation" +msgstr "" + +#: ../../glossary.en.rst:56 +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 "" + +#: ../../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 "" + +#: ../../glossary.en.rst:51 +msgid "storage unit" +msgstr "" + +#: ../../glossary.en.rst:53 +msgid "Obsolete term for :term:`cache span`." +msgstr "" + +#: ../../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 "" + +#: ../../glossary.en.rst:59 +msgid "write cursor" +msgstr "" + +#: ../../glossary.en.rst:61 +msgid "The location in a :term:`cache stripe` where new data is written." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/index.po b/doc/locale/ja/LC_MESSAGES/index.po new file mode 100644 index 00000000000..53b623f4a8e --- /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..6ed6fe106e6 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSAPI.en.po @@ -0,0 +1,239 @@ +# +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 "" + +#: ../../reference/api/TSAPI.en.rst:24 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSAPI.en.rst:25 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSAPI.en.rst:26 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSAPI.en.rst:54 +msgid "" +"Protocol plugins can enable Traffic Server to proxy-cache new protocol " +"content." +msgstr "" + +#: ../../reference/api/TSAPI.en.rst:55 +msgid "" +"A blacklisting plugin denies attempts to access web sites that are off-" +"limits." +msgstr "" + +#: ../../reference/api/TSAPI.en.rst:56 +msgid "Append transform plugins add data to HTTP response content." +msgstr "" + +#: ../../reference/api/TSAPI.en.rst:57 +msgid "An image conversion plugin transforms JPEG images to GIF images." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSAPI.en.rst:85 +msgid "" +"Function names are mixed-case. For example, :func:`TSUrlCreate` and " +":func:`TSContDestroy`." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSAPI.en.rst:142 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSAPI.en.rst:143 +msgid ":manpage:`TSPluginInit(3ts)`" +msgstr "" 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..3be669be690 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSDebug.en.po @@ -0,0 +1,83 @@ +# +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 "" + +#: ../../reference/api/TSDebug.en.rst:24 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSDebug.en.rst:25 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSDebug.en.rst:49 +msgid "" +":func:`TSIsDebugTagSet` returns non-zero if the given debug tag is enabled." +msgstr "" + +#: ../../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 "" + +#: ../../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 conjuction with " +":func:`TSHttpTxnDebugSet`, :func:`TSHttpSsnDebugSet`, " +":func:`TSHttpTxnDebugGet` and :func:`TSHttpSsnDebugGet` to enable debugging " +"on specific session and transaction objects." +msgstr "" + +#: ../../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 "" + +#: ../../reference/api/TSDebug.en.rst:78 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSDebug.en.rst:79 +msgid ":manpage:`TSAPI(3ts)`, :manpage:`printf(3)`" +msgstr "" 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..a317e1b7d16 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpHookAdd.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/TSHttpHookAdd.en.rst:22 +msgid "TSHttpHookAdd" +msgstr "" + +#: ../../reference/api/TSHttpHookAdd.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSHttpHookAdd.en.rst:26 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" 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..ea6dbc1ce0c --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSHttpOverridableConfig.en.po @@ -0,0 +1,71 @@ +# +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 "" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:27 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:28 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:55 +msgid "Examples" +msgstr "" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:57 +msgid "" +"Enable :ref:`transaction buffer control ` " +"with a high water mark of 262144 and a low water mark of 65536. ::" +msgstr "" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:69 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSHttpOverridableConfig.en.rst:70 +msgid ":manpage:`TSAPI(3ts)`" +msgstr "" 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..c738fcbe49b --- /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..35cad5988ff --- /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..da076f54490 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSIOBufferCreate.en.po @@ -0,0 +1,109 @@ +# +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..d23c194d453 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSInstallDirGet.en.po @@ -0,0 +1,64 @@ +# +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 "" + +#: ../../reference/api/TSInstallDirGet.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSInstallDirGet.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSInstallDirGet.en.rst:58 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSInstallDirGet.en.rst:59 +msgid ":manpage:`TSAPI(3ts)`" +msgstr "" 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..2748f8acab9 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSLifecycleHookAdd.en.po @@ -0,0 +1,138 @@ +# +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 "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:27 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:28 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:45 +msgid "`TS_LIFECYCLE_PORTS_INITIALIZED_HOOK`" +msgstr "" + +#: ../../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 "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:45 +msgid "" +"Invoked with the event `TS_EVENT_LIFECYCLE_PORTS_INITIALIZED` and `NULL` " +"data." +msgstr "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:53 +msgid "`TS_LIFECYCLE_PORTS_READY_HOOK`" +msgstr "" + +#: ../../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 "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:53 +msgid "" +"Invoked with the event `TS_EVENT_LIFECYCLE_PORTS_READY` and `NULL` data." +msgstr "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:58 +msgid "`TS_LIFECYCLE_CACHE_READY_HOOK`" +msgstr "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:56 +msgid "Called after Traffic Server cache initialization has finished." +msgstr "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:58 +msgid "" +"Invoked with the event `TS_EVENT_LIFECYCLE_CACHE_READY` and `NULL` data." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:108 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSLifecycleHookAdd.en.rst:109 +msgid ":manpage:`TSAPI(3ts)`, :manpage:`TSContCreate(3ts)`" +msgstr "" 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..0942a09e2d1 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSMBufferCreate.en.po @@ -0,0 +1,84 @@ +# +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 "" + +#: ../../reference/api/TSMBufferCreate.en.rst:24 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSMBufferCreate.en.rst:26 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" 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..6261682eee7 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSPluginInit.en.po @@ -0,0 +1,65 @@ +# +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 "" + +#: ../../reference/api/TSPluginInit.en.rst:24 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSPluginInit.en.rst:26 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" 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..e7a104829f6 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSRemap.en.po @@ -0,0 +1,97 @@ +# +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 "" + +#: ../../reference/api/TSRemap.en.rst:24 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSRemap.en.rst:26 +msgid "`#include ` `#include `" +msgstr "" + +#: ../../reference/api/TSRemap.en.rst:37 +msgid "Description" +msgstr "" + +#: ../../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 " +"pligin is given an opportunity to examine the HTTP transaction." +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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSRemap.en.rst:83 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSRemap.en.rst:85 +msgid ":manpage:`TSAPI(3ts)`" +msgstr "" 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..9f32a54c252 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSTrafficServerVersionGet.en.po @@ -0,0 +1,51 @@ +# +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 "" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:24 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:26 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../reference/api/TSTrafficServerVersionGet.en.rst:40 +msgid "The other APIs return an integer version number." +msgstr "" + +#: ../../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 "" 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..7da99a9a967 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSTypes.en.po @@ -0,0 +1,97 @@ +# +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 "" + +#: ../../reference/api/TSTypes.en.rst:24 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSTypes.en.rst:25 +msgid "`#include `" +msgstr "" + +#: ../../reference/api/TSTypes.en.rst:26 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../reference/api/TSTypes.en.rst:36 +msgid "An opaque type that represents a Traffic Server :term:`continuation`." +msgstr "" + +#: ../../reference/api/TSTypes.en.rst:40 +msgid "" +"An enumeration that identifies a specific type of hook for HTTP " +"transactions." +msgstr "" + +#: ../../reference/api/TSTypes.en.rst:44 +msgid "An opaque type that represents a Traffic Server :term:`session`." +msgstr "" + +#: ../../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 "" + +#: ../../reference/api/TSTypes.en.rst:54 +msgid "" +"An opaque type that represents a Traffic Server HTTP :term:`transaction`." +msgstr "" + +#: ../../reference/api/TSTypes.en.rst:58 +msgid "" +"An enumeration that identifies a :ref:`life cycle hook `." +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" 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..beaf17d6a99 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSUrlCreate.en.po @@ -0,0 +1,154 @@ +# +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:59 +msgid "Description" +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:61 +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 port or scheme " +"information." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:67 +msgid "" +":func:`TSUrlCreate` creates a new URL within the marshal buffer bufp. " +"Release the resulting handle with a call to TSHandleMLocRelease. " +":func:`TSUrlClone` copies the contents of the URL at location src_url within" +" the marshal buffer src_bufp to a location within the marshal buffer " +"dest_bufp. Release the returned handle with a call to " +":func:`TSHandleMLocRelease`." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:74 +msgid "" +":func:`TSUrlCopy` copies the contents of the URL at location src_url within " +"the marshal buffer src_bufp to the location dest_url within the marshal " +"buffer dest_bufp. :func:`TSUrlCopy` works correctly even if src_bufp and " +"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:81 +msgid "" +":func:`TSUrlPrint` formats a URL stored in an :type:`TSMBuffer` to an " +":type:`TSIOBuffer`." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:83 +msgid "" +":func:`TSUrlParse` parses a URL. The 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 start pointer equals the end pointer. The end pointer " +"must be one byte after the last character you want to parse. The URL parsing" +" routine assumes that everything between start and 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:91 +msgid "" +":func:`TSUrlLengthGet` calculates the length of the URL located at offset " +"within the marshal buffer bufp if it were returned as a string. This length " +"will be the same as the length returned by :func:`TSUrlStringGet`." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:95 +msgid "" +":func:`TSUrlStringGet` constructs a string representation of the URL located" +" at offset within the marshal buffer bufp. :func:`TSUrlStringGet` stores the" +" length of the allocated string in the parameter 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 NULL then no attempt is made to de-reference " +"it." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:102 +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 bufp. The length of " +"the returned string is placed in length and a pointer to the URL portion is " +"returned. The returned string is not guaranteed to be NUL-terminated." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:109 +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 bufp to the string value. If " +"length is -1 then these functions assume that value is NUL-terminated. " +"Otherwise, the length of the string value is taken to be length. These " +"functions copy the string to within bufp, so it can be subsequently modified" +" or deleted." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:117 +msgid "" +":func:`TSUrlPortGet` retrieves the port number portion of the URL located at" +" offset within the marshal buffer bufp, It returns 0 if there is no port " +"number." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:121 +msgid "" +":func:`TSUrlPortSet` sets the port number portion of the URL located at " +"offset within the marshal buffer bufp to the value port." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:124 +msgid "" +":func:`TSStringPercentEncode` performs percent-encoding of the string str, " +"storing the new string in the dst buffer. The length parameter will be set " +"to the new (encoded) string length, or 0 if the encoding failed. " +"TSUrlPercentEncode is similar but operates on a URL object. If the optional " +"map parameter is provided, it should be a map of characters to encode." +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:131 +msgid "" +":func:`TSStringPercentDecode` perform percent-decoding of the string in the " +"buffer, writing to the 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/TSUrlCreate.en.rst:137 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSUrlCreate.en.rst:139 +msgid "" +":manpage:`TSAPI(3ts)`, :manpage:`TSMBufferCreate(3ts)`, " +":manpage:`TSmalloc(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..f4d6cbe5963 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/api/TSmalloc.en.po @@ -0,0 +1,92 @@ +# +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 "" + +#: ../../reference/api/TSmalloc.en.rst:25 +msgid "Synopsis" +msgstr "" + +#: ../../reference/api/TSmalloc.en.rst:27 +msgid "`#include `" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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:`TSMimeHdrFieldStringValueGet` " +"into NLL-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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/api/TSmalloc.en.rst:78 +msgid "See also" +msgstr "" + +#: ../../reference/api/TSmalloc.en.rst:79 +msgid ":manpage:`TSAPI(3ts)`" +msgstr "" 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..77fc2dffb33 --- /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 "" 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..4df6a42854b --- /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: 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/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..7e808d77e19 --- /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..c36b04a4725 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/commands/traffic_line.en.po @@ -0,0 +1,150 @@ +# +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_line.en.rst:20 +msgid "traffic_line" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:23 +msgid "Synopsis" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:26 +msgid ":program:`traffic_line` [options]" +msgstr "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../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 "" + +#: ../../reference/commands/traffic_line.en.rst:88 +msgid "Shut down Traffic Server on the local node." +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:92 +msgid "Start Traffic Server on the local node." +msgstr "" + +#: ../../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 "" + +#: ../../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:119 +msgid "Performance Statistics" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:123 +msgid "" +"The :option:`traffic_line -r` option accepts the following variable names::" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:775 +msgid "Examples" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:777 +msgid "Configure Traffic Server to log in Squid format::" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:784 +msgid "Files" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:786 +msgid ":file:`records.config`, :file:`ssl_multicert.config`" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:789 +msgid "See also" +msgstr "" + +#: ../../reference/commands/traffic_line.en.rst:791 +msgid ":manpage:`records.config(5)`" +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..47a65c3e258 --- /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..8bc7a54d54f --- /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..d1442394864 --- /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:44 +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..7f97e6ebd13 --- /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:71 +msgid "Print usage information and exit." +msgstr "" + +#: ../../reference/commands/traffic_server.en.rst:75 +msgid "Print version information and exit." +msgstr "" + +#: ../../reference/commands/traffic_server.en.rst:78 +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..f572b228428 --- /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/tspush.en.po b/doc/locale/ja/LC_MESSAGES/reference/commands/tspush.en.po new file mode 100644 index 00000000000..fd3ae0ff755 --- /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..bed13eb8564 --- /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..d86a2559782 --- /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..9986ee4d64b --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/cache.config.en.po @@ -0,0 +1,254 @@ +# +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:129 +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:141 +msgid "``pin-in-cache``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:134 +msgid "" +"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:137 +msgid "``d`` for days; for example: 2d" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:138 +msgid "``h`` for hours; for example: 10h" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:139 +msgid "``m`` for minutes; for example: 5m" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:140 +msgid "``s`` for seconds; for example: 20s" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:141 +msgid "mixed units; for example: 1h15m20s" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:147 +msgid "``revalidate``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:146 +msgid "" +"The amount of time object(s) are to be considered fresh. Use the same time " +"formats as ``pin-in-cache``." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:154 +msgid "``ttl-in-cache``" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:152 +msgid "" +"The amount of time object(s) are to be kept in the cache, regardless of " +"Cache-Control response headers. Use the same time formats as pin-in-cache " +"and revalidate ." +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:157 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/cache.config.en.rst:159 +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 "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/congestion.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/congestion.config.en.po new file mode 100644 index 00000000000..559db69ed07 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/congestion.config.en.po @@ -0,0 +1,304 @@ +# +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/congestion.config.en.rst:20 +msgid "congestion.config" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:24 +msgid "" +"The :file:`congestion.config` file enables you to configure Traffic Server " +"to stop forwarding HTTP requests to origin servers when they become " +"congested, and then send the client a message to retry the congested origin " +"server later. After you modify the :file:`congestion.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. Traffic Server uses the :file:`congestion.config` file only if you " +"enable the `Congestion Control `_ option." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:35 +msgid "You can create rules in the congestion.config file to specify:" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:37 +msgid "Which origin servers Traffic Server tracks for congestion." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:38 +msgid "" +"The timeouts Traffic Server uses, depending on whether a server is " +"congested." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:40 +msgid "" +"The page Traffic Server sends to the client when a server becomes congested." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:42 +msgid "" +"If Traffic Server tracks the origin servers per IP address or per hostname." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:46 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:48 +msgid "" +"Each line in :file:`congestion.config` must follow the format below. Traffic" +" Server applies the rules in the order listed, starting at the top of the " +"file. Traffic Server recognizes three space-delimited tags::" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:54 +msgid "" +"The following list shows possible primary destinations with allowed values." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:58 +msgid "*``dest_domain``* {#dest_domain}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:58 +msgid "A requested domain name." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:61 +msgid "*``dest_host``* {#dest_host}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:61 +msgid "A requested hostname." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:64 +msgid "*``dest_ip``* {#dest_ip}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:64 +msgid "A requested IP address." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:67 +msgid "*``url_regex``* {#url_regex}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:67 +msgid "A regular expression (regex) to be found in a URL." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:69 +msgid "" +"The secondary specifiers are optional in the congestion.config file. The " +"following list shows possible secondary specifiers with allowed values. You " +"can use more than one secondary specifier in a rule; however, you cannot " +"repeat a secondary specifier." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:75 +msgid "*``port``* {#port}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:75 +msgid "A requested URL port or range of ports." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:78 +msgid "*``prefix``* {#prefix}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:78 +msgid "A prefix in the path part of a URL." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:80 +msgid "The following list shows the possible tags and their allowed values." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:86 +msgid "*``max_connection_failures``* {#max_connection_failures}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:83 +msgid "" +"Default: ``5`` The maximum number of connection failures allowed within the " +"fail window described below before Traffic Server marks the origin server as" +" congested." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:92 +msgid "*``fail_window``* {#fail_window}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:89 +msgid "" +"Default: ``120`` seconds. The time period during which the maximum number of" +" connection failures can occur before Traffic Server marks the origin server" +" as congested." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:97 +msgid "*``proxy_retry_interval``* {#proxy_retry_interval}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:95 +msgid "" +"Default: ``10`` seconds. The number of seconds that Traffic Server waits " +"before contacting a congested origin server again." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:102 +msgid "*``client_wait_interval``* {#client_wait_interval}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:100 +msgid "" +"Default: ``300`` seconds. The number of seconds that the client is advised " +"to wait before retrying the congested origin server." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:107 +msgid "*``wait_interval_alpha``* {#wait_interval_alpha}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:105 +msgid "" +"Default: ``30`` seconds The upper limit for a random number that is added to" +" the wait interval." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:113 +msgid "*``live_os_conn_timeout``* {#live_os_conn_timeout}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:110 +msgid "" +"Default: ``60`` seconds. The connection timeout to the live (uncongested) " +"origin server. If a client stops a request before the timeout occurs, then " +"Traffic Server does not record a connection failure." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:118 +msgid "*``live_os_conn_retries``* {#live_os_conn_retries}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:116 +msgid "" +"Default: ``2`` The maximum number of retries allowed to the live " +"(uncongested) origin server." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:122 +msgid "*``dead_os_conn_timeout``* {#dead_os_conn_timeout}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:121 +msgid "" +"Default: ``15`` secondsj The connection timeout to the congested origin " +"server." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:127 +msgid "*``dead_os_conn_retries``* {#dead_os_conn_retries}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:125 +msgid "" +"Default: ``1`` The maximum number of retries allowed to the congested origin" +" server." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:132 +msgid "*``max_connection``* {#max_connection}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:130 +msgid "" +"Default: ``-1`` The maximum number of connections allowed from Traffic " +"Server to the origin server." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:137 +msgid "*``error_page``* {#error_page}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:135 +msgid "" +"Default: ``\"congestion#retryAfter\"`` The error page sent to the client " +"when a server is congested. You must enclose the value in quotes;" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:150 +msgid "*:file:`congestion.config`* {#congestion_scheme}" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:140 +msgid "" +"Default: ``\"per_ip\"`` Specifies if Traffic Server applies the rule on a " +"per-host (``\"per_host\"``) or per-IP basis (``\"per_ip\"``). You must " +"enclose the value in quotes." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:145 +msgid "" +"For example: if the server ``www.host1.com`` has two IP addresses and you " +"use the tag value ``\"per_ip\"``, then each IP address has its own number of" +" connection failures and is marked as congested independently. If you use " +"the tag value ``\"per_host\"`` and the server ``www.host1.com`` is marked as" +" congested, then both IP addresses are marked as congested." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:153 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:155 +msgid "" +"The following :file:`congestion.config` rule configures Traffic Server to " +"stop forwarding requests to the server ``www.host.com`` on port 80 (HTTP " +"traffic) if the server is congested, according to the timeouts specified. " +"Traffic Server uses the default tag values because no tag has been " +"specified." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:165 +msgid "" +"You can use one or more tags in a rule, but each tag must have one value " +"only. If you specify no tags in the rule, then Traffic Server uses the " +"default values." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:169 +msgid "" +"You can override any of the default tag values by adding configuration " +"variables at the end of :file:`records.config` as follows:" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:176 +msgid "" +"where tag is one of the tags described in the list under " +":file:`congestion.config` and value is the value you want to use." +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:180 +msgid "For example::" +msgstr "" + +#: ../../reference/configuration/congestion.config.en.rst:186 +msgid "" +"Rules in the :file:`congestion.config` file override the following variables" +" in the :file:`records.config` file:" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/hosting.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/hosting.config.en.po new file mode 100644 index 00000000000..ea75cf34e7e --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/hosting.config.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" + +#: ../../reference/configuration/hosting.config.en.rst:20 +msgid "hosting.config" +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:24 +msgid "" +"The :file:`hosting.config` file enables you to assign cache partitions to " +"specific origin servers and/or domains so that you can manage cache space " +"efficiently and restrict disk usage. For step-by-step instructions on " +"partitioning the cache according to origin servers and/or domains, refer to " +"`Partitioning the Cache <../configuring-cache#PartitoningCache>`_. Before " +"you can assign cache partitions to specific origin servers and/or domains, " +"you must first partition your cache according to size and protocol in the " +":file:`volume.config` file. For step-by-step instructions about partitioning" +" your cache, refer to `Partitioning the Cache <../configuring-" +"cache#PartitioningCache>`_." +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:35 +msgid "" +"After you modify hosting.config, navigate to the Traffic Server bin " +"directory and run :option:`traffic_line -x` to apply your changes." +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:38 +msgid "" +"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/hosting.config.en.rst:43 +msgid "" +"The :file:`volume.config` configuration must be the same on all nodes in a " +"cluster." +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:46 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:48 +msgid "" +"Each line in the :file:`hosting.config` file must have one of the following " +"formats::" +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:54 +msgid "" +"where ``HOST`` is the fully-qualified hostname of the origin server whose " +"content you want to store on a particular partition (for example, " +"``www.myhost.com``); ``DOMAIN`` is the domain whose content you want to " +"store on a particular partition(for example, ``mydomain.com``); and " +"``NUMBERS`` is a comma-separated list of the partitions on which you want to" +" store the content that belongs to the origin server or domain listed. The " +"partition numbers must be valid numbers listed in the file:`volume.config`." +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:63 +msgid "" +"**Note:** To allocate more than one partition to an origin server or domain," +" you must enter the partitions in a comma-separated list on one line, as " +"shown in the example below. The :file:`hosting.config` file cannot contain " +"multiple entries for the same origin server or domain." +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:70 +msgid "Generic Partition" +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:72 +msgid "" +"When configuring the :file:`hosting.config` file, you must assign a generic " +"partition to use for content that does not belong to any of the origin " +"servers or domains listed. If all partitions for a particular origin server " +"become corrupt, Traffic Server will also use the generic partition to store " +"content for that origin server." +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:78 +msgid "The generic partition must have the following format::" +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:82 +msgid "where ``NUMBERS`` is a comma-separated list of generic partitions." +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:86 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/hosting.config.en.rst:88 +msgid "" +"The following example configures Traffic Server to store content from the " +"domain ``mydomain.com`` in partition 1 and content from ``www.myhost.com`` " +"in partition 2. Traffic Server stores content from all other origin servers " +"in partitions 3 and 4." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/icp.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/icp.config.en.po new file mode 100644 index 00000000000..af6e15c93a6 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/icp.config.en.po @@ -0,0 +1,163 @@ +# +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/icp.config.en.rst:20 +msgid "icp.config" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:26 +msgid "The Traffic Server ICP feature is not functional in this release." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:28 +msgid "" +"The :file:`icp.config` file defines ICP peers (parent and sibling caches)." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:32 +msgid "" +"After you modify the icp.config file, navigate to the Traffic Server bin " +"directory and run the :option:`traffic_line -x` command to apply the " +"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/icp.config.en.rst:39 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:41 +msgid "" +"Each line in the icp.config file contains the name and configuration " +"information for a single ICP peer in the following format::" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:46 +msgid "Each field is described in the following list." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:52 +msgid "*``host``* {#host}" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:49 +msgid "The hostname of the ICP peer." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:51 +msgid "" +"This field is optional; if you do not specify the hostname of the ICP peer, " +"you must specify the IP address." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:58 +msgid "*``host_IP``* {#host_IP}" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:55 +msgid "The IP address of the ICP peer." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:57 +msgid "" +"This field is optional; if you do not specify the IP address of the ICP " +"peer, you must specify the hostname." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:64 +msgid "*``ctype``* {#ctype}" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:61 +msgid "Use the following options:" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:63 +msgid "1 to indicate an ICP parent cache" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:64 +msgid "2 to indicate an ICP sibling cache" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:68 +msgid "*``proxy_port``* {#proxy_port}" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:67 +msgid "" +"The port number of the TCP port used by the ICP peer for proxy " +"communication." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:72 +msgid "*``icp_port``* {#icp_port}" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:71 +msgid "" +"The port number of the UDP port used by the ICP peer for ICP communication." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:78 +msgid "*``MC_on``* {#mc_on}" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:75 +msgid "Enable or disable MultiCast:" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:77 +msgid "0 if multicast is disabled" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:78 +msgid "1 if multicast is enabled" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:81 +msgid "*``MC_ip``* {#mc_ip}" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:81 +msgid "The MultiCast IP address." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:90 +msgid "*``MC_ttl``* {#mc_ttl}" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:84 +msgid "The multicast time to live. Use the following options:" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:86 +msgid "" +"1 if IP multicast datagrams will not be forwarded beyond a single subnetwork" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:88 +msgid "" +"2 to allow delivery of IP multicast datagrams to more than one subnet (if " +"there are one or more multicast routers attached to the first hop subnet)." +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:93 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/icp.config.en.rst:95 +msgid "" +"The following example configuration is for three nodes: the local host, one " +"parent, and one sibling." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/index.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/index.en.po new file mode 100644 index 00000000000..df0f10b98ab --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/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/configuration/index.en.rst:5 +msgid "Configuration File Reference" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/ip_allow.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/ip_allow.config.en.po new file mode 100644 index 00000000000..993758e4e3d --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/ip_allow.config.en.po @@ -0,0 +1,79 @@ +# +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/ip_allow.config.en.rst:20 +msgid "ip_allow.config" +msgstr "" + +#: ../../reference/configuration/ip_allow.config.en.rst:24 +msgid "" +"The :file:`ip_allow.config` file controls client access to the Traffic " +"Server proxy cache. You can specify ranges of IP addresses that are allowed " +"to use the Traffic Server as a web proxy cache. After you modify the " +":file:`ip_allow.config` file, navigate to the Traffic Server bin directory " +"and 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/ip_allow.config.en.rst:33 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/ip_allow.config.en.rst:35 +msgid "" +"Each line in the :file:`ip_allow.config` file must have the following " +"format::" +msgstr "" + +#: ../../reference/configuration/ip_allow.config.en.rst:40 +msgid "" +"where src_ip is the IP address or range of IP addresses of the client(s). " +"The action ``ip_allow`` enables the specified client(s) to access the " +"Traffic Server proxy cache, and ``ip_deny`` denies the specified client(s) " +"to access the Traffic Server proxy cache. Multiple method keywords can be " +"specified (method=GET method=HEAD), or multiple methods can be separated by " +"an '\\|' (method=GET\\|HEAD). The method keyword is optional and it is " +"defaulted to ALL. Available methods: ALL, GET, CONNECT, DELETE, HEAD, " +"ICP_QUERY, OPTIONS, POST, PURGE, PUT, TRACE, PUSH" +msgstr "" + +#: ../../reference/configuration/ip_allow.config.en.rst:50 +msgid "" +"By default, the :file:`ip_allow.config` file contains the following lines, " +"which allows all methods to localhost to access the Traffic Server proxy " +"cache and denies PUSH, PURGE and DELETE to all IPs (note this allows all " +"other methods to all IPs)::" +msgstr "" + +#: ../../reference/configuration/ip_allow.config.en.rst:61 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/ip_allow.config.en.rst:63 +msgid "" +"The following example enables all clients to access the Traffic Server proxy" +" cache::" +msgstr "" + +#: ../../reference/configuration/ip_allow.config.en.rst:68 +msgid "" +"The following example allows all clients on a specific subnet to access the " +"Traffic Server proxy cache::" +msgstr "" + +#: ../../reference/configuration/ip_allow.config.en.rst:73 +msgid "" +"The following example denies all clients on a specific subnet to access the " +"Traffic Server proxy cache::" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/log_hosts.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/log_hosts.config.en.po new file mode 100644 index 00000000000..e2ceb0cabe9 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/log_hosts.config.en.po @@ -0,0 +1,68 @@ +# +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/log_hosts.config.en.rst:20 +msgid "log_hosts.config" +msgstr "" + +#: ../../reference/configuration/log_hosts.config.en.rst:24 +msgid "" +"To record HTTP transactions for different origin servers in separate log " +"files, you must list each origin server hostname in the " +":file:`log_hosts.config` file. In addition, you must enable the `HTTP Host " +"Log Splitting <../working-log-files#HTTPHostLogSplitting>`_ option. You " +"should use the same :file:`log_hosts.config` file on every Traffic Server " +"node in your cluster. After you modify the :file:`log_hosts.config` file, " +"run the :option:`traffic_line -x` command to apply the 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/log_hosts.config.en.rst:35 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/log_hosts.config.en.rst:37 +msgid "" +"Each line in the :file:`log_hosts.config` file has the following format::" +msgstr "" + +#: ../../reference/configuration/log_hosts.config.en.rst:41 +msgid "where ``hostname`` is the hostname of the origin server." +msgstr "" + +#: ../../reference/configuration/log_hosts.config.en.rst:45 +msgid "" +"You can specify keywords in the :file:`log_hosts.config` file to record all " +"transactions from origin servers with the specified keyword in their names " +"in a separate log file. See the example below." +msgstr "" + +#: ../../reference/configuration/log_hosts.config.en.rst:50 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/log_hosts.config.en.rst:52 +msgid "" +"The following example configures Traffic Server to create separate log files" +" containing all HTTP transactions for the origin servers ``webserver1``, " +"``webserver2``, and ``webserver3``::" +msgstr "" + +#: ../../reference/configuration/log_hosts.config.en.rst:60 +msgid "" +"The following example records all HTTP transactions from origin servers that" +" contain ``sports`` in their names. For example: ``sports.yahoo.com`` and " +"``www.foxsports.com`` in a log file called ``squid-sport.log`` (the Squid " +"format is enabled)::" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/logs_xml.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/logs_xml.config.en.po new file mode 100644 index 00000000000..97ea8683252 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/logs_xml.config.en.po @@ -0,0 +1,507 @@ +# +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/logs_xml.config.en.rst:20 +msgid "logs_xml.config" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:24 +msgid "" +"The :file:`logs_xml.config` file defines the custom log file formats, " +"filters, and processing options. The format of this file is modeled after " +"XML, the Extensible Markup Language." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:29 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:31 +msgid "The :file:`logs_xml.config` file contains the specifications below:" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:33 +msgid "" +"``LogFormat`` specifies the fields to be gathered from each protocol event " +"access." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:35 +msgid "" +"``LogFilter`` specifies the filters that are used to include or exclude " +"certain entries being logged based on the value of a field within that " +"entry." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:38 +msgid "" +"``LogObject`` specifies an object that contains a particular format, a local" +" filename, filters, and collation servers." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:41 +msgid "" +"The :file:`logs_xml.config` file ignores extra white space, blank lines, and" +" all comments." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:47 +msgid "LogFormat" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:49 +msgid "The following list shows ``LogFormat`` specifications." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:57 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:54 +msgid "" +"Required Valid format names include any name except ``squid``, ``common``, " +"``extended``, or ``extended2``, which are pre-defined formats. There is no " +"default for this tag." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:78 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:62 +msgid "" +"Required A valid format specification is a printf-style string describing " +"each log entry when formatted for ASCII output. Use ``%<`` ``field`` ``>`` " +"as a placeholder for valid field names. For more information, refer to :ref" +":`custom-logging-fields`." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:68 +msgid "The specified field can be one of the following types:" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:70 +msgid "" +"Simple. For example: ``%`` A field within a container, such as an HTTP " +"header or a statistic. Fields of this type have the syntax: ::" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:76 +msgid "" +"Aggregates, such as ``COUNT``, ``SUM``, ``AVG``, ``FIRST``, ``LAST``. Fields" +" of this type have the syntax: ``%``" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:82 +msgid "" +"You cannot create a format specification that contains both aggregate " +"operators and regular fields." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:96 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:85 +msgid "" +"Optional Use this tag when the format contains aggregate operators. The " +"value \"``aggregate_interval_secs``\\\" represents the number of seconds " +"between individual aggregate values being produced." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:90 +msgid "The valid set of aggregate operators are:" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:92 +msgid "COUNT" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:93 +msgid "SUM" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:94 +msgid "AVG" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:95 +msgid "FIRST" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:96 +msgid "LAST" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:101 +msgid "LogFilters" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:103 +msgid "The following list shows the ``LogFilter`` specifications." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:107 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:106 +msgid "Required All filters must be uniquely named." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:131 +msgid "" +"````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:110 +msgid "Required This field contains the following elements:" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:113 +msgid "" +"``valid_log_field`` - the field that will be compared against the given " +"value. For more information, refer to :ref:`logging-format-cross-reference`." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:116 +msgid "" +"``valid_operator_field`` - any one of the following: ``MATCH``, " +"``CASE_INSENSITIVE_MATCH``, ``CONTAIN``, ``CASE_INSENSITIVE_CONTAIN``." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:120 +msgid "" +"``MATCH`` is true if the field and value are identical (case-sensitive)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:122 +msgid "" +"``CASE_INSENSITIVE_MATCH`` is similar to ``MATCH``, except that it is case-" +"insensitive." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:124 +msgid "" +"``CONTAIN`` is true if the field contains the value (the value is a " +"substring of the field)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:126 +msgid "" +"``CASE_INSENSITIVE_CONTAIN`` is a case-insensitive version of ``CONTAIN``." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:129 +msgid "" +"``valid_comparison_value`` - any string or integer matching the field type. " +"For integer values, all of the operators are equivalent and mean that the " +"field must be equal to the specified value." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:135 +msgid "" +"There are no negative comparison operators. If you want to specify a " +"negative condition, then use the ``Action`` field to ``REJECT`` the record." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:142 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:140 +msgid "" +"Required: ``ACCEPT`` or ``REJECT`` . This instructs Traffic Server to either" +" accept or reject records that satisfy the filter condition." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:147 +msgid "LogObject" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:149 +msgid "The following list shows the ``LogObject`` specifications." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:156 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:152 +msgid "" +"Required Valid format names include the predefined logging formats: " +"``squid``, ``common``, ``extended``, and ``extended2``, as well as any " +"previously-defined custom log formats. There is no default for this tag." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:171 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:159 +msgid "" +"Required The filename to which the given log file is written on the local " +"file system or on a remote collation server. No local log file will be " +"created if you fail to specify this tag. All filenames are relative to the " +"default logging directory." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:165 +msgid "" +"If the name does not contain an extension (for example, ``squid``), then the" +" extension ``.log`` is automatically appended to it for ASCII logs and " +"``.blog`` for binary logs (refer to :ref:`Mode = \"valid_logging_mode\" " +"`_)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:170 +msgid "" +"If you do not want an extension to be added, then end the filename with a " +"single (.) dot (for example: ``squid.`` )." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:199 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:176 +msgid "" +"Optional Valid logging modes include ``ascii`` , ``binary`` , and " +"``ascii_pipe`` . The default is ``ascii`` ." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:180 +msgid "" +"Use ``ascii`` to create event log files in human-readable form (plain " +"ASCII)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:182 +msgid "" +"Use ``binary`` to create event log files in binary format. Binary log files " +"generate lower system overhead and occupy less space on the disk (depending " +"on the information being logged). You must use the :program:`traffic_logcat`" +" utility to translate binary log files to ASCII format before you can read " +"them." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:187 +msgid "" +"Use ``ascii_pipe`` to write 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 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." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:195 +msgid "" +"If you are using a collation server, then the log is written to a pipe on " +"the collation server. A local pipe is created even before a transaction is " +"processed, so you can see the pipe right after Traffic Server starts. Pipes " +"on a collation server, however, *are* created when Traffic Server starts." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:205 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:202 +msgid "" +"Optional A comma-separated list of names of any previously-defined log " +"filters. If more than one filter is specified, then all filters must accept " +"a record for the record to be logged." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:211 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:208 +msgid "" +"Optional A comma-separated list of the protocols this object should log. " +"Valid protocol names for this release are ``HTTP`` (FTP is deprecated)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:216 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:214 +msgid "" +"Optional A comma-separated list of valid hostnames.This tag indicates that " +"only entries from the named servers will be included in the file." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:225 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:221 +msgid "" +"Optional A comma-separated list of collation servers to which all log " +"entries (for this object) are forwarded. Collation servers can be specified " +"by name or IP address. Specify the collation port with a colon after the " +"name; for example, ``host:port`` ." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:231 +msgid "``
``" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:228 +msgid "" +"Optional 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 "" + +#: ../../reference/configuration/logs_xml.config.en.rst:251 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:234 +msgid "" +"Optional Enables or disables log file rolling for the ``LogObject``. This " +"setting overrides the value for the " +":ts:cv:`proxy.config.log.rolling_enabled` variable in the " +":file:`records.config` file. Set *truth value* to one of the following " +"values:" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:241 +msgid "``0`` to disable rolling for this particular ``LogObject``." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:242 +msgid "" +"``1`` to roll log files at specific intervals during the day (you specify " +"time intervals with the ``RollingIntervalSec`` and ``RollingOffsetHr`` " +"fields)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:245 +msgid "" +"``2`` to roll log files when they reach a certain size (you specify the size" +" with the ``RollingSizeMb`` field)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:247 +msgid "" +"``3`` to roll log files at specific intervals during the day or when they " +"reach a certain size (whichever occurs first)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:249 +msgid "" +"``4`` to roll log files at specific intervals during the day when log files " +"reach a specific size (at a specified time if the file is of the specified " +"size)." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:263 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:256 +msgid "" +"Optional The seconds between log file rolling for the ``LogObject``; enables" +" you to specify different rolling intervals for different ``LogObjects``." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:261 +msgid "" +"This setting overrides the value for " +":ts:cv:`proxy.config.log.rolling_interval_sec` in the :file:`records.config`" +" file." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:273 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:266 +msgid "" +"Optional Specifies an hour (from 0 to 23) at which rolling is guaranteed to " +"align. Rolling might start before then, but a rolled file will be produced " +"only at that time. The impact of this setting is only noticeable if the " +"rolling interval is larger than one hour. This setting overrides the " +"configuration setting for :ts:cv:`proxy.config.log.rolling_offset_hr` in the" +" :file:`records.config` file." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:277 +msgid "````" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:276 +msgid "Optional The size at which log files are rolled." +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:280 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:282 +msgid "" +"The following is an example of a ``LogFormat`` specification that collects " +"information using three common fields: ::" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:290 +msgid "" +"The following is an example of a ``LogFormat`` specification that uses " +"aggregate operators: ::" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:299 +msgid "" +"The following is an example of a ``LogFilter`` that will cause only " +"``REFRESH_HIT`` entries to be logged: ::" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:310 +msgid "" +"When specifying the field in the filter condition, you can omit the ``%<>``." +" This means that the filter below is equivalent to the example directly " +"above: ::" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:320 +msgid "" +"The following is an example of a ``LogObject`` specification that creates a " +"local log file for the minimal format defined earlier. The log filename will" +" be ``minimal.log`` because this is an ASCII log file (the default).::" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:330 +msgid "" +"The following is an example of a ``LogObject`` specification that includes " +"only HTTP requests served by hosts in the domain ``company.com`` or by the " +"specific server ``server.somewhere.com``. Log entries are sent to port 4000 " +"of the collation host ``logs.company.com`` and to port 5000 of the collation" +" host ``209.131.52.129.`` ::" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:347 +msgid "WELF" +msgstr "" + +#: ../../reference/configuration/logs_xml.config.en.rst:349 +msgid "" +"Traffic Server supports WELF (WebTrends Enhanced Log Format) so you can " +"analyze Traffic Server log files with WebTrends reporting tools. A " +"predefined ```` that is compatible with WELF is provided in the " +":file:`logs_xml.config` file (shown below). To create a WELF format log " +"file, create a ```` that uses this predefined format. ::" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/parent.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/parent.config.en.po new file mode 100644 index 00000000000..e8047ce3b36 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/parent.config.en.po @@ -0,0 +1,259 @@ +# +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/parent.config.en.rst:20 +msgid "parent.config" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:24 +msgid "" +"The :file:`parent.config` file identifies the parent proxies used in an " +"cache hierarchy. Use this file to perform the following configuration:" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:27 +msgid "" +"Set up parent cache hierarchies, with multiple parents and parent failover" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:29 +msgid "Configure selected URL requests to bypass parent proxies" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:31 +msgid "" +"Traffic Server uses the :file:`parent.config` file only when the parent " +"caching option is enabled (refer to :ref:`configuring-traffic-server-to-" +"use-a-parent-cache`)." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:34 +msgid "" +"After you modify the :file:`parent.config` file, run the " +":option:`traffic_line -x` command to apply your changes. When you apply the " +"changes to one node in a cluster, Traffic Server automatically applies the " +"changes to all other nodes in the cluster." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:40 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:42 +msgid "" +"Each line in the :file:`parent.config` file must contain a parent caching " +"rule. Traffic Server recognizes three space-delimited tags: ::" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:47 +msgid "" +"The following list shows the possible primary destinations and their allowed" +" values." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:53 +msgid "``dest_domain``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:53 +msgid "A requested domain name." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:58 +msgid "``dest_host``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:58 +msgid "A requested hostname." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:63 +msgid "``dest_ip``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:63 +msgid "" +"A requested IP address or range of IP addresses separated by a dash (-)." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:68 +msgid "``url_regex``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:68 +msgid "A regular expression (regex) to be found in a URL" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:70 +msgid "" +"The secondary specifiers are optional in the :file:`parent.config` file. The" +" following list shows the possible secondary specifiers and their allowed " +"values." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:77 +msgid "``port``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:77 +msgid "A requested URL port." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:82 +msgid "``scheme``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:82 +msgid "A request URL protocol: ``http`` or ``https``." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:87 +msgid "``prefix``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:87 +msgid "A prefix in the path part of a URL." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:92 +msgid "``suffix``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:92 +msgid "A file suffix in the URL." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:102 +msgid "``method``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:97 +msgid "A request URL method. It can be one of the following:" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:99 +msgid "get" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:100 +msgid "post" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:101 +msgid "put" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:102 +msgid "trace" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:108 +msgid "``time``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:107 +msgid "" +"A time range, such as 08:00-14:00, during which the parent cache is used to " +"serve requests." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:113 +msgid "``src_ip``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:113 +msgid "A client IP address." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:115 +msgid "" +"The following list shows the possible actions and their allowed values." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:123 +msgid "``parent``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:120 +msgid "" +"An ordered list of parent servers. If the request cannot be handled by the " +"last parent server in the list, then it will be routed to the origin server." +" You can specify either a hostname or an IP address, but; you must specify " +"the port number." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:135 +msgid "``round_robin``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:128 +#: ../../reference/configuration/parent.config.en.rst:140 +msgid "One of the following values:" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:130 +msgid "" +"``true`` - Traffic Server goes through the parent cache list in a round " +"robin-based on client IP address." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:132 +msgid "" +"``strict`` - Traffic Server machines serve requests strictly in turn. For " +"example: machine ``proxy1`` serves the first request, ``proxy2`` serves the " +"second request, and so on." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:135 +msgid "``false`` - Round robin selection does not occur." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:144 +msgid "``go_direct``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:142 +msgid "" +"``true`` - requests bypass parent hierarchies and go directly to the origin " +"server." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:144 +msgid "``false`` - requests do not bypass parent hierarchies." +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:147 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:149 +msgid "" +"The following rule configures a parent cache hierarchy consisting of Traffic" +" Server (which is the child) and two parents, ``p1.x.com`` and ``p2.x.com``." +" Traffic Server forwards the requests it cannot serve to the parent servers " +"``p1.x.com`` and ``p2.x.com`` in a round-robin fashion::" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:158 +msgid "" +"The following rule 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): " +"``url_regex=politics prefix=/viewpoint go_direct=true``" +msgstr "" + +#: ../../reference/configuration/parent.config.en.rst:163 +msgid "" +"Every line in the :file:`parent.config` file must contain either a " +"``parent=`` or ``go_direct=`` directive." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/plugin.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/plugin.config.en.po new file mode 100644 index 00000000000..a736161a68b --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/plugin.config.en.po @@ -0,0 +1,46 @@ +# +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/plugin.config.en.rst:20 +msgid "plugin.config" +msgstr "" + +#: ../../reference/configuration/plugin.config.en.rst:24 +msgid "" +"The :file:`plugin.config` file controls run-time loadable plugins available " +"to the Traffic Server, as well as their configuration." +msgstr "" + +#: ../../reference/configuration/plugin.config.en.rst:28 +msgid "Example" +msgstr "" + +#: ../../reference/configuration/plugin.config.en.rst:41 +msgid "" +"Each configuration line consists of a path to an ``.so`` file. This path can" +" either be absolute, or relative to the plugin-directory (usually " +"``/usr/local/libexec/trafficserver``). Such a line tells Traffic Server to " +"load said plugin." +msgstr "" + +#: ../../reference/configuration/plugin.config.en.rst:46 +msgid "" +"A plugin can have any number of configuration parameters listed. Please " +"refer to our `plugins' documentation <../plugins>`_ for their reference." +msgstr "" + +#: ../../reference/configuration/plugin.config.en.rst:49 +msgid "" +"Plugins should only be listed *once*. The order in which the plugins are " +"listed is also the order in which they are chained for the processing." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/records.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/records.config.en.po new file mode 100644 index 00000000000..6d7afd3a44e --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/records.config.en.po @@ -0,0 +1,3010 @@ +# +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/records.config.en.rst:20 +msgid "records.config" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:24 +msgid "" +"The :file:`records.config` file is a list of configurable variables used by " +"the Traffic Server software. Many of the variables in the " +":file:`records.config` file are set automatically when you set configuration" +" options in Traffic Line or Traffic Shell. After you modify the " +":file:`records.config` file, run the command :option:`traffic_line -x` to " +"apply the changes. When you apply changes to one node in a cluster, Traffic " +"Server automatically applies the changes to all other nodes in the cluster." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:34 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:36 +msgid "Each variable has the following format::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:40 +msgid "where" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:42 +msgid "" +"``SCOPE`` is related to clustering and is either ``CONFIG`` (all members of " +"the cluster) or ``LOCAL`` (only the local machine)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:45 +msgid "" +"``DATATYPE`` is one of ``INT`` (integer), ``STRING`` (string), ``FLOAT`` " +"(floating point). : A variable marked as ``Deprecated`` is still functional " +"but should be avoided as it may be removed in a future release without " +"warning." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:51 +msgid "A variable marked as ``Reloadable`` can be updated via the command::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:55 +msgid "" +"``INT`` type configurations are expressed as any normal integer, e.g. " +"*32768*. They can also be expressed using more human readable values using " +"standard prefixes, e.g. *32K*. The following prefixes are supported for all " +"``INT`` type configurations" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:60 +msgid "``K`` Kilobytes (1024 bytes)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:61 +msgid "``M`` Megabytes (1024^2 or 1,048,576 bytes)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:62 +msgid "``G`` Gigabytes (1024^3 or 1,073,741,824 bytes" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:63 +msgid "``T`` Terabytes (1024^4 or 1,099,511,627,776 bytes)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:67 +msgid "" +"Traffic Server currently writes back configurations to disk periodically, " +"and when doing so, will not preserve the prefixes." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:71 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:73 +msgid "" +"In the following example, the variable `proxy.config.proxy_name`_ is a " +"``STRING`` datatype with the value ``my_server``. This means that the name " +"of the Traffic Server proxy is ``my_server``. ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:79 +msgid "If the server name should be ``that_server`` the line would be ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:83 +msgid "" +"In the following example, the variable ``proxy.config.arm.enabled`` is a " +"yes/no flag. A value of ``0`` (zero) disables the option; a value of ``1`` " +"enables the option. ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:89 +msgid "" +"In the following example, the variable sets the cluster startup timeout to " +"10 seconds. ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:94 +msgid "" +"The last examples configures a 64GB RAM cache, using a human readable " +"prefix. ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:101 +msgid "Environment Overrides" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:103 +msgid "" +"Every :file:`records.config` configuration variable can be overridden by a " +"corresponding environment variable. This can be useful in situations where " +"you need a static :file:`records.config` but still want to tweak one or two " +"settings. The override variable is formed by converting the " +":file:`records.config` variable name to upper case, and replacing any dot " +"separators with an underscore." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:110 +msgid "" +"Overriding a variable from the environment is permanent and will not be " +"affected by future configuration changes made in :file:`records.config` or " +"applied with :program:`traffic_line`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:114 +msgid "" +"For example, we could override the `proxy.config.product_company`_ variable " +"like this::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:123 +msgid "Configuration Variables" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:125 +msgid "" +"The following list describes the configuration variables available in the " +":file:`records.config` file." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:129 +msgid "System Variables" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:133 +msgid "The name of the organization developing Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:137 +msgid "The name of the vendor providing Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:141 +msgid "The name of the product." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:146 +msgid "The name of the Traffic Server node." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:150 +msgid "The location of the Traffic Server ``bin`` directory." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:154 +msgid "" +"The name of the executable that runs the :program:`traffic_server` process." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:158 +msgid "The command-line options for starting Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:162 +msgid "" +"The name of the executable that runs the :program:`traffic_manager` process." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:166 +msgid "" +"The script executed before the :program:`traffic_manager` process spawns the" +" :program:`traffic_server` process." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:171 +msgid "The directory that contains Traffic Server configuration files." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:176 +msgid "The email address to which Traffic Server sends alarm messages." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:178 +msgid "" +"During a custom Traffic Server installation, you can specify the email " +"address; otherwise, Traffic Server uses the Traffic Server user account name" +" as the default value for this variable." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:183 +msgid "" +"The facility used to record system log files. Refer to :ref:`understanding-" +"traffic-server-log-files`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:187 +msgid "" +"The signal sent to :program:`traffic_cop`'s managed processes to stop them." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:189 +msgid "A value of ``0`` means no signal will be sent." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:193 +msgid "" +"The minimum amount of free swap space allowed before Traffic Server stops " +"the :program:`traffic_server` and :program:`traffic_manager` processes to " +"prevent the system from hanging. This configuration variable applies if swap" +" is enabled in Linux 2.2 only." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:198 +msgid "" +"The name and location of the file that contains warnings, status messages, " +"and error messages produced by the Traffic Server processes. If no path is " +"specified, then Traffic Server creates the file in its logging directory." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:203 +msgid "" +"The directory in which Traffic Server stores configuration snapshots on the " +"local system. Unless you specify an absolute path, this directory is located" +" in the Traffic Server ``config`` directory." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:208 +msgid "" +"When enabled (the default, ``1``), Traffic Server scales threads according " +"to the available CPU cores. See the config option below." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:212 +msgid "" +"Factor by which Traffic Server scales the number of threads. The multiplier " +"is usually the number of available CPU cores. By default this is scaling " +"factor is ``1.5``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:217 +msgid "*XXX* What does this do?" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:221 +msgid "" +"When enabled (``1``), runs a separate thread for accept processing. If " +"disabled (``0``), then only 1 thread can be created." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:225 +msgid "" +"The new default thread stack size, for all threads. The original default is " +"set at 1 MB." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:232 +#: ../../reference/configuration/records.config.en.rst:299 +#: ../../reference/configuration/records.config.en.rst:514 +#: ../../reference/configuration/records.config.en.rst:532 +#: ../../reference/configuration/records.config.en.rst:1383 +#: ../../reference/configuration/records.config.en.rst:1672 +msgid "Value" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:232 +#: ../../reference/configuration/records.config.en.rst:299 +#: ../../reference/configuration/records.config.en.rst:514 +#: ../../reference/configuration/records.config.en.rst:532 +#: ../../reference/configuration/records.config.en.rst:1672 +msgid "Effect" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:234 +#: ../../reference/configuration/records.config.en.rst:301 +#: ../../reference/configuration/records.config.en.rst:517 +#: ../../reference/configuration/records.config.en.rst:535 +#: ../../reference/configuration/records.config.en.rst:1386 +#: ../../reference/configuration/records.config.en.rst:1675 +msgid "1" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:234 +msgid "assign threads to sockets" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:235 +#: ../../reference/configuration/records.config.en.rst:302 +#: ../../reference/configuration/records.config.en.rst:518 +#: ../../reference/configuration/records.config.en.rst:536 +#: ../../reference/configuration/records.config.en.rst:1387 +#: ../../reference/configuration/records.config.en.rst:1676 +msgid "2" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:235 +msgid "assign threads to real cores" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:236 +#: ../../reference/configuration/records.config.en.rst:303 +#: ../../reference/configuration/records.config.en.rst:519 +#: ../../reference/configuration/records.config.en.rst:537 +#: ../../reference/configuration/records.config.en.rst:1388 +#: ../../reference/configuration/records.config.en.rst:1677 +msgid "3" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:236 +msgid "assign threads to logical cores" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:237 +#: ../../reference/configuration/records.config.en.rst:516 +#: ../../reference/configuration/records.config.en.rst:534 +#: ../../reference/configuration/records.config.en.rst:1385 +#: ../../reference/configuration/records.config.en.rst:1674 +msgid "0" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:237 +msgid "don't assign threads to any cores" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:242 +msgid "" +"This option only has an affect when Traffic Server has been compiled with " +"``--enable-hwloc``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:245 +msgid "Network" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:249 +msgid "" +"Controls the global default IP addresses to which to bind proxy server " +"ports. The value is a space separated list of IP addresses, one per " +"supported IP address family (currently IPv4 and IPv6)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:251 +msgid "" +"Unless explicitly specified in `proxy.config.http.server_ports`_ the server " +"port will be bound to one of these addresses, selected by IP address family." +" The built in default is any address. This is used if no address for a " +"family is specified. This setting is useful if most or all server ports " +"should be bound to the same address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:255 +msgid "" +"This is ignored for inbound transparent server ports because they must be " +"able to accept connections on arbitrary IP addresses." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +#: ../../reference/configuration/records.config.en.rst:0 +msgid "Example" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:259 +msgid "" +"Set the global default for IPv4 to ``192.168.101.18`` and leave the global " +"default for IPv6 as any address.::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:265 +msgid "" +"Set the global default for IPv4 to ``191.68.101.18`` and the global default " +"for IPv6 to ``fc07:192:168:101::17``.::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:271 +msgid "" +"This controls the global default for the local IP address for outbound " +"connections to origin servers. The value is a list of space separated IP " +"addresses, one per supported IP address family (currently IPv4 and IPv6)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:273 +msgid "" +"Unless explicitly specified in `proxy.config.http.server_ports`_ one of " +"these addresses, selected by IP address family, will be used as the local " +"address for outbound connections. This setting is useful if most or all of " +"the server ports should use the same outbound IP addresses." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:277 +msgid "" +"This is ignored for outbound transparent ports as the local outbound address" +" will be the same as the client local address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:281 +msgid "" +"Set the default local outbound IP address for IPv4 connectionsn to " +"``192.168.101.18``.::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:287 +msgid "" +"Set the default local outbound IP address to ``192.168.101.17`` for IPv4 and" +" ``fc07:192:168:101::17`` for IPv6.::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:292 +msgid "Cluster" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:296 +msgid "Sets the clustering mode:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:301 +msgid "full-clustering mode" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:302 +msgid "management-only mode" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:303 +msgid "no clustering" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:308 +msgid "" +"The reliable service port. The reliable service port is used to send " +"configuration information between the nodes in a cluster. All nodes in a " +"cluster must use the same reliable service port." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:313 +msgid "" +"The number of threads for cluster communication. On heavy cluster, the " +"number should be adjusted. It is recommend that take the thread CPU usage as" +" a reference when adjusting." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:318 +msgid "Set the interface to use for cluster communications." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:322 +msgid "" +"This turns on the local caching of objects in cluster mode. The point of " +"this is to allow for popular or **hot** content to be cached on all nodes in" +" a cluster. Be aware that the primary way to configure this behavior is via " +"the :file:`cache.config` configuration file using ``action=cluster-cache-" +"local`` directives." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:328 +msgid "" +"This particular :file:`records.config` configuration can be controlled per " +"transaction or per remap rule. As such, it augments the :file:`cache.config`" +" directives, since you can turn on the local caching feature without complex" +" regular expression matching." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:333 +msgid "" +"This implies that turning this on in your global :file:`records.config` is " +"almost never what you want; instead, you want to use this either via e.g. " +"``conf_remap.so`` overrides for a certain remap rule, or through a custom " +"plugin using the appropriate APIs." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:340 +msgid "Local Manager" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:344 +msgid "The semaphore ID for the local manager." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:348 +msgid "The autoconfiguration port." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:352 +msgid "The maximum number of copies of rolled configuration files to keep." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:356 +msgid "" +"Option used to specify who to run the :program:`traffic_server` process as; " +"also used to specify ownership of config and log files." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:358 +msgid "The nonprivileged user account designated to Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:360 +msgid "" +"As of version 2.1.1 if the user_id is prefixed with pound character (#) the " +"remaining of the string is considered to be a `numeric user identifier " +"`_. If the value is set to " +"``#-1`` Traffic Server will not change the user during startup." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:364 +msgid "" +"Setting ``user_id`` to ``root`` or ``#0`` is now forbidden to increase " +"security. Trying to do so, will cause the :program:`traffic_server` fatal " +"failure. However there are two ways to bypass that restriction" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:369 +msgid "Specify ``-DBIG_SECURITY_HOLE`` in ``CXXFLAGS`` during compilation." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:370 +msgid "Set the ``user_id=#-1`` and start trafficserver as root." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:373 +msgid "Process Manager" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:377 +msgid "" +"The port used for internal communication between the " +":program:`traffic_manager` and :program:`traffic_server` processes." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:380 +msgid "Alarm Configuration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:384 +msgid "" +"Name of the script file that can execute certain actions when an alarm is " +"signaled. The default file is a sample script named ``example_alarm_bin.sh``" +" located in the ``bin`` directory. You must dit the script to suit your " +"needs." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:389 +msgid "" +"The full path to the script file that sends email to alert someone bout " +"Traffic Server problems." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:392 +msgid "HTTP Engine" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:396 +msgid "Ports used for proxying HTTP traffic." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:398 +msgid "" +"This is a list, separated by space or comma, of :index:`port descriptors`. " +"Each descriptor is a sequence of keywords and values separated by colons. " +"Not all keywords have values, those that do are specifically noted. Keywords" +" with values can have an optional '=' character separating the keyword and " +"value. The case of keywords is ignored. The order of keywords is irrelevant " +"but unspecified results may occur if incompatible options are used (noted " +"below). Options without values are idempotent. Options with values use the " +"last (right most) value specified, except for ``ip-out`` as detailed later." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:400 +msgid "Quick reference chart." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:403 +msgid "Name" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:403 +msgid "Note" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:403 +msgid "Definition" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:405 +#: ../../reference/configuration/records.config.en.rst:421 +msgid "*number*" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:405 +msgid "**Required**" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:405 +msgid "The local port." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:406 +#: ../../reference/configuration/records.config.en.rst:424 +#: ../../reference/configuration/records.config.en.rst:1429 +msgid "ipv4" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:406 +msgid "**Default**" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:406 +msgid "Bind to IPv4 address family." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:407 +#: ../../reference/configuration/records.config.en.rst:427 +#: ../../reference/configuration/records.config.en.rst:1430 +msgid "ipv6" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:407 +msgid "Bind to IPv6 address family." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:408 +#: ../../reference/configuration/records.config.en.rst:432 +msgid "tr-in" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:408 +msgid "Inbound transparent." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:409 +#: ../../reference/configuration/records.config.en.rst:437 +msgid "tr-out" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:409 +msgid "Outbound transparent." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:410 +#: ../../reference/configuration/records.config.en.rst:442 +msgid "tr-full" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:410 +msgid "Fully transparent (inbound and outbound)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:411 +#: ../../reference/configuration/records.config.en.rst:445 +msgid "tr-pass" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:411 +msgid "Pass through enabled." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:412 +#: ../../reference/configuration/records.config.en.rst:467 +msgid "ssl" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:412 +msgid "SSL terminated." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:413 +#: ../../reference/configuration/records.config.en.rst:450 +msgid "ip-in" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:413 +#: ../../reference/configuration/records.config.en.rst:414 +#: ../../reference/configuration/records.config.en.rst:415 +msgid "**Value**" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:413 +msgid "Local inbound IP address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:414 +#: ../../reference/configuration/records.config.en.rst:457 +msgid "ip-out" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:414 +msgid "Local outbound IP address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:415 +#: ../../reference/configuration/records.config.en.rst:462 +msgid "ip-resolve" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:415 +msgid "IP address resolution style." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:416 +#: ../../reference/configuration/records.config.en.rst:472 +msgid "blind" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:416 +msgid "Blind (``CONNECT``) port." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:417 +#: ../../reference/configuration/records.config.en.rst:475 +msgid "compress" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:417 +msgid "**N/I**" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:417 +msgid "Compressed. Not implemented." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:421 +msgid "" +"Local IP port to bind. This is the port to which ATS clients will connect." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:424 +msgid "" +"Use IPv4. This is the default and is included primarily for completeness. " +"This forced if the ``ip-in`` option is used with an IPv4 address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:427 +msgid "" +"Use IPv6. This is forced if the ``ip-in`` option is used with an IPv6 " +"address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:430 +msgid "" +"Inbound transparent. The proxy port will accept connections to any IP " +"address on the port. To have IPv6 inbound transparent you must use this and " +"the ``ipv6`` option. This overrides " +":ts:cv:`proxy.local.incoming_ip_to_bind`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:432 +msgid "Not compatible with: ``ip-in``, ``ssl``, ``blind``" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:435 +msgid "" +"Outbound transparent. If ATS connects to an origin server for a transaction " +"on this port, it will use the client's address as its local address. This " +"overrides :ts:cv:`proxy.local.outgoing_ip_to_bind`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:437 +msgid "Not compatible with: ``ip-out``, ``ssl``, ``ip-resolve``" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:440 +msgid "" +"Fully transparent. This is a convenience option and is identical to " +"specifying both ``tr-in`` and ``tr-out``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:442 +msgid "" +"Not compatible with: Any option not compatible with ``tr-in`` or ``tr-out``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:445 +msgid "" +"Transparent pass through. This option is useful only for inbound transparent" +" proxy ports. If the parsing of the expected HTTP header fails, then the " +"transaction is switched to a blind tunnel instead of generating an error " +"response to the client. It effectively enables " +":ts:cv:`proxy.config.http.use_client_target_addr` for the transaction as " +"there is no other place to obtain the origin server address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:448 +msgid "" +"Set the local IP address for the port. This is the address to which clients " +"will connect. This forces the IP address family for the port. The ``ipv4`` " +"or ``ipv6`` can be used but it is optional and is an error for it to " +"disagree with the IP address family of this value. An IPv6 address **must** " +"be enclosed in square brackets. If this options is omitted " +":ts:cv:`proxy.local.incoming_ip_to_bind` is used." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:450 +msgid "Not compatible with: ``tr-in``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:453 +msgid "" +"Set the local IP address for outbound connections. This is the address used " +"by ATS locally when it connects to an origin server for transactions on this" +" port. If this is omitted :ts:cv:`proxy.local.outgoing_ip_to_bind` is used." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:455 +msgid "" +"This option can used multiple times, once for each IP address family. The " +"address used is selected by the IP address family of the origin server " +"address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:457 +#: ../../reference/configuration/records.config.en.rst:462 +msgid "Not compatible with: ``tr-out``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:460 +msgid "" +"Set the :ts:cv:`host resolution style ` for " +"transactions on this proxy port." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:465 +msgid "" +"Require SSL termination for inbound connections. SSL :ref:`must be " +"configured ` for this option to provide a " +"functional server port." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:467 +msgid "Not compatible with: ``tr-in``, ``tr-out``, ``blind``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:470 +msgid "Accept only ``CONNECT`` transactions on this port." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:472 +msgid "Not compatible with: ``tr-in``, ``ssl``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:475 +msgid "" +"Compress the connection. Retained only by inertia, should be considered " +"\"not implemented\"." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:479 +msgid "Listen on port 80 on any address for IPv4 and IPv6.::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:485 +msgid "" +"Listen transparently on any IPv4 address on port 8080, and transparently on " +"port 8080 on local address ``fc01:10:10:1::1`` (which implies ``ipv6``).::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:493 +msgid "" +"Listen on port 8080 for IPv6, fully transparent. Set up an SSL port on 443. " +"These ports will use the IP address from " +":ts:cv:`proxy.local.incoming_ip_to_bind`. Listen on IP address " +"``192.168.17.1``, port 80, IPv4, and connect to origin servers using the " +"local address ``10.10.10.1`` for IPv4 and ``fc01:10:10:1::1`` for IPv6.::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:499 +msgid "" +"The range of origin server ports that can be used for tunneling via " +"``CONNECT``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:501 +msgid "" +"Traffic Server allows tunnels only to the specified ports. Supports both " +"wildcards ('\\*') and ranges (\"0-1023\")." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:506 +msgid "" +"These are the ports on the *origin server*, not Traffic Server :ts:cv:`proxy" +" ports `." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:511 +msgid "" +"Set how the ``Via`` field is handled on a request to the origin server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:516 +#: ../../reference/configuration/records.config.en.rst:534 +msgid "Do not modify / set this via header" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:517 +#: ../../reference/configuration/records.config.en.rst:535 +msgid "Update the via, with normal verbosity" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:518 +#: ../../reference/configuration/records.config.en.rst:536 +msgid "Update the via, with higher verbosity" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:519 +#: ../../reference/configuration/records.config.en.rst:537 +msgid "Update the via, with highest verbosity" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:524 +#: ../../reference/configuration/records.config.en.rst:542 +msgid "" +"The ``Via`` header string interpretation can be `decoded here. " +"`_" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:529 +msgid "Set how the ``Via`` field is handled on the response to the client." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:547 +msgid "You can specify one of the following:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:549 +msgid "``0`` no Server: header is added to the response." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:550 +msgid "``1`` the Server: header is added (see string below)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:551 +msgid "" +"``2`` the Server: header is added only if the response from rigin does not " +"have one already." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:556 +msgid "" +"This option specifies whether Traffic Server should insert an ``Age`` header" +" in the response. The Age field value is the cache's estimate of the amount " +"of time since the response was generated or revalidated by the origin " +"server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:559 +msgid "``0`` no ``Age`` header is added" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:560 +msgid "``1`` the ``Age`` header is added" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:565 +msgid "" +"The Server: string that ATS will insert in a response header (if requested, " +"see above). Note that the current version number is always appended to this " +"string." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:571 +msgid "" +"Enables (``1``) or disables (``0``) ``.com`` domain expansion. This " +"configures the Traffic Server to resolve unqualified hostnames by prepending" +" with ``www.`` and appending with ``.com`` before redirecting to the " +"expanded address. For example: if a client makes a request to ``host``, then" +" Traffic Server redirects the request to ``www.host.com``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:578 +msgid "Specifies whether Traffic Sever can generate a chunked response:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:580 +msgid "``0`` Never" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:581 +msgid "``1`` Always" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:582 +msgid "" +"``2`` Generate a chunked response if the server has returned HTTP/1.1 before" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:583 +msgid "" +"``3`` = Generate a chunked response if the client request is HTTP/1.1 and " +"the origin server has returned HTTP/1.1 before" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:587 +msgid "" +"If HTTP/1.1 is used, then Traffic Server can use keep-alive connections with" +" pipelining to origin servers. If HTTP/0.9 is used, then Traffic Server does" +" not use ``keep-alive`` connections to origin servers. If HTTP/1.0 is used, " +"then Traffic Server can use ``keep-alive`` connections without pipelining to" +" origin servers." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:596 +msgid "Enables (``1``) or disables (``0``) the reuse of server sessions." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:601 +msgid "" +"Enables (``1``) or disables (``0``) :program:`traffic_cop` heartbeat ogging." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:605 +msgid "" +"For fully transparent ports use the same origin server address as the " +"client." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:607 +msgid "" +"This option causes Traffic Server to avoid where possible doing DNS lookups " +"in forward transparent proxy mode. The option is only effective if the " +"following three conditions are true -" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:611 +msgid "Traffic Server is in forward proxy mode." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:612 +msgid "The proxy port is inbound transparent." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:613 +msgid "The target URL has not been modified by either remapping or a plugin." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:615 +msgid "" +"If any of these conditions are not true, then normal DNS processing is done " +"for the connection." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:618 +msgid "" +"If all of these conditions are met, then the origin server IP address is " +"retrieved from the original client connection, rather than through HostDB or" +" DNS lookup. In effect, client DNS resolution is used instead of Traffic " +"Server DNS." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:623 +msgid "" +"This can be used to be a little more efficient (looking up the target once " +"by the client rather than by both the client and Traffic Server) but the " +"primary use is when client DNS resolution can differ from that of Traffic " +"Server. Two known uses cases are:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:628 +msgid "" +"Embedded IP addresses in a protocol with DNS load sharing. In this case, " +"even though Traffic Server and the client both make the same request to the " +"same DNS resolver chain, they may get different origin server addresses. If " +"the address is embedded in the protocol then the overall exchange will fail." +" One current example is Microsoft Windows update, which presumably embeds " +"the address as a security measure." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:636 +msgid "" +"The client has access to local DNS zone information which is not available " +"to Traffic Server. There are corporate nets with local DNS information for " +"internal servers which, by design, is not propagated outside the core " +"corporate network. Depending a network topology it can be the case that " +"Traffic Server can access the servers by IP address but cannot resolve such " +"addresses by name. In such as case the client supplied target address must " +"be used." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:645 +msgid "" +"This solution must be considered interim. In the longer term, it should be " +"possible to arrange for much finer grained control of DNS lookup so that " +"wildcard domain can be set to use Traffic Server or client resolution. In " +"both known use cases, marking specific domains as client determined (rather " +"than a single global switch) would suffice. It is possible to do this " +"crudely with this flag by enabling it and then use identity URL mappings to " +"re-disable it for specific domains." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:655 +msgid "Parent Proxy Configuration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:660 +msgid "" +"Enables (``1``) or disables (``0``) the parent caching option. Refer to :ref" +":`hierarchical-caching`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:665 +msgid "" +"The amount of time allowed between connection retries to a parent cache that" +" is unavailable." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:670 +msgid "" +"The number of times the connection to the parent cache can fail before " +"Traffic Server considers the parent unavailable." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:675 +msgid "" +"The total number of connection attempts allowed to a parent cache before " +"Traffic Server bypasses the parent or fails the request (depending on the " +"``go_direct`` option in the :file:`parent.config` file)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:681 +msgid "" +"The total number of connection attempts allowed per parent, if multiple " +"parents are used." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:686 +msgid "The timeout value (in seconds) for parent cache connection attempts." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:691 +msgid "" +"Configures Traffic Server to send proxy authentication headers on to the " +"parent cache." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:696 +msgid "" +"Don't try to resolve DNS, forward all DNS requests to the parent. This is " +"off (``0``) by default." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:699 +msgid "HTTP Connection Timeouts" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:704 +msgid "" +"Specifies how long Traffic Server keeps connections to clients open for a " +"subsequent request after a transaction ends." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:709 +msgid "" +"Specifies how long Traffic Server keeps connections to origin servers open " +"for a subsequent transfer of data after a transaction ends." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:714 +msgid "" +"Specifies how long Traffic Server keeps connections to clients open if a " +"transaction stalls." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:719 +msgid "" +"Specifies how long Traffic Server keeps connections to origin servers open " +"if the transaction stalls." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:724 +msgid "" +"The maximum amount of time Traffic Server can remain connected to a client. " +"If the transfer to the client is not complete before this timeout expires, " +"then Traffic Server closes the connection." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:727 +#: ../../reference/configuration/records.config.en.rst:735 +msgid "The default value of ``0`` specifies that there is no timeout." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:732 +msgid "" +"The maximum amount of time Traffic Server waits for fulfillment of a " +"connection request to an origin server. If Traffic Server does not complete " +"the transfer to the origin server before this timeout expires, then Traffic " +"Server terminates the connection request." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:740 +msgid "" +"The timeout interval in seconds before Traffic Server closes a connection " +"that has no activity." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:745 +msgid "" +"Specifies how long Traffic Server continues a background fill before giving " +"up and dropping the origin server connection." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:750 +msgid "" +"The proportion of total document size already transferred when a client " +"aborts at which the proxy continues fetching the document from the origin " +"server to get it into the cache (a **background fill**)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:754 +msgid "Origin Server Connect Attempts" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:759 +msgid "" +"The maximum number of connection retries Traffic Server can make when the " +"origin server is not responding." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:764 +msgid "" +"The maximum number of connection retries Traffic Server can make when the " +"origin server is unavailable." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:769 +msgid "" +"Limits the number of socket connections across all origin servers to the " +"value specified. To disable, set to zero (``0``)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:774 +msgid "" +"Limits the number of socket connections per origin server to the value " +"specified. To enable, set to one (``1``)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:779 +msgid "" +"As connection to an origin server are opened, keep at least 'n' number of " +"connections open to that origin, even if the connection isn't used for a " +"long time period. Useful when the origin supports keep-alive, removing the " +"time needed to set up a new connection from the next request at the expense " +"of added (inactive) connections. To enable, set to one (``1``)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:787 +msgid "" +"The maximum number of failed connection attempts allowed before a round-" +"robin entry is marked as 'down' if a server has round-robin DNS entries." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:793 +msgid "The timeout value (in seconds) for an origin server connection." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:798 +msgid "" +"The timeout value (in seconds) for an origin server connection when the " +"client request is a ``POST`` or ``PUT`` request." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:804 +msgid "" +"Specifies how long (in seconds) Traffic Server remembers that an origin " +"server was unreachable." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:809 +msgid "" +"The number of seconds before Traffic Server marks an origin server as " +"unavailable after a client abandons a request because the origin server was " +"too slow in sending the response header." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:813 +msgid "Congestion Control" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:817 +msgid "" +"Enables (``1``) or disables (``0``) the Congestion Control option, which " +"configures Traffic Server to stop forwarding HTTP requests to origin servers" +" when they become congested. Traffic Server sends the client a message to " +"retry the congested origin server later. Refer to :ref:`using-congestion-" +"control`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:823 +msgid "" +"Transaction buffering / flow control is enabled if this is set to a non-zero" +" value. Otherwise no flow control is done." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:828 +msgid "" +"The high water mark for transaction buffer control. External source I/O is " +"halted when the total buffer space in use by the transaction exceeds this " +"value." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:834 +msgid "" +"The low water mark for transaction buffer control. External source I/O is " +"resumed when the total buffer space in use by the transaction is no more " +"than this value." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:838 +msgid "Negative Response Caching" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:843 +msgid "" +"When enabled (``1``), Traffic Server caches negative responses (such as " +"``404 Not Found``) when a requested page does not exist. The next time a " +"client requests the same page, Traffic Server serves the negative response " +"directly from cache." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:849 +msgid "" +"``Cache-Control`` directives from the server forbidding ache are ignored for" +" the following HTTP response codes, regardless of the value specified for " +"the :ts:cv:`proxy.config.http.negative_caching_enabled` variable. The " +"following negative responses are cached by Traffic Server:::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:865 +msgid "" +"The cache lifetime for objects cached from this setting is controlled via " +":ts:cv:`proxy.config.http.negative_caching_lifetime`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:869 +msgid "Proxy User Variables" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:874 +msgid "" +"When enabled (``1``), Traffic Server removes the ``From`` header to protect " +"the privacy of your users." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:879 +msgid "" +"When enabled (``1``), Traffic Server removes the ``Referrer`` header to " +"protect the privacy of your site and users." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:884 +msgid "" +"When enabled (``1``), Traffic Server removes the ``User-agent`` header to " +"protect the privacy of your site and users." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:889 +msgid "" +"When enabled (``1``), Traffic Server removes the ``Cookie`` header to " +"protect the privacy of your site and users." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:894 +msgid "" +"When enabled (``1``), Traffic Server removes ``Client-IP`` headers for more " +"privacy." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:899 +msgid "" +"When enabled (``1``), Traffic Server inserts ``Client-IP`` headers to retain" +" the client IP address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:903 +msgid "" +"When enabled (``1``), Traffic Server appends ``X-Forwards`` headers to " +"outgoing requests." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:908 +msgid "The headers Traffic Server should remove from outgoing requests." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:913 +msgid "" +"When enabled (``1``), Traffic Server adds the client IP address to the ``X" +"-Forwarded-For`` header." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:918 +msgid "" +"Enable (``1``) to normalize all ``Accept-Encoding:`` headers to one of the " +"following:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:920 +msgid "" +"``Accept-Encoding: gzip`` (if the header has ``gzip`` or ``x-gzip`` with any" +" ``q``) **OR**" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:921 +msgid "*blank* (for any header that does not include ``gzip``)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:923 +msgid "" +"This is useful for minimizing cached alternates of documents (e.g. ``gzip, " +"deflate`` vs. ``deflate, gzip``). Enabling this option is recommended if " +"your origin servers use no encodings other than ``gzip``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:928 +msgid "Security" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:933 +msgid "" +"Enables (``1``) or disables (``0``) the HTTP ``PUSH`` option, which allows " +"you to deliver content directly to the cache without a user request." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:938 +msgid "" +"If you enable this option, then you must also specify a filtering rule in " +"the ip_allow.config file to allow only certain machines to push content into" +" the cache." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:943 +msgid "Cache Control" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:948 +msgid "" +"Enables (``1``) or disables (``0``) ability to a read cached object while " +"the another connection is completing the write to cache for the same object." +" Several other configuration values need to be set for this to become " +"active. See :ref:`reducing-origin-server-requests-avoiding-the-thundering-" +"herd`" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:954 +msgid "Forces the use of a specific hardware sector size (512 - 8192 bytes)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:959 +msgid "Enables (``1``) or disables (``0``) caching of HTTP requests." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:964 +msgid "" +"Enables (``1``) or disables (``0``) caching objects that have an empty " +"response body. This is particularly useful for caching 301 or 302 responses " +"with a ``Location`` header but no document body. This only works if the " +"origin response also has a ``Content-Length`` header." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:972 +msgid "" +"When enabled (``1``), Traffic Server ignores client requests to bypass the " +"cache." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:977 +msgid "" +"When enabled (``1``), Traffic Server issues a conditional request to the " +"origin server if an incoming request has a ``No-Cache`` header." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:982 +msgid "" +"When enabled (``1``), Traffic Server ignores origin server requests to " +"bypass the cache." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:987 +msgid "Specifies how cookies are cached:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:989 +msgid "``0`` = do not cache any responses to cookies" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:990 +msgid "``1`` = cache for any content-type" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:991 +msgid "``2`` = cache only for image types" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:992 +msgid "``3`` = cache for all but text content-types" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:996 +msgid "" +"When enabled (``1``), Traffic Server ignores ``WWW-Authentication`` headers " +"in responses ``WWW-Authentication`` headers are removed and not cached." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1002 +msgid "" +"Enables (``1``) or disables (``0``) caching of URLs that look dynamic, i.e.:" +" URLs that end in *``.asp``* or contain a question mark (*``?``*), a " +"semicolon (*``;``*), or *``cgi``*. For a full list, please refer to " +"`HttpTransact::url_looks_dynamic `_" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1009 +msgid "" +"Enables (``1``) or disables (``0``) caching of alternate versions of HTTP " +"objects that do not contain the ``Vary`` header." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1014 +msgid "Specifies when to revalidate content:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1016 +msgid "``0`` = use cache directives or heuristic (the default value)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1017 +msgid "``1`` = stale if heuristic" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1018 +msgid "``2`` = always stale (always revalidate)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1019 +msgid "``3`` = never stale" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1021 +msgid "``4`` = use cache directives or heuristic (0) unless the request" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1021 +msgid "has an ``If-Modified-Since`` header" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1023 +msgid "" +"If the request contains the ``If-Modified-Since`` header, then Traffic " +"Server always revalidates the cached content and uses the client's ``If-" +"Modified-Since`` header for the proxy request." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1030 +msgid "" +"Specifies when to add ``no-cache`` directives to Microsoft Internet Explorer" +" requests. You can specify the following:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1032 +msgid "``0`` = ``no-cache`` is *not* added to MSIE requests" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1033 +msgid "``1`` = ``no-cache`` is added to IMS MSIE requests" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1034 +msgid "``2`` = ``no-cache`` is added to all MSIE requests" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1039 +msgid "" +"The type of headers required in a request for the request to be cacheable." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1041 +msgid "``0`` = no headers required to make document cacheable" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1042 +msgid "" +"``1`` = either the ``Last-Modified`` header, or an explicit lifetime header," +" ``Expires`` or ``Cache-Control: max-age``, is required" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1043 +msgid "" +"``2`` = explicit lifetime is required, ``Expires`` or ``Cache-Control: max-" +"age``" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1048 +msgid "" +"The maximum age allowed for a stale response before it cannot be cached." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1052 +msgid "" +"When enabled (``1``), Traffic Server looks up range requests in the cache." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1057 +msgid "" +"When enabled with a value of ``1``, Traffic Server serves documents from " +"cache with a ``Content-Type:`` header even if it does not match the " +"``Accept:`` header of the request. If set to ``2``, this logic only happens " +"in the absence of a ``Vary`` header in the cached response (which is the " +"recommended and safe use)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1063 +msgid "" +"This option should only be enabled with ``1`` if you're having problems with" +" caching *and* you origin server doesn't set the ``Vary`` header. " +"Alternatively, if the origin is incorrectly setting ``Vary: Accept`` or " +"doesn't respond with ``406 (Not Acceptable)``, you can also enable this " +"configuration with a ``1``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1073 +msgid "" +"When enabled with a value of ``1``, Traffic Server serves documents from " +"cache with a ``Content-Language:`` header even if it does not match the " +"``Accept-Language:`` header of the request. If set to ``2``, this logic only" +" happens in the absence of a ``Vary`` header in the cached response (which " +"is the recommended and safe use)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1080 +msgid "" +"This option should only be enabled with ``1`` if you're having problems with" +" caching *and* you origin server doesn't set the ``Vary`` header. " +"Alternatively, if the origin is incorrectly setting ``Vary: Accept-" +"Language`` or doesn't respond with ``406 (Not Acceptable)``, you can also " +"enable this configuration with a ``1``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1090 +msgid "" +"When enabled with a value of ``1``, Traffic Server serves documents from " +"cache with a ``Content-Encoding:`` header even if it does not match the " +"``Accept-Encoding:`` header of the request. If set to ``2``, this logic only" +" happens in the absence of a ``Vary`` header in the cached response (which " +"is the recommended and safe use)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1097 +msgid "" +"This option should only be enabled with ``1`` if you're having problems with" +" caching *and* you origin server doesn't set the ``Vary`` header. " +"Alternatively, if the origin is incorrectly setting ``Vary: Accept-" +"Encoding`` or doesn't respond with ``406 (Not Acceptable)`` you can also " +"enable this configuration with a ``1``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1107 +msgid "" +"When enabled with a value of ``1``, Traffic Server serves documents from " +"cache with a ``Content-Type:`` header even if it does not match the " +"``Accept-Charset:`` header of the request. If set to ``2``, this logic only " +"happens in the absence of a ``Vary`` header in the cached response (which is" +" the recommended and safe use)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1114 +msgid "" +"This option should only be enabled with ``1`` if you're having problems with" +" caching *and* you origin server doesn't set the ``Vary`` header. " +"Alternatively, if the origin is incorrectly setting ``Vary: Accept-Charset``" +" or doesn't respond with ``406 (Not Acceptable)``, you can also enable this " +"configuration with a ``1``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1124 +msgid "" +"When enabled (``1``), Traffic Server ignores any ``Cache-Control: max-age`` " +"headers from the client. This technically violates the HTTP RFC, but avoids " +"a problem where a client can forcefully invalidate a cached object." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1130 +msgid "" +"Specifies the maximum object size that will be cached. ``0`` is unlimited." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1135 +msgid "" +"When enabled (``1``), Traffic Server will keep certain HTTP objects in the " +"cache for a certain time as specified in cache.config." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1139 +msgid "" +"The size of the region (as a percentage of the total content storage in a " +":term:`cache stripe`) in front of the :term:`write cursor` that constitutes " +"a recent access hit for evacutating the accessed object." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1142 +msgid "" +"When an object is accessed it can be marked for evacuation, that is to be " +"copied over the write cursor and thereby preserved from being overwritten. " +"This is done if it is no more than a specific number of bytes in front of " +"the write cursor. The number of bytes is a percentage of the total number of" +" bytes of content storage in the cache stripe where the object is stored and" +" that percentage is set by this variable." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1150 +msgid "Limit the size of objects that are hit evacuated." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1152 +msgid "" +"Objects larger than the limit are not hit evacuated. A value of 0 disables " +"the limit." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1155 +msgid "RAM Cache" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1159 +msgid "" +"By default the RAM cache size is automatically determined, based on disk " +"cache size; approximately 10 MB of RAM cache per GB of disk cache. " +"Alternatively, it can be set to a fixed value such as **20GB** (21474836480)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1166 +msgid "" +"Two distinct RAM caches are supported, the default (0) being the **CLFUS** " +"(*Clocked Least Frequently Used by Size*). As an alternative, a simpler " +"**LRU** (*Least Recently Used*) cache is also available, by changing this " +"configuration to 1." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1173 +msgid "" +"Enabling this option will filter inserts into the RAM cache to ensure that " +"they have been seen at least once. For the **LRU**, this provides scan " +"resistance. Note that **CLFUS** already requires that a document have " +"history before it is inserted, so for **CLFUS**, setting this option means " +"that a document must be seen three times before it is added to the RAM " +"cache." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1181 +msgid "" +"The **CLFUS** RAM cache also supports an optional in-memory compression. " +"This is not to be confused with ``Content-Encoding: gzip`` compression. The " +"RAM cache compression is intended to try to save space in the RAM, and is " +"not visible to the User-Agent (client)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1186 +msgid "Possible values are:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1188 +msgid "``0`` = no compression" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1189 +msgid "``1`` = fastlz (extremely fast, relatively low compression)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1190 +msgid "``2`` = libz (moderate speed, reasonable compression)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1191 +msgid "``3`` = liblzma (very slow, high compression)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1195 +msgid "" +"Compression runs on task threads. To use more cores for RAM cache " +"compression, increase :ts:cv:`proxy.config.task_threads`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1199 +msgid "Heuristic Expiration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1204 +msgid "" +"The minimum amount of time an HTTP object without an expiration date can " +"remain fresh in the cache before is considered to be stale." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1210 +msgid "" +"The maximum amount of time an HTTP object without an expiration date can " +"remain fresh in the cache before is considered to be stale." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1216 +msgid "" +"The aging factor for freshness computations. Traffic Server stores an object" +" for this percentage of the time that elapsed since it last changed." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1222 +msgid "" +"How often Traffic Server checks for an early refresh, during the period " +"before the document stale time. The interval specified must be in seconds. " +"See :ref:`fuzzy-revalidation`" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1228 +msgid "" +"The probability that a refresh is made on a document during the specified " +"fuzz time." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1233 +msgid "" +"Handles 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. The default value is ``0``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1236 +msgid "Dynamic Content & Content Negotiation" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1241 +msgid "The header on which Traffic Server varies for text documents." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1243 +msgid "" +"For example: if you specify ``User-agent``, then Traffic Server caches all " +"the different user-agent versions of documents it encounters." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1249 +msgid "The header on which Traffic Server varies for images." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1254 +msgid "" +"The header on which Traffic Server varies for anything other than text and " +"images." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1257 +msgid "Customizable User Response Pages" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1263 +msgid "``0`` = disable customizable user response pages" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1264 +msgid "" +"``1`` = enable customizable user response pages in the default directory " +"only" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1265 +msgid "``2`` = enable language-targeted user response pages" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1269 +msgid "" +"Enables (``1``) or disables (``0``) logging for customizable response pages." +" When enabled, Traffic Server records a message in the error log each time a" +" customized response page is used or modified." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1274 +msgid "The customizable response page default directory." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1278 +msgid "Specifies when Traffic Server suppresses generated response pages:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1280 +msgid "``0`` = never suppress generated response pages" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1281 +msgid "``1`` = always suppress generated response pages" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1282 +msgid "``2`` = suppress response pages only for intercepted traffic" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1286 +msgid "Enable the user interface page." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1289 +msgid "DNS" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1294 +msgid "Enables (``1``) or disables (``0``) local domain expansion." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1296 +msgid "" +"Traffic Server can attempt to resolve unqualified hostnames by expanding to " +"the local domain. For example if a client makes a request to an unqualified " +"host (``host_x``) and the Traffic Server local domain is ``y.com`` , then " +"Traffic Server will expand the hostname to ``host_x.y.com``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1305 +msgid "" +"Enables (``1``) or disables (``0``) DNS server selection. When enabled, " +"Traffic Server refers to the :file:`splitdns.config` file for the selection " +"specification. Refer to :ref:`Configuring DNS Server Selection (Split DNS) " +"`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1310 +msgid "" +"Specifies a list of hostname extensions that are automatically added to the " +"hostname after a failed lookup. For example: if you want Traffic Server to " +"add the hostname extension .org, then specify ``org`` as the value for this " +"variable (Traffic Server automatically adds the dot (.))." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1316 +msgid "" +"If the variable :ts:cv:`proxy.config.http.enable_url_expandomatic` is set to" +" ``1`` (the default value), then you do not have to add *``www.``* and " +"*``.com``* to this list because Traffic Server automatically tries www. and " +".com after trying the values you've specified." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1322 +msgid "" +"Allows to specify which ``resolv.conf`` file to use for finding resolvers. " +"While the format of this file must be the same as the standard " +"``resolv.conf`` file, this option allows an administrator to manage the set " +"of resolvers in an external configuration file, without affecting how the " +"rest of the operating system uses DNS." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1329 +msgid "Enables (``1``) or disables (``0``) DNS server round-robin." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1334 +msgid "The DNS servers." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1339 +msgid "Indicates whether to use SRV records for orgin server lookup." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1343 +msgid "" +"Create and dedicate a thread entirely for DNS processing. This is probably " +"most useful on system which do a significant number of DNS lookups, " +"typically forward proxies. But even on other systems, it can avoid some " +"contention on the first worker thread (which otherwise takes on the burden " +"of all DNS lookups)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1350 +msgid "HostDB" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1355 +msgid "" +"The number of seconds for which to use a stale NS record while initiating a " +"background fetch for the new data." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1358 +msgid "If not set then stale records are not served." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1363 +msgid "" +"The amount of space (in bytes) used to store ``hostdb``. The value of this " +"variable must be increased if you increase the size of the " +"`proxy.config.hostdb.size`_ variable." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1369 +msgid "The maximum number of entries that can be stored in the database." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1373 +msgid "" +"For values above ``200000``, you must increase " +":ts:cv:`proxy.config.hostdb.storage_size` by at least 44 bytes per entry." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1378 +msgid "" +"A host entry will eventually time out and be discarded. This variable " +"controls how that time is calculated. A DNS request will return a TTL value " +"and an internal value can be set with :ts:cv:`proxy.config.hostdb.timeout`. " +"This variable determines which value will be used." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1383 +msgid "TTL" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1385 +msgid "The TTL from the DNS response." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1386 +msgid "The internal timeout value." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1387 +msgid "" +"The smaller of the DNS and internal TTL values. The internal timeout value " +"becomes a maximum TTL." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1388 +msgid "" +"The larger of the DNS and internal TTL values. The internal timeout value " +"become a minimum TTL." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1395 +msgid "Internal time to live value for host DB entries, **in minutes**." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1397 +msgid "See :ts:cv:`proxy.config.hostdb.ttl_mode` for when this value is used." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1402 +msgid "Set host resolution to use strict round robin." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1404 +msgid "" +"When this and :ts:cv:`proxy.config.hostdb.timed_round_robin` are both " +"disabled (set to ``0``), Traffic Server always uses the same origin server " +"for the same client, for as long as the origin server is available. " +"Otherwise if this is set then IP address is rotated on every request. This " +"setting takes precedence over " +":ts:cv:`proxy.config.hostdb.timed_round_robin`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1412 +msgid "Set host resolution to use timed round robin." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1414 +msgid "" +"When this and :ts:cv:`proxy.config.hostdb.strict_round_robin` are both " +"disabled (set to ``0``), Traffic Server always uses the same origin server " +"for the same client, for as long as the origin server is available. " +"Otherwise if this is set to :arg:`N` the IP address is rotated if more than " +":arg:`N` seconds have past since the first time the current address was " +"used." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1421 +msgid "Set the host resolution style." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1423 +msgid "" +"This is an ordered list of keywords separated by semicolons that specify how" +" a host name is to be resolved to an IP address. The keywords are case " +"insensitive." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1427 +msgid "Keyword" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1427 +msgid "Meaning" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1429 +msgid "Resolve to an IPv4 address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1430 +msgid "Resolve to an IPv6 address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1431 +msgid "client" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1431 +msgid "Resolve to the same family as the client IP address." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1432 +msgid "none" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1432 +msgid "Stop resolving." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1435 +msgid "" +"The order of the keywords is critical. When a host name needs to be resolved" +" it is resolved in same order as the keywords. If a resolution fails, the " +"next option in the list is tried. The keyword ``none`` means to give up " +"resolution entirely. The keyword list has a maximum length of three " +"keywords, more are never needed. By default there is an implicit " +"``ipv4;ipv6`` attached to the end of the string unless the keyword ``none`` " +"appears." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1442 +msgid "Use the incoming client family, then try IPv4 and IPv6. ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1446 +msgid "" +"Because of the implicit resolution this can also be expressed as just ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1452 +msgid "Resolve only to IPv4. ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1458 +msgid "" +"Resolve only to the same family as the client (do not permit cross family " +"transactions). ::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1462 +msgid "" +"This value is a global default that can be overridden by " +":ts:cv:`proxy.config.http.server_ports`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1466 +msgid "" +"This style is used as a convenience for the administrator. During a " +"resolution the *resolution order* will be one family, then possibly the " +"other. This is determined by changing ``client`` to ``ipv4`` or ``ipv6`` " +"based on the client IP address and then removing duplicates." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1472 +msgid "" +"This option has no effect on outbound transparent connections The local IP " +"address used in the connection to the origin server is determined by the " +"client, which forces the IP address family of the address used for the " +"origin server. In effect, outbound transparent connections always use a " +"resolution style of \"``client``\"." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1477 +msgid "Logging Configuration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1482 +msgid "Enables and disables event logging:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1484 +msgid "``0`` = logging disabled" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1485 +msgid "``1`` = log errors only" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1486 +msgid "``2`` = log transactions only" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1487 +msgid "``3`` = full logging (errors + transactions)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1489 +msgid "Refer to :ref:`working-with-log-files`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1494 +msgid "" +"The maximum amount of time before data in the buffer is flushed to disk." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1500 +msgid "The amount of space allocated to the logging directory (in MB)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1504 +msgid "" +"All files in the logging directory contribute to the space used, even if " +"they are not log files. In collation client mode, if there is no local disk " +"logging, or :ts:cv:`proxy.config.log.max_space_mb_for_orphan_logs` is set to" +" a higher value than :ts:cv:`proxy.config.log.max_space_mb_for_logs`, TS " +"will take :ts:cv:`proxy.config.log.max_space_mb_for_orphan_logs` for maximum" +" allowed log space." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1513 +msgid "" +"The amount of space allocated to the logging directory (in MB) if this node " +"is acting as a collation client." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1517 +msgid "" +"When max_space_mb_for_orphan_logs is take as the maximum allowedlog space in" +" the logging system, the same rule apply to " +"proxy.config.log.max_space_mb_for_logs also apply to " +"proxy.config.log.max_space_mb_for_orphan_logs, ie: All files in the logging " +"directory contribute to the space used, even if they are not log files. you " +"may need to consider this when you enable full remote logging, and bump to " +"the same size as proxy.config.log.max_space_mb_for_logs." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1526 +msgid "" +"The tolerance for the log space limit (in megabytes). If the variable " +":ts:cv:`proxy.config.log.auto_delete_rolled_files` is set to ``1`` " +"(enabled), then autodeletion of log files is triggered when the amount of " +"free space available in the logging directory is less than the value " +"specified here." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1533 +msgid "The hostname of the machine running Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1538 +msgid "" +"The full path to the logging directory. This can be an absolute path or a " +"path relative to the directory in which Traffic Server is installed." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1540 +msgid "The directory you specify must already exist." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1545 +msgid "" +"The log file permissions. The standard UNIX file permissions are used " +"(owner, group, other). Permissible values are:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1547 +msgid "" +"``-`` no permission ``r`` read permission ``w`` write permission ``x`` " +"execute permission" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1549 +msgid "" +"Permissions are subject to the umask settings for the Traffic Server " +"process. This means that a umask setting of\\ ``002`` will not allow write " +"permission for others, even if specified in the configuration file. " +"Permissions for existing log files are not changed when the configuration is" +" changed." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1556 +msgid "Enables (``1``) or disables (``0``) custom logging." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1561 +msgid "" +"Enables (``1``) or disables (``0``) the `squid log file format <../working-" +"log-files/log-formats#SquidFormat>`_." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1566 +msgid "The squid log file type:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1568 +#: ../../reference/configuration/records.config.en.rst:1590 +#: ../../reference/configuration/records.config.en.rst:1612 +#: ../../reference/configuration/records.config.en.rst:1638 +msgid "``1`` = ASCII" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1569 +#: ../../reference/configuration/records.config.en.rst:1591 +#: ../../reference/configuration/records.config.en.rst:1613 +#: ../../reference/configuration/records.config.en.rst:1639 +msgid "``0`` = binary" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1574 +msgid "" +"The `squid log <../working-log-files/log-formats#SquidFormat>`_ filename." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1578 +msgid "" +"The `squid log <../working-log-files/log-formats#SquidFormat>`_ file header " +"text." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1583 +msgid "" +"Enables (``1``) or disables (``0``) the `Netscape common log file format " +"<../working-log-files/log-formats#NetscapeFormats>`_." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1588 +msgid "" +"The `Netscape common log <../working-log-files/log-" +"formats#NetscapeFormats>`_ file type:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1596 +msgid "" +"The `Netscape common log <../working-log-files/log-" +"formats#NetscapeFormats>`_ filename." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1601 +msgid "" +"The `Netscape common log <../working-log-files/log-" +"formats#NetscapeFormats>`_ file header text." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1606 +msgid "" +"Enables (``1``) or disables (``0``) the `Netscape extended log file format " +"<../working-log-files/log-formats#NetscapeFormats>`_." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1610 +msgid "" +"The `Netscape extended log <../working-log-files/log-" +"formats#NetscapeFormats>`_ file type:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1617 +msgid "" +"The `Netscape extended log <../working-log-files/log-" +"formats#NetscapeFormats>`_ filename." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1622 +msgid "" +"The `Netscape extended log <../working-log-files/log-" +"formats#NetscapeFormats>`_ file header text." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1626 +msgid "Set whether the extend log is written as ASCII (text) or binary." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1631 +msgid "" +"Enables (``1``) or disables (``0``) the `Netscape Extended-2 log file format" +" <../working-log-files/log-formats#NetscapeFormats>`_." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1636 +msgid "" +"The `Netscape Extended-2 log <../working-log-files/log-" +"formats#NetscapeFormats>`_ file type:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1644 +msgid "" +"The `Netscape Extended-2 log <../working-log-files/log-" +"formats#NetscapeFormats>`_ filename." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1649 +msgid "" +"The `Netscape Extended-2 log <../working-log-files/log-" +"formats#NetscapeFormats>`_ file header text." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1654 +msgid "" +"When enabled (``1``), configures Traffic Server to store ICP transactions in" +" a separate log file." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1656 +msgid "" +"``0`` = separation is disabled, all ICP transactions are recorded in the " +"same file as HTTP transactions" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1657 +msgid "``1`` = all ICP transactions are recorded in a separate log file." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1658 +msgid "" +"``-1`` = filter all ICP transactions from the default log files; ICP " +"transactions are not logged anywhere." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1663 +msgid "" +"When enabled (``1``), configures Traffic Server to create a separate log " +"file for HTTP transactions for each origin server listed in the " +":file:`log_hosts.config` file. Refer to `HTTP Host Log Splitting " +"<../working-log-files#HTTPHostLogSplitting>`_." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1669 +msgid "Set the log collation mode." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1674 +msgid "collation is disabled" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1675 +msgid "this host is a log collation server" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1676 +msgid "" +"this host is a collation client and sends entries using standard formats to " +"the collation server" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1677 +msgid "" +"this host is a collation client and sends entries using the traditional " +"custom formats to the collation server" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1678 +msgid "4" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1678 +msgid "" +"this host is a collation client and sends entries that use both the standard" +" and traditional custom formats to the collation server" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1681 +msgid "" +"For information on sending XML-based custom formats to the collation server," +" refer to `logs_xml.config `_." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1684 +msgid "" +"Although Traffic Server supports traditional custom logging, you should use " +"the more versatile XML-based custom formats." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1688 +msgid "The hostname of the log collation server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1693 +msgid "" +"The port used for communication between the collation server and client." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1698 +msgid "" +"The password used to validate logging data and prevent the exchange of " +"unauthorized information when a collation server is being used." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1703 +msgid "" +"When enabled (``1``), configures Traffic Server to include the hostname of " +"the collation client that generated the log entry in each entry." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1708 +msgid "The number of seconds between collation server connection retries." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1713 +msgid "" +"Specifies how log files are rolled. You can specify the following values:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1715 +msgid "``0`` = disables log file rolling" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1716 +msgid "" +"``1`` = enables log file rolling at specific intervals during the day " +"(specified with the" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1717 +msgid "" +"`proxy.config.log.rolling_interval_sec`_ and " +"`proxy.config.log.rolling_offset_hr`_ variables)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1718 +msgid "" +"``2`` = enables log file rolling when log files reach a specific size " +"(specified with the `proxy.config.log.rolling_size_mb`_ variable)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1719 +msgid "" +"``3`` = enables log file rolling at specific intervals during the day or " +"when log files reach a specific size (whichever occurs first)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1720 +msgid "" +"``4`` = enables log file rolling at specific intervals during the day when " +"log files reach a specific size (i.e., at a specified" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1721 +msgid "time if the file is of the specified size)" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1726 +msgid "" +"The log file rolling interval, in seconds. The minimum value is ``300`` (5 " +"minutes). The maximum, and default, value is 86400 seconds (one day)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1728 +msgid "" +"If you start Traffic Server within a few minutes of the next rolling time, " +"then rolling might not occur until the next rolling time." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1733 +msgid "" +"The file rolling offset hour. The hour of the day that starts the log " +"rolling period." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1738 +msgid "The size that log files must reach before rolling takes place." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1743 +msgid "" +"Enables (``1``) or disables (``0``) automatic deletion of rolled files." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1748 +msgid "" +"Configures Traffic Server to log only a sample of transactions rather than " +"every transaction. You can specify the following values:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1750 +msgid "``1`` = log every transaction" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1751 +msgid "``2`` = log every second transaction" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1752 +msgid "``3`` = log every third transaction and so on..." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1758 +msgid "" +"If set to a non-zero value :arg:`N` then any connection that takes longer " +"than :arg:`N` milliseconds from accept to completion will cause its timing " +"stats to be written to the :ts:cv:`debugging log file " +"`. This is identifying data about the " +"transaction and all of the :c:type:`transaction milestones " +"`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1763 +msgid "Diagnostic Logging Configuration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1771 +msgid "" +"control where Traffic Server should log diagnostic output. Messages at " +"diagnostic level can be directed to any combination of diagnostic " +"destinations. Valid diagnostic message destinations are:::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1781 +msgid "To log debug diagnostics to both syslog and diags.log:::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1786 +msgid "Reverse Proxy" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1791 +msgid "Enables (``1``) or disables (``0``) HTTP reverse proxy." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1796 +msgid "" +"The URL to which to redirect requests with no host headers (reverse proxy)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1800 +msgid "URL Remap Rules" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1804 +msgid "Sets the name of the :file:`remap.config` file." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1809 +msgid "" +"Enables (``1``) or disables (``0``) requests for a PAC file on the proxy " +"service port (8080 by default) to be redirected to the PAC port. For this " +"type of redirection to work, the variable " +"`proxy.config.reverse_proxy.enabled`_ must be set to ``1``." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1815 +msgid "" +"Sets the PAC port so that PAC requests made to the Traffic Server proxy " +"service port are redirected this port. ``-1`` is the default setting that " +"sets the PAC port to the autoconfiguration port (the default " +"autoconfiguration port is 8083). This variable can be used together with the" +" `proxy.config.url_remap.default_to_server_pac`_ variable to get a PAC file " +"from a different port. You must create and run a process that serves a PAC " +"file on this port. For example: if you create a Perl script that listens on " +"port 9000 and writes a PAC file in response to any request, then you can set" +" this variable to ``9000``. Browsers that request the PAC file from a proxy " +"server on port 8080 will get the PAC file served by the Perl script." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1830 +msgid "" +"Set this variable to ``1`` if you want Traffic Server to serve requests only" +" from origin servers listed in the mapping rules of the :file:`remap.config`" +" file. If a request does not match, then the browser will receive an error." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1838 +msgid "" +"Set this variable to ``1`` if you want to retain the client host header in a" +" request during remapping." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1844 +msgid "SSL Termination" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1848 +msgid "Enables (``1``) or disables (``0``) SSLv2. Please don't enable it." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1852 +msgid "Enables (``1``) or disables (``0``) SSLv3." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1856 +msgid "Enables (``1``) or disables (``0``) TLSv1." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1860 +msgid "Sets the client certification level:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1865 +msgid "``0`` = no client certificates are required. Traffic Server does" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1863 +msgid "" +"not verify client certificates during the SSL handshake. Access to Traffic " +"Server depends on Traffic Server configuration options (such as access " +"control lists)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1871 +msgid "``1`` = client certificates are optional. If a client has a" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1868 +msgid "" +"certificate, then the certificate is validated. If the client does not have " +"a certificate, then the client is still allowed access to Traffic Server " +"unless access is denied through other Traffic Server configuration options." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1874 +msgid "``2`` = client certificates are required. The client must be" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1874 +msgid "" +"authenticated during the SSL handshake. Clients without a certificate are " +"not allowed to access Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1879 +msgid "" +"The location of the :file:`ssl_multicert.config` file, relative to the " +"Traffic Server configuration directory. In the following example, if the " +"Traffic Server configuration directory is `/etc/trafficserver`, the Traffic " +"Server SSL configuration file and the corresponding certificates are located" +" in `/etc/trafficserver/ssl`::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1892 +msgid "" +"The location of the SSL certificates and chains used for accepting and " +"validation new SSL sessions. If this is a relative path, it is appended to " +"the Traffic Server installation PREFIX. All certificates and certificate " +"chains listed in :file:`ssl_multicert.config` will be loaded relative to " +"this path." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1900 +msgid "" +"The location of the SSL certificate private keys. Change this variable only " +"if the private key is not located in the SSL certificate file. All private " +"keys listed in :file:`ssl_multicert.config` will be loaded relative to this " +"path." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1908 +msgid "" +"The name of a file containing a global certificate chain that should be used" +" with every server certificate. This file is only used if there are " +"certificates defined in :file:`ssl_multicert.config`. Unless this is an " +"absolute path, it is loaded relative to the path specified by " +":ts:cv:`proxy.config.ssl.server.cert.path`." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1916 +msgid "" +"The location of the certificate authority file that client certificates will" +" be verified against." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1921 +msgid "" +"The filename of the certificate authority that client certificates will be " +"verified against." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1926 +msgid "TBD" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1929 +msgid "Client-Related Configuration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1933 +msgid "" +"Configures Traffic Server to verify the origin server certificate with the " +"Certificate Authority (CA)." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1938 +msgid "The filename of SSL client certificate installed on Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1942 +msgid "" +"The location of the SSL client certificate installed on Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1947 +msgid "" +"The filename of the Traffic Server private key. Change this variable only if" +" the private key is not located in the Traffic Server SSL client certificate" +" file." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1953 +msgid "" +"The location of the Traffic Server private key. Change this variable only if" +" the private key is not located in the SSL client certificate file." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1959 +msgid "" +"The filename of the certificate authority against which the origin server " +"will be verified." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1964 +msgid "" +"Specifies the location of the certificate authority file against which the " +"origin server will be verified." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1968 +msgid "ICP Configuration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1972 +msgid "Sets ICP mode for hierarchical caching:" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1974 +msgid "``0`` = disables ICP" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1975 +msgid "``1`` = allows Traffic Server to receive ICP queries only" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1976 +msgid "``2`` = allows Traffic Server to send and receive ICP queries" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1978 +msgid "Refer to `ICP Peering <../hierachical-caching#ICPPeering>`_." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1982 +msgid "Specifies the network interface used for ICP traffic." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1986 +msgid "" +"The Traffic Server installation script detects your network interface and " +"sets this variable appropriately. If your system has multiple network " +"interfaces, check that this variable specifies the correct interface." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1994 +msgid "Specifies the UDP port that you want to use for ICP messages." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:1999 +msgid "Specifies the timeout used for ICP queries." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2002 +msgid "Scheduled Update Configuration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2006 +msgid "Enables (``1``) or disables (``0``) the Scheduled Update option." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2011 +msgid "" +"Enables (``1``) or disables (``0``) a force immediate update. When enabled, " +"Traffic Server overrides the scheduling expiration time for all scheduled " +"update entries and initiates updates until this option is disabled." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2019 +msgid "" +"Specifies the number of times Traffic Server can retry the scheduled update " +"of a URL in the event of failure." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2025 +msgid "" +"Specifies the delay (in seconds) between each scheduled update retry for a " +"URL in the event of failure." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2031 +msgid "" +"Specifies the maximum simultaneous update requests allowed at any time. This" +" option prevents the scheduled update process from overburdening the host." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2036 +msgid "Remap Plugin Processor" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2040 +msgid "" +"Enables (``1``) or disables (``0``) the ability to run separate threads for " +"remap plugin processing." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2044 +msgid "" +"Specifies the number of threads that will be used for remap plugin " +"rocessing." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2047 +msgid "Plug-in Configuration" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2051 +msgid "Specifies the location of Traffic Server plugins." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2054 +msgid "Sockets" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2058 +msgid "" +"default: ``1`` meaning ``on`` all Platforms except Linux: ``45`` seconds" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2060 +msgid "" +"This directive enables operating system specific optimizations for a " +"listening socket. ``defer_accept`` holds a call to ``accept(2)`` back until " +"data has arrived. In Linux' special case this is up to a maximum of 45 " +"seconds." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2065 +msgid "" +"Sets the send buffer size for connections from the client to Traffic Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2069 +msgid "" +"Sets the receive buffer size for connections from the client to Traffic " +"Server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2073 +msgid "" +"Turns different options \"on\" for the socket handling client connections:::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2080 +#: ../../reference/configuration/records.config.en.rst:2102 +msgid "" +"This is a flag and you look at the bits set. Therefore, you must set the " +"value to ``3`` if you want to enable both options above." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2086 +msgid "" +"Sets the send buffer size for connections from Traffic Server to the origin " +"server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2090 +msgid "" +"Sets the receive buffer size for connections from Traffic Server to the " +"origin server." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2095 +msgid "Turns different options \"on\" for the origin server socket:::" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2108 +msgid "" +"Same as the command line option ``--accept_mss`` that sets the MSS for all " +"incoming requests." +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2111 +msgid "Undocumented" +msgstr "" + +#: ../../reference/configuration/records.config.en.rst:2113 +msgid "" +"These are referenced but not documented. Please contribute a definition." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/remap.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/remap.config.en.po new file mode 100644 index 00000000000..32642ce99f2 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/remap.config.en.po @@ -0,0 +1,441 @@ +# +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/remap.config.en.rst:20 +msgid "remap.config" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:28 +msgid "" +"The :file:`remap.config` file contains mapping rules that Traffic Server " +"uses to perform the following actions:" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:31 +msgid "" +"Map URL requests for a specific origin server to the appropriate location on" +" Traffic Server when Traffic Server acts as a reverse proxy for that " +"particular origin server" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:34 +msgid "" +"Reverse-map server location headers so that when origin servers respond to a" +" request with a location header that redirects the client to another " +"location, the clients do not bypass Traffic Server" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:37 +msgid "" +"Redirect HTTP requests permanently or temporarily without Traffic Server " +"having to contact any origin servers" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:40 +msgid "" +"Refer to :ref:`reverse-proxy-and-http-redirects`, for information about " +"redirecting HTTP requests and using reverse proxy." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:43 +msgid "" +"After you modify the :file:`remap.config` run the :option:`traffic_line -x` " +"to apply the changes. When you apply the changes to one node in a cluster, " +"Traffic Server automatically applies the changes to all other nodes in the " +"cluster." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:49 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:51 +msgid "" +"Each line in the :file:`remap.config` file must contain a mapping rule. " +"Empty lines, or lines starting with ``#`` are ignored. Each line can be " +"broken up into multiple lines for better readability by using ``\\`` as " +"continuation marker." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:55 +msgid "" +"Traffic Server recognizes three space-delimited fields: ``type``, " +"``target``, and ``replacement``. The following list describes the format of " +"each field." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:79 +msgid "``type``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:61 +msgid "Enter one of the following:" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:63 +msgid "" +"``map`` --translates an incoming request URL to the appropriate origin " +"server URL." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:66 +msgid "" +"``reverse_map`` --translates the URL in origin server redirect responses to " +"point to the Traffic Server." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:69 +msgid "" +"``redirect`` --redirects HTTP requests permanently without having to contact" +" the origin server. Permanent redirects notify the browser of the URL change" +" (by returning an HTTP status code 301) so that the browser can update " +"bookmarks." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:74 +msgid "" +"``redirect_temporary`` --redirects HTTP requests temporarily without having " +"to contact the origin server. Temporary redirects notify the browser of the " +"URL change for the current request only (by returning an HTTP status code " +"307)." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:88 +msgid "``target``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:84 +#: ../../reference/configuration/remap.config.en.rst:93 +msgid "Enter the origin (\"from\") URL. You can enter up to four components: ::" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:88 +msgid "where ``scheme`` is ``http``." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:98 +msgid "``replacement``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:97 +msgid "where ``scheme`` can be ``http`` or ``https``." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:103 +msgid "Precedence" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:105 +msgid "" +"Remap rules are not processed top-down, but based on an internal priority" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:108 +msgid "``map`` and ``reverse_map``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:109 +msgid "``regex_map``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:110 +msgid "``redirect`` and ``redirect_temporary``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:111 +msgid "``regex_redirect`` and ``regex_redirect_temporary``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:115 +msgid "Match-All" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:117 +msgid "" +"A map rule with a single ``/`` acts as a wildcard, it will match any " +"request. This should be use with care, and certainly only once at the end of" +" the remap.config file. E.g." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:126 +#: ../../reference/configuration/remap.config.en.rst:266 +#: ../../reference/configuration/remap.config.en.rst:283 +#: ../../reference/configuration/remap.config.en.rst:306 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:128 +msgid "" +"The following section shows example mapping rules in the " +":file:`remap.config` file." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:132 +msgid "Reverse Proxy Mapping Rules" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:134 +msgid "" +"The following example shows a map rule that does not specify a path prefix " +"in the target or replacement: ::" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:140 +msgid "This rule results in the following translations:" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:143 +#: ../../reference/configuration/remap.config.en.rst:164 +#: ../../reference/configuration/remap.config.en.rst:181 +#: ../../reference/configuration/remap.config.en.rst:200 +#: ../../reference/configuration/remap.config.en.rst:214 +#: ../../reference/configuration/remap.config.en.rst:222 +msgid "Client Request" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:143 +#: ../../reference/configuration/remap.config.en.rst:164 +#: ../../reference/configuration/remap.config.en.rst:181 +#: ../../reference/configuration/remap.config.en.rst:200 +#: ../../reference/configuration/remap.config.en.rst:214 +#: ../../reference/configuration/remap.config.en.rst:222 +msgid "Translated Request" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:145 +msgid "``http://www.x.com/Widgets/index.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:145 +msgid "``http://server.hoster.com/Widgets/index.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:146 +msgid "``http://www.x.com/cgi/form/submit.sh?arg=true``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:146 +msgid "``http://server.hoster.com/cgi/form/submit.sh?arg=true``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:149 +msgid "" +"The following example shows a map rule with path prefixes specified in the " +"target: ::" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:161 +msgid "These rules result in the following translations:" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:166 +msgid "``http://www.y.com/marketing/projects/manhattan/specs.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:166 +msgid "``http://marketing.y.com/projects/manhattan/specs.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:167 +msgid "``http://www.y.com/stuff/marketing/projects/boston/specs.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:167 +msgid "``http://info.y.com/marketing/projects/boston/specs.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:168 +msgid "``http://www.y.com/engineering/marketing/requirements.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:168 +msgid "``http://engineering.y.com/marketing/requirements.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:171 +msgid "The following example shows that the order of the rules matters: ::" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:178 +msgid "These rules result in the following translation." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:183 +msgid "``http://www.g.com/stuff/a.gif``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:183 +msgid "``http://external.g.com/stuff/a.gif``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:186 +msgid "" +"In the above examples, the second rule is never applied because all URLs " +"that match the second rule also match the first rule. The first rule takes " +"precedence because it appears earlier in the :file:`remap.config` file." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:191 +msgid "" +"The following example shows a mapping with a path prefix specified in the " +"target and replacement::" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:197 +msgid "This rule results in the following translation." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:202 +msgid "``http://www.h.com/a/b/c/d/doc.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:202 +msgid "``http://server.h.com/customers/x/y/c/d/doc.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:203 +msgid "``http://www.h.com/a/index.html``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:203 +msgid "``Translation fails``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:206 +msgid "The following example shows reverse-map rules::" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:211 +msgid "These rules result in the following translations." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:216 +#: ../../reference/configuration/remap.config.en.rst:224 +msgid "``http://www.x.com/Widgets``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:216 +msgid "``http://server.hoster.com/x/Widgets``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:222 +msgid "Origin Server Header" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:224 +msgid "``http://server.hoster.com/x/Widgets/``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:224 +msgid "``http://www.x.com/Widgets/``" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:227 +msgid "" +"When acting as a reverse proxy for multiple servers, Traffic Server is " +"unable to route to URLs from older browsers that do not send the ``Host:`` " +"header. As a solution, set the variable " +":ts:cv:`proxy.config.header.parse.no_host_url_redirect` in the " +":file:`records.config` file to the URL to which Traffic Server will redirect" +" requests without host headers." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:234 +msgid "Redirect Mapping Rules" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:236 +msgid "" +"The following rule permanently redirects all HTTP requests for " +"``www.company.com`` to ``www.company2.com``: ::" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:241 +msgid "" +"The following rule *temporarily* redirects all HTTP requests for " +"``www.company1.com`` to ``www.company2.com``: ::" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:249 +msgid "Regular Expression (regex) Remap Support" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:251 +msgid "" +"Regular expressions can be specified in remapping rules, with the " +"limitations below:" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:254 +msgid "" +"Only the ``host`` field can contain a regex; the ``scheme``, ``port``, and " +"other fields cannot. For path manipulation via regexes, use the " +"``regex_remap`` plugin." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:257 +msgid "" +"The number of capturing subpatterns is limited to 9. This means that ``$0`` " +"through ``$9`` can be used as subtraction placeholders (``$0`` will be the " +"entire input string)." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:260 +msgid "The number of substitutions in the expansion string is limited to 10." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:261 +msgid "" +"There is no ``regex_`` equivalent to ``reverse_remap``, so when using " +"``regex_remap`` you should make sure the reverse path is clear by setting " +"(:ts:cv:`proxy.config.url_remap.pristine_host_hdr`)" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:276 +msgid "Plugin Chaining" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:278 +msgid "" +"Plugins can be configured to be evaluated in a specific order, passing the " +"results from one in to the next (unless a plugin returns 0, then the " +"\"chain\" is broken)." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:289 +msgid "will pass \"1\" and \"2\" to plugin1.so and \"3\" to plugin2.so." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:291 +msgid "This will pass \"1\" and \"2\" to plugin1.so and \"3\" to plugin2.so" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:296 +msgid "Named Filters" +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:298 +msgid "" +"Named filters can be created and applied to blocks of mappings using the " +"``.definefilter``, ``.activatefilter``, and ``.deactivatefilter`` " +"directives. Named filters must be defined using ``.definefilter`` before " +"being used. Once defined, ``.activatefilter`` can used to activate a filter " +"for all mappings that follow until deactivated with ``.deactivatefilter``." +msgstr "" + +#: ../../reference/configuration/remap.config.en.rst:323 +msgid "" +"The filter `disable_delete_purge` will be applied to all of the mapping " +"rules. (It is activated before any mappings and is never deactivated.) The " +"filter `internal_only` will only be applied to the second mapping." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/splitdns.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/splitdns.config.en.po new file mode 100644 index 00000000000..919a80c0f61 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/splitdns.config.en.po @@ -0,0 +1,180 @@ +# +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/splitdns.config.en.rst:20 +msgid "splitdns.config" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:24 +msgid "" +"The :file:`splitdns.config` file enables you to specify the DNS server that " +"Traffic Server should use for resolving hosts under specific conditions. For" +" more information, refer to :ref:`configuring-dns-server-selection-split-" +"dns`." +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:28 +msgid "" +"To specify a DNS server, you must supply the following information in each " +"active line within the file:" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:31 +msgid "" +"A primary destination specifier in the form of a destination domain, a " +"destination host, or a URL regular expression" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:33 +msgid "" +"A set of server directives, listing one or more DNS servers with " +"corresponding port numbers" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:36 +msgid "" +"You can also include the following optional information with each DNS server" +" specification:" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:39 +msgid "A default domain for resolving hosts" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:40 +msgid "" +"A search list specifying the domain search order when multiple domains are " +"specified" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:43 +msgid "" +"After you modify the :file:`splitdns.config` file, run the " +":option:`traffic_line -x` command to apply the changes. When you apply " +"changes to a node in a cluster, Traffic Server automatically applies the " +"changes to all other nodes in the cluster." +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:50 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:52 +msgid "" +"Each line in the :file:`splitdns.config` file uses one of the following " +"formats: ::" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:57 +msgid "The following list describes each field." +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:64 +msgid "``dest_domain``" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:62 +msgid "" +"A valid domain name. This specifies that DNS server selection will be based " +"on the destination domain. You can prefix the domain with an exclamation " +"mark (``!``) to indicate the NOT logical operator." +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:71 +msgid "``dest_host``" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:69 +msgid "" +"A valid hostname. This specifies that DNS server selection will be based on " +"the destination host. You can prefix the host with an exclamation mark " +"(``!``) to indicate the ``NOT`` logical operator." +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:77 +msgid "``url_regex``" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:76 +msgid "" +"A valid URL regular expression. This specifies that DNS server selection " +"will be based on a regular expression." +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:89 +msgid "``dns_server``" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:82 +msgid "" +"This is a required directive. It identifies the DNS server that Traffic " +"Server should use with the given destination specifier. You can specify a " +"port using a colon (``:``). If you do not specify a port, then 53 is used. " +"Specify multiple DNS servers with spaces or semicolons (``;``) as " +"separators." +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:88 +msgid "You must specify the domains with IP addresses in CIDR (\"dot\") notation." +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:97 +msgid "``def_domain``" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:94 +msgid "" +"A valid domain name. This optional directive specifies the default domain " +"name to use for resolving hosts. Only one entry is allowed. If you do not " +"provide the default domain, the system determines its value from " +"``/etc/resolv.conf``" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:104 +msgid "``search_list``" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:102 +msgid "" +"A list of domains separated by spaces or semicolons (;). This specifies the " +"domain search order. If you do not provide the search list, the system " +"determines the value from :manpage:`resolv.conf(5)`" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:107 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:109 +msgid "Consider the following DNS server selection specifications: ::" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:114 +msgid "Now consider the following two requests: ::" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:118 +msgid "" +"This request matches the first line and therefore selects DNS server " +"``255.255.255.255`` on port ``212``. All resolver requests use " +"``company.com`` as the default domain, and ``company.com`` and " +"``company1.com`` as the set of domains to search first. ::" +msgstr "" + +#: ../../reference/configuration/splitdns.config.en.rst:125 +msgid "" +"This request matches the second line. Therefore, Traffic Server selects DNS " +"server ``255.255.255.253``. Because no ``def_domain`` or ``search_list`` was" +" supplied, Traffic Server retrieves this information from " +":manpage:`resolv.conf(5)`" +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/ssl_multicert.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/ssl_multicert.config.en.po new file mode 100644 index 00000000000..11810fbca45 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/ssl_multicert.config.en.po @@ -0,0 +1,154 @@ +# +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/ssl_multicert.config.en.rst:20 +msgid "ssl_multicert.config" +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:24 +msgid "" +"The :file:`ssl_multicert.config` file lets you configure Traffic Server to " +"use multiple SSL server certificates to terminate the SSL sessions. If you " +"have a Traffic Server system with more than one IP address assigned to it, " +"then you can assign a different SSL certificate to be served when a client " +"requests a particular IP address or host name." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:31 +msgid "" +"At configuration time, certificates are parsed to extract the certificate " +"subject and all the DNS `subject alternative names " +"`_. A certificate will be " +"presented for connections requesting any of the hostnames found in the " +"certificate. Wildcard names are supported, but only of the form " +"`*.domain.com`, ie. where `*` is the leftmost domain component." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:39 +msgid "" +"Changes to :file:`ssl_multicert.config` can be applied to a running Traffic " +"Server using :option:`traffic_line -x`." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:43 +msgid "Format" +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:45 +msgid "" +"Each :file:`ssl_multicert.config` line consists of a sequence of `key=value`" +" fields that specify how Traffic Server should use a particular SSL " +"certificate." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:53 +msgid "ssl_cert_name=PATH" +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:50 +msgid "" +"The name of the file containing the TLS certificate. `PATH` is located " +"relative to the directory specified by the " +":ts:cv:`proxy.config.ssl.server.cert.path` configuration variable. This is " +"the only field that is required to be present." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:64 +msgid "dest_ip=ADDRESS" +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:56 +msgid "" +"The IP (v4 or v6) address that the certificate should be presented on. This " +"is now only used as a fallback in the case that the TLS " +"SubjectNameIndication extension is not supported. If `ADDRESS` is `*`, the " +"corresponding certificate will be used as the global default fallback if no " +"other match can be made. The address may contain a port specifier, in which" +" case the corresponding certificate will only match for connections accepted" +" on the specified port. IPv6 addresses must be enclosed by square brackets " +"if they have a port, eg, [::1]:80." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:70 +msgid "ssl_key_name=PATH" +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:67 +msgid "" +"The name of the file containing the private key for this certificate. If the" +" key is contained in the certificate file, this field can be omitted, " +"otherwise `PATH` is resolved relative to the " +":ts:cv:`proxy.config.ssl.server.private_key.path` configuration variable." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:76 +msgid "ssl_ca_name=FILENAME" +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:73 +msgid "" +"If the certificate is issued by an authority that is not in the system CA " +"bundle, additional certificates may be needed to validate the certificate " +"chain. `PATH` is resolved relative to the " +":ts:cv:`proxy.config.ssl.CA.cert.path` configuration variable." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:79 +msgid "Certificate Selection" +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:81 +msgid "" +"Traffic Server attempts two certificate selections during SSL connection " +"setup. An initial selection is made when a TCP connection is accepted. This " +"selection examines the IP address and port that the client is connecting to " +"and chooses the best certificate from the those that have a ``dest_ip`` " +"specification. If no matching certificates are found, a default certificate " +"is chosen. The final certificate selection is made during the SSL " +"handshake. At this point, the client may use `Server Name Indication " +"`_ to request a " +"specific hostname. Traffic Server will use this request to select a " +"certificate with a matching subject or subject alternative name. Failing " +"that, a wildcard certificate match is attempted. If no match can be made, " +"the initial certificate selection remains in force." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:95 +msgid "" +"In all cases, Traffic Server attempts to select the most specific match. An " +"address specification that contains a port number will take precedence over " +"a specification that does not contain a port number. A specific certificate " +"subject will take precedence over a wildcard certificate." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:103 +msgid "Examples" +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:105 +msgid "" +"The following example configures Traffic Server to use the SSL certificate " +"``server.pem`` for all requests to the IP address 111.11.11.1 and the SSL " +"certificate ``server1.pem`` for all requests to the IP address 11.1.1.1. " +"Connections from all other IP addresses are terminated with the " +"``default.pem`` certificate. Since the private key is included in the " +"certificate files, no private key name is specified." +msgstr "" + +#: ../../reference/configuration/ssl_multicert.config.en.rst:119 +msgid "" +"The following example configures Traffic Server to use the SSL certificate " +"``server.pem`` and the private key ``serverKey.pem`` for all requests to " +"port 8443 on IP address 111.11.11.1. The ``general.pem`` certificate is used" +" for server name matches." +msgstr "" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/storage.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/storage.config.en.po new file mode 100644 index 00000000000..25ea9d28ed7 --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/storage.config.en.po @@ -0,0 +1,239 @@ +# +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-13 01:18+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/configuration/storage.config.en.rst:20 +msgid "storage.config" +msgstr "" + +#: ../../reference/configuration/storage.config.en.rst:24 +msgid "" +"The :file:`storage.config` file lists all the files, directories, and/or " +"hard disk partitions that make up the Traffic Server cache. After you modify" +" the :file:`storage.config` file, you must restart Traffic Server." +msgstr "" +":file:`storage.config` ファむルは、Traffic Serverのキャッシュずしお構成する" +"党おのファむル、ディレクトリやハヌドディスクパヌティションを列挙したす。" +":file:`storage.config` ファむル修正埌は、Traffic Server を再起動しなければ" +"いけたせん。" + +#: ../../reference/configuration/storage.config.en.rst:29 +msgid "Format" +msgstr "フォヌマット" + +#: ../../reference/configuration/storage.config.en.rst:31 +msgid "The format of the :file:`storage.config` file is::" +msgstr ":file:`storage.config` ファむルのフォヌマットは::" + +#: ../../reference/configuration/storage.config.en.rst:35 +msgid "" +"where :arg:`pathname` is the name of a partition, directory or file, " +":arg:`size` is the size of the named partition, directory or file (in " +"bytes), and :arg:`volume` is the volume number that is used in " +":file:`volume.config` and :file:`hosting.config`. You must specify a size " +"for directories or files; size is optional for raw partitions. :arg:`volume`" +" is optional." +msgstr "" +"``pathname`` にはパヌティションやディレクトリ、ファむルの名前を蚘述したす。" +"``size`` には名前を付けたパヌティション、ディレクトリやファむルのサむズを" +"(バむト単䜍で)指定したす。" +"``volume`` には :file:`volume.config` ず :file:`hosting.config` で䜿甚されおいる" +"ボリュヌム番号を指定したす。" +"ディレクトリやファむルはサむズを指定しなければいけたせん。" +"ロヌパヌティションに぀いおは任意です。" +"``volume`` は任意です。" + +#: ../../reference/configuration/storage.config.en.rst:41 +msgid "You can use any partition of any size. For best performance:" +msgstr "" +"どんなサむズのどんなパヌティションでも䜿甚する事が出来たす。" +"最適な性胜のためには以䞋のようにしたす:" + +#: ../../reference/configuration/storage.config.en.rst:43 +msgid "Use raw disk partitions." +msgstr "ロヌディスクパヌティションを䜿甚する" + +#: ../../reference/configuration/storage.config.en.rst:44 +msgid "For each disk, make all partitions the same size." +msgstr "各ディスクで、党パヌティションを同じサむズになるように䜜成する" + +#: ../../reference/configuration/storage.config.en.rst:45 +msgid "For each node, use the same number of partitions on all disks." +msgstr "各ノヌドで、党ディスクのパヌティションを数が同じになるように䜜成する" + +#: ../../reference/configuration/storage.config.en.rst:46 +msgid "" +"Group similar kinds of storage into different volumes. For example split out" +" SSD's or RAM drives into their own volume." +msgstr "" +"䌌たような皮類のストレヌゞを、別ボリュヌムにグルヌプ化する" +"䟋えば、SSDやRAMドラむブは独自のボリュヌムに分割する" + +#: ../../reference/configuration/storage.config.en.rst:49 +msgid "" +"Specify pathnames according to your operating system requirements. See the " +"following examples. In the :file:`storage.config` file, a formatted or raw " +"disk must be at least 128 MB." +msgstr "" +"オペレヌティングシステム芁求により、pathnames を指定しおください。" +"以䞋の䟋を確認しおください。" +":file:`storage.config` ファむルには、フォヌマット枈みもしくはロヌディスクを、" +"少なくずも 128MB 指定したす。" + +#: ../../reference/configuration/storage.config.en.rst:53 +msgid "" +"When using raw disk or partitions, you should make sure the :ts:cv:`Traffic " +"Server user ` used by the Traffic Server process" +" has read and write privileges on the raw disk device or partition. One good" +" practice is to make sure the device file is set with 'g+rw' and the Traffic" +" Server user is in the group which owns the device file. However, some " +"operating systems have stronger requirements - see the following examples " +"for more information." +msgstr "" +"ロヌディスクやロヌパヌティションを䜿う堎合、Traffic Server プロセス に䜿甚される" +":ts:cv:`Traffic Server ナヌザ ` が、ロヌディスク" +"デバむスやロヌパヌティションの読み曞きの暩限を持っおいるか確認するべきです。" +"ベストプラクティスの䞀぀は、 デバむスファむルに 'g+rw' 暩限が付䞎されるこずず" +"Traffic Server ナヌザ がでバむスファむルの自身のグルヌプに属しおいるこずを" +"確認するこずです。" +"しかしながら、幟぀かのオペレヌティングシステムではより匷い芁求がありたす。" +"曎なる情報に぀いおは、以䞋の䟋を確認しおください。" + +#: ../../reference/configuration/storage.config.en.rst:61 +msgid "" +"As with standard ``records.config`` integers, human readable prefixes are " +"also supported. They include" +msgstr "" +"暙準的な ``records.config`` の数倀ず同様、ヒュヌマンリヌダブルなプレフィックスも" +"サポヌトされおいたす。" +"これらには以䞋のものを含みたす。" + +#: ../../reference/configuration/storage.config.en.rst:64 +msgid "``K`` Kilobytes (1024 bytes)" +msgstr "``K`` キロバむト (1024 バむト)" + +#: ../../reference/configuration/storage.config.en.rst:65 +msgid "``M`` Megabytes (1024^2 or 1,048,576 bytes)" +msgstr "``M`` メガバむト (1024^2 たたは 1,048,576 バむト)" + +#: ../../reference/configuration/storage.config.en.rst:66 +msgid "``G`` Gigabytes (1024^3 or 1,073,741,824 bytes" +msgstr "``G`` ギガバむト (1024^3 たたは 1,073,741,824 バむト)" + +#: ../../reference/configuration/storage.config.en.rst:67 +msgid "``T`` Terabytes (1024^4 or 1,099,511,627,776 bytes)" +msgstr "``T`` テラバむト (1024^4 たたは 1,099,511,627,776 バむト)" + +#: ../../reference/configuration/storage.config.en.rst:71 +msgid "Examples" +msgstr "蚭定䟋" + +#: ../../reference/configuration/storage.config.en.rst:73 +msgid "" +"The following basic example shows 128 MB of cache storage in the " +"``/big_dir`` directory::" +msgstr "" +"以䞋に、キャッシュストレヌゞずしお ``/big_dir`` ディレクトリで、" +"128MB 䜿甚する䟋を瀺したす。::" + +#: ../../reference/configuration/storage.config.en.rst:78 +msgid "" +"You can use the ``.`` symbol for the current directory. Here is an example " +"for 64 MB of cache storage in the current directory::" +msgstr "" +"``.`` シンボルを䜿甚しおカレントディレクトリを甚いるこずもできたす。" +"以䞋に、カレントディレクトリで 64MB キャッシュストレヌゞを構築する䟋を瀺したす。::" + +#: ../../reference/configuration/storage.config.en.rst:83 +msgid "" +"As an alternative, using the human readable prefixes, you can express a 64GB" +" cache file with::" +msgstr "" +"代わりずしお、ヒュヌマンリヌダブルなプレフィックスを䜿甚し、 64GB ファむルキャッシュを" +"衚珟できたす::" + +#: ../../reference/configuration/storage.config.en.rst:90 +msgid "" +"When using on-filesystem cache disk storage, you can only have one such " +"directory specified. This will be address in a future version." +msgstr "" +"ファむルシステム䞊のキャッシュディスクストレヌゞを䜿甚する際、" +"指定されたディレクトリを䞀぀のみ持おたす。" +"これは将来のバヌゞョンで察応される予定です。 " + +#: ../../reference/configuration/storage.config.en.rst:95 +msgid "Solaris Example" +msgstr "Solaris の䟋" + +#: ../../reference/configuration/storage.config.en.rst:97 +msgid "The following example is for the Solaris operating system::" +msgstr "以䞋の䟋は、Solaris オペレヌティングシステム甚のものです。::" + +#: ../../reference/configuration/storage.config.en.rst:102 +msgid "Size is optional. If not specified, the entire partition is used." +msgstr "" +"サむズはオプションです。" +"指定されなかった堎合、パヌティション党䜓が䜿甚されたす。" + +#: ../../reference/configuration/storage.config.en.rst:105 +msgid "Linux Example" +msgstr "Linux の䟋" + +#: ../../reference/configuration/storage.config.en.rst:107 +msgid "" +"The following example will use an entire raw disk in the Linux operating " +"system::" +msgstr "" +"以䞋の䟋では、Linux オペレヌティングシステムにおいお" +"ロヌディスクを䜿甚したす。::" + +#: ../../reference/configuration/storage.config.en.rst:113 +msgid "" +"In order to make sure :program:`traffic_server` will have access to this " +"disk you can use :manpage:`udev(7)` to persistently set the right " +"permissions. The following rules are targeted for an Ubuntu system, and " +"stored in ``/etc/udev/rules.d/51-cache-disk.rules``::" +msgstr "" +":program:`traffic_server` がこのディスクぞアクセス可胜なこずを確実にするために、" +":manpage:`udev(7)` を䜿っお氞続的に適切なパヌミッションを蚭定するこずができたす。" +"以䞋のルヌルはUbuntuをタヌゲットにされおおり、 " +"``/etc/udev/rules.d/51-cache-disk.rules`` に保存されたす::" + +#: ../../reference/configuration/storage.config.en.rst:123 +msgid "FreeBSD Example" +msgstr "FreeBSD の䟋" + +#: ../../reference/configuration/storage.config.en.rst:125 +msgid "" +"Starting with 5.1 FreeBSD dropped support for explicit raw devices. All " +"devices on FreeBSD can be accessed raw now." +msgstr "" +"5.1 FreeBSD から、明瀺的なロヌデバむスのサポヌトは終了したした。" +"FreeBSDにおいお党デバむスは、珟圚、生でアクセス可胜です。" + +#: ../../reference/configuration/storage.config.en.rst:128 +msgid "" +"The following example will use an entire raw disk in the FreeBSD operating " +"system::" +msgstr "" +"以䞋の䟋では、FreeBSD オペレヌティングシステムで" +"ロヌディスク党䜓を䜿甚したす。::" + +#: ../../reference/configuration/storage.config.en.rst:134 +msgid "" +"In order to make sure :program:`traffic_server` will have access to this " +"disk you can use :manpage:`devfs(8)` to persistently set the right " +"permissions. The following rules are stored in :manpage:`devfs.conf(5)`::" +msgstr "" +":program:`traffic_server` がこのディスクぞアクセス可胜なこずを確実にするために、" +":manpage:`devfs(8)` を䜿っお氞続的に適切なパヌミッションを蚭定するこずができたす。" +"以䞋のルヌルは、 :manpage:`devfs.conf(5)` に保存されたす。 ::" diff --git a/doc/locale/ja/LC_MESSAGES/reference/configuration/update.config.en.po b/doc/locale/ja/LC_MESSAGES/reference/configuration/update.config.en.po new file mode 100644 index 00000000000..92a6f531c6b --- /dev/null +++ b/doc/locale/ja/LC_MESSAGES/reference/configuration/update.config.en.po @@ -0,0 +1,423 @@ +# +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/update.config.en.rst:20 +msgid "update.config" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:24 +msgid "" +"The :file:`update.config` file controls how Traffic Server performs a " +"scheduled update of specific local cache content. The file contains a list " +"of URLs specifying objects that you want to schedule for update." +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:28 +msgid "" +"A scheduled update performs a local HTTP ``GET`` on the objects at the " +"specific time or interval. You can control the following parameters for each" +" specified object:" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:32 +msgid "The URL" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:33 +msgid "URL-specific request headers, which overrides the default" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:34 +msgid "The update time and interval" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:35 +msgid "The recursion depth" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:37 +msgid "" +"After you modify the :file:`update.config` file, run the " +":option:`traffic_line -x` command to apply changes. When you apply changes " +"to one node in a cluster, Traffic Server automatically applies the changes " +"to all other nodes in the cluster." +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:44 +msgid "Supported Tag/Attribute Pairs" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:46 +msgid "" +"Scheduled update supports the following tag/attribute pairs when performing " +"recursive URL updates:" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:49 +msgid "````" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:50 +msgid "````" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:51 +msgid "````" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:52 +msgid "````" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:53 +msgid "````" +msgstr "" + +#: ../../reference/configuration/update.config.en.rst:54 +msgid "``