From b199b7329801efd705c41d93dae4869900a952f1 Mon Sep 17 00:00:00 2001 From: Justin B Rye Date: Fri, 5 Jan 2018 22:35:31 +0100 Subject: review and fix the three new apt-transport- manpages References: https://lists.debian.org/debian-l10n-english/2018/01/msg00002.html --- doc/apt-transport-http.1.xml | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) (limited to 'doc/apt-transport-http.1.xml') diff --git a/doc/apt-transport-http.1.xml b/doc/apt-transport-http.1.xml index 546e47761..7426a4502 100644 --- a/doc/apt-transport-http.1.xml +++ b/doc/apt-transport-http.1.xml @@ -35,30 +35,30 @@ most used of all transports. Note that a transport is never called directly by a user but used by APT tools based on user configuration. HTTP is an unencrypted transport protocol meaning that the whole communication with the remote server (or proxy) can be observed by a -sufficiently capable attacker referred to commonly as man in the middle (MITM). -Such an attacker can not modify the communication to compromise -the security of your system through as APTs data security model is independent of the -chosen transport method. This is explained in detail in &apt-secure;. An overview over +sufficiently capable attacker commonly referred to as a "man in the middle" (MITM). +However, such an attacker can not modify the communication to compromise +the security of your system, as APT's data security model is independent of the +chosen transport method. This is explained in detail in &apt-secure;. An overview of available transport methods is given in &sources-list;. Options -Various options are available to modify its behaviour which can be set in -an &apt-conf; file ranging from proxy configuration to workaround for specific -server insufficiencies. +Various options can be set in an &apt-conf; file to modify its behavior, +ranging from proxy configuration to workarounds for specific +server limitations. Proxy Configuration The environment variable http_proxy is supported for system wide configuration. -Proxies specific to apt can be configured via the option Acquire::http::Proxy. +Proxies specific to APT can be configured via the option Acquire::http::Proxy. Proxies which should be used only for certain hosts can be specified via Acquire::http::Proxy::host. Even more finegrained control -can be achieved via proxy autodetection detailed further below. +can be achieved via proxy autodetection, detailed further below. All these options use the URI format scheme://[[user][:pass]@]host[:port]/. Supported URI schemes are socks5h (SOCKS5 with remote DNS resolution), http and https. -Authentification details can be supplied via &apt-authconf; instead of including it in the URI directly. +Authentication details can be supplied via &apt-authconf; instead of including it in the URI directly. The various APT configuration options support the special value DIRECT meaning that -no proxy should be used. The environment variable no_proxy with the same propose is also supported. -Further more there are three settings provided for cache control with HTTP/1.1 compliant proxy caches: +no proxy should be used. The environment variable no_proxy is also supported for the same purpose. +Furthermore, there are three settings provided for cache control with HTTP/1.1 compliant proxy caches: Acquire::http::No-Cache tells the proxy not to use its cached response under any circumstances. Acquire::http::Max-Age sets the allowed maximum age (in @@ -70,8 +70,8 @@ the proxy from polluting its cache with (big) .deb files. Automatic Proxy Configuration Acquire::http::Proxy-Auto-Detect can be used to -specify an external command to discover the http proxy to use. The first -and only parameter is an URI denoting the host to be contacted to allow +specify an external command to discover the HTTP proxy to use. The first +and only parameter is a URI denoting the host to be contacted, to allow for host-specific configuration. APT expects the command to output the proxy on stdout as a single line in the previously specified URI format or the word DIRECT if no proxy should be used. No output @@ -93,8 +93,8 @@ disables downloading from multiple servers at the same time. The setting Acquire::http::Pipeline-Depth can be used to enable HTTP pipelining (RFC 2616 section 8.1.2.2) which can be beneficial e.g. on high-latency connections. It specifies how many requests are sent in a pipeline. -APT tries to detect and workaround misbehaving webservers and proxies at runtime, but -if you know that yours does not conform to the HTTP/1.1 specification pipelining can +APT tries to detect and work around misbehaving webservers and proxies at runtime, but +if you know that yours does not conform to the HTTP/1.1 specification, pipelining can be disabled by setting the value to 0. It is enabled by default with the value 10. Acquire::http::AllowRedirect controls whether APT will follow redirects, which is enabled by default. @@ -102,7 +102,7 @@ redirects, which is enabled by default. User-Agent for the http download method as some proxies allow access for clients only if the client uses a known identifier. Acquire::http::SendAccept is enabled by default and -sends a Accept: text/* header field to the server for +sends an Accept: text/* header field to the server for requests without file extensions to prevent the server from attempting content negotiation. -- cgit v1.2.3