From: Stefan Fritsch Date: Sat, 1 Oct 2011 20:57:36 +0000 (+0000) Subject: update xforms X-Git-Tag: 2.3.15~181 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a83284e10365f9baf39331e545dde65ecdc99ef1;p=thirdparty%2Fapache%2Fhttpd.git update xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1178089 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en index 79b27fada3e..43224bd1047 100644 --- a/docs/manual/bind.html.en +++ b/docs/manual/bind.html.en @@ -44,10 +44,10 @@

When httpd starts, it binds to some port and address on the local machine and waits for incoming requests. By default, it listens to all addresses on the machine. However, it may need to - be told to listen on specific ports, or only on selected - addresses, or a combination of both. This is often combined with the - Virtual Host feature, which determines how - httpd responds to different IP addresses, hostnames and + be told to listen on specific ports, or only on selected + addresses, or a combination of both. This is often combined with the + Virtual Host feature, which determines how + httpd responds to different IP addresses, hostnames and ports.

The Listen @@ -55,7 +55,7 @@ incoming requests only on the specified port(s) or address-and-port combinations. If only a port number is specified in the Listen - directive, the server listens to the given port on all interfaces. + directive, the server listens to the given port on all interfaces. If an IP address is given as well as a port, the server will listen on the given port and interface. Multiple Listen directives may be used to specify a number of addresses and ports to listen on. The @@ -85,9 +85,9 @@ Listen [2001:db8::a00:20ff:fea7:ccea]:80

-

Overlapping Listen directives will result in a +

Overlapping Listen directives will result in a fatal error which will prevent the server from starting up.

- +

(48)Address already in use: make_sock: could not bind to address [::]:80

@@ -100,31 +100,31 @@

A growing number of platforms implement IPv6, and APR supports IPv6 on most of these platforms, - allowing httpd to allocate IPv6 sockets, and to handle requests sent + allowing httpd to allocate IPv6 sockets, and to handle requests sent over IPv6.

One complicating factor for httpd administrators is whether or - not an IPv6 socket can handle both IPv4 connections and IPv6 - connections. Handling IPv4 connections with an IPv6 socket uses - IPv4-mapped IPv6 addresses, which are allowed by default on most - platforms, but are disallowed by default on FreeBSD, NetBSD, and + not an IPv6 socket can handle both IPv4 connections and IPv6 + connections. Handling IPv4 connections with an IPv6 socket uses + IPv4-mapped IPv6 addresses, which are allowed by default on most + platforms, but are disallowed by default on FreeBSD, NetBSD, and OpenBSD, in order to match the system-wide policy on those - platforms. On systems where it is disallowed by default, a + platforms. On systems where it is disallowed by default, a special configure parameter can change this behavior for httpd.

-

On the other hand, on some platforms, such as Linux and Tru64, the - only way to handle both IPv6 and IPv4 is to use - mapped addresses. If you want httpd to handle IPv4 and IPv6 connections - with a minimum of sockets, which requires using IPv4-mapped IPv6 +

On the other hand, on some platforms, such as Linux and Tru64, the + only way to handle both IPv6 and IPv4 is to use + mapped addresses. If you want httpd to handle IPv4 and IPv6 connections + with a minimum of sockets, which requires using IPv4-mapped IPv6 addresses, specify the --enable-v4-mapped configure option.

-

--enable-v4-mapped is the default on all platforms except - FreeBSD, NetBSD, and OpenBSD, so this is probably how your httpd was +

--enable-v4-mapped is the default on all platforms except + FreeBSD, NetBSD, and OpenBSD, so this is probably how your httpd was built.

-

If you want httpd to handle IPv4 connections only, regardless of - what your platform and APR will support, specify an IPv4 address on all +

If you want httpd to handle IPv4 connections only, regardless of + what your platform and APR will support, specify an IPv4 address on all Listen directives, as in the following examples:

@@ -133,8 +133,8 @@ Listen 192.0.2.1:80

-

If your platform supports it and you want httpd to handle IPv4 and - IPv6 connections on separate sockets (i.e., to disable IPv4-mapped +

If your platform supports it and you want httpd to handle IPv4 and + IPv6 connections on separate sockets (i.e., to disable IPv4-mapped addresses), specify the --disable-v4-mapped configure option. --disable-v4-mapped is the default on FreeBSD, NetBSD, and OpenBSD.

top
@@ -143,14 +143,14 @@

The optional second protocol argument of Listen - is not required for most - configurations. If not specified, https is the default for - port 443 and http the default for all other ports. The + is not required for most + configurations. If not specified, https is the default for + port 443 and http the default for all other ports. The protocol is used to determine which module should handle a request, and - to apply protocol specific optimizations with the + to apply protocol specific optimizations with the AcceptFilter directive.

-

You only need to set the protocol if you are running on non-standard +

You only need to set the protocol if you are running on non-standard ports. For example, running an https site on port 8443:

@@ -161,7 +161,7 @@

How This Works With Virtual Hosts

-

The Listen directive does not implement +

The Listen directive does not implement Virtual Hosts - it only tells the main server what addresses and ports to listen on. If no <VirtualHost> diff --git a/docs/manual/bind.html.fr b/docs/manual/bind.html.fr index e162fc5a452..513a31447be 100644 --- a/docs/manual/bind.html.fr +++ b/docs/manual/bind.html.fr @@ -91,7 +91,7 @@

Des directives Listen imbriquées provoqueront une erreur fatale qui empêchera le serveur de démarrer.

- +

(48)Address already in use: make_sock: could not bind to address [::]:80

diff --git a/docs/manual/bind.html.tr.utf8 b/docs/manual/bind.html.tr.utf8 index d2e68fbf89a..53eea28a846 100644 --- a/docs/manual/bind.html.tr.utf8 +++ b/docs/manual/bind.html.tr.utf8 @@ -25,6 +25,7 @@  ko  |  tr 

+
Bu çeviri güncel olmayabilir. Son değişiklikler için İngilizce sürüm geçerlidir.

Apache HTTPD sunucusunun belli adresleri ve portları dinlemek üzere yapılandırılması.

diff --git a/docs/manual/bind.xml.de b/docs/manual/bind.xml.de index 5bb44d2c045..093b711f9cc 100644 --- a/docs/manual/bind.xml.de +++ b/docs/manual/bind.xml.de @@ -1,7 +1,7 @@ - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -logresolve - Resolve IP-addresses to hostnames in Apache +<title>logresolve - Resolve IP-addresses to hostnames in Apache log files - Apache HTTP Server @@ -17,7 +17,7 @@
<-

logresolve - Resolve IP-addresses to hostnames in Apache +Apache > HTTP Server > Documentation > Version 2.3 > Programs

logresolve - Resolve IP-addresses to hostnames in Apache log files

Available Languages:  en  | diff --git a/docs/manual/programs/logresolve.html.ko.euc-kr b/docs/manual/programs/logresolve.html.ko.euc-kr index ac4460a5976..8e302cd47f2 100644 --- a/docs/manual/programs/logresolve.html.ko.euc-kr +++ b/docs/manual/programs/logresolve.html.ko.euc-kr @@ -24,6 +24,8 @@  ko  |  tr 

+
ÀÌ ¹®¼­´Â ÃÖ½ÅÆÇ ¹ø¿ªÀÌ ¾Æ´Õ´Ï´Ù. + ÃÖ±Ù¿¡ º¯°æµÈ ³»¿ëÀº ¿µ¾î ¹®¼­¸¦ Âü°íÇϼ¼¿ä.

logresolve´Â ¾ÆÆÄÄ¡ Á¢±Ù·Î±×ÆÄÀÏ¿¡ ÀÖ´Â IP-ÁÖ¼Ò¸¦ ã´Â ÈÄó¸® ÇÁ·Î±×·¥ÀÌ´Ù. ³×ÀÓ¼­¹öÀÇ ºÎÇϸ¦ diff --git a/docs/manual/programs/logresolve.html.tr.utf8 b/docs/manual/programs/logresolve.html.tr.utf8 index 65631f4bc0f..71d1647f86d 100644 --- a/docs/manual/programs/logresolve.html.tr.utf8 +++ b/docs/manual/programs/logresolve.html.tr.utf8 @@ -24,6 +24,7 @@  ko  |  tr 

+
Bu çeviri güncel olmayabilir. Son değişiklikler için İngilizce sürüm geçerlidir.

logresolve, Apache'nin erişim günlüklerindeki IP adreslerini çözümlemek için bir ardıl işlem diff --git a/docs/manual/programs/logresolve.xml.ko b/docs/manual/programs/logresolve.xml.ko index 30c2a328f91..7984bf49b0f 100644 --- a/docs/manual/programs/logresolve.xml.ko +++ b/docs/manual/programs/logresolve.xml.ko @@ -1,7 +1,7 @@ - + + + + + + + + + + + + + + + + + diff --git a/docs/manual/vhosts/details.xml.ko b/docs/manual/vhosts/details.xml.ko index d3cb93db201..a788a04184d 100644 --- a/docs/manual/vhosts/details.xml.ko +++ b/docs/manual/vhosts/details.xml.ko @@ -1,7 +1,7 @@ - + + + + + + + diff --git a/docs/manual/vhosts/ip-based.xml.ja b/docs/manual/vhosts/ip-based.xml.ja index 1119a162ac9..705f07c1cb5 100644 --- a/docs/manual/vhosts/ip-based.xml.ja +++ b/docs/manual/vhosts/ip-based.xml.ja @@ -1,7 +1,7 @@ - + + + + + + + diff --git a/docs/manual/vhosts/name-based.xml.ja b/docs/manual/vhosts/name-based.xml.ja index 72fab3bd85e..74539ab46e7 100644 --- a/docs/manual/vhosts/name-based.xml.ja +++ b/docs/manual/vhosts/name-based.xml.ja @@ -1,7 +1,7 @@ - + + +