From: Joshua Slive
Date: Wed, 29 May 2002 03:49:52 +0000 (+0000)
Subject: Update transformations.
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6ba2a5369bda5af61fd06078c4348c742358e8b0;p=apache
Update transformations.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95336 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mod_negotiation.html.en b/docs/manual/mod/mod_negotiation.html.en
index 2439fa4f1d..2235d574ca 100644
--- a/docs/manual/mod/mod_negotiation.html.en
+++ b/docs/manual/mod/mod_negotiation.html.en
@@ -17,7 +17,7 @@
implicit filename pattern match, and choose from amongst the
results.
-Directives
See also
Type maps
+Directives
See also
A type map has the same format as RFC822 mail headers. It
contains document descriptions separated by blank lines, with
lines beginning with a hash character ('#') treated as
@@ -80,15 +80,38 @@
Example:
-
- Content-Type: image/jpeg; qs=0.8
-
+Content-Type: image/jpeg; qs=0.8 |
URI:
- The path to the file containing this variant, relative to
- the map file.
+ uri of the file containing the variant (of the given
+ media type, encoded with the given content encoding). These
+ are interpreted as URLs relative to the map file; they must
+ be on the same server (!), and they must refer to files to
+ which the client would be granted access if they were to be
+ requested directly.
+
+ Body:
+
+ New in Apache 2.0, the actual content of the resource may
+ be included in the type-map file using the Body header. This
+ header must contain a string that designates a delimiter for
+ the body content. Then all following lines in the type map
+ file will be considered part of the resource body until the
+ delimiter string is found.
+
+ Example:
+
+Body:----xyz----
+<html>
+<body>
+<p>Content of the page.</p>
+</body>
+</html>
+----xyz----
+ |
+
MultiViews
diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en
index 2976fa8db0..b3c11ae2cf 100644
--- a/docs/manual/mod/mod_proxy.html.en
+++ b/docs/manual/mod/mod_proxy.html.en
@@ -221,8 +221,8 @@ to the correct, fully qualified, server address. This is the preferred method
since the user's bookmark files will then contain fully qualified hosts.
-
Description: | Ports that are allowed to CONNECT through
-the proxy | Syntax: | AllowCONNECT port [port] ... | Default: | AllowCONNECT 443 563 | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Ports that are allowed to CONNECT through
+the proxy | Syntax: | AllowCONNECT port [port] ... | Default: | AllowCONNECT 443 563 | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
The AllowCONNECT
directive specifies a list
of port numbers to which the proxy CONNECT
method may
connect. Today's browsers use this method when a https
@@ -231,8 +231,8 @@ effect.
By default, only the default https port (443) and the
default snews port (563) are enabled. Use the
AllowCONNECT
directive to overrride this default and
allow connections to the listed ports only.
-
Description: | Hosts, domains, or networks that will be connected
-to directly | Syntax: | NoProxy
+
+ Hostname] ... | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
This directive is only useful for Apache proxy servers within
intranets. The NoProxy
directive specifies a
list of subnets, IP addresses, hosts and/or domains, separated by
@@ -334,8 +334,8 @@ always served directly, without forwarding to the configured
and www.mydomain.com.
(note the trailing period) are
considered equal.
-
See also
Description: | Container for directives applied to proxied
-resources | Syntax: | <Proxy wildcard-url> ...</Proxy> | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+See also
Description: | Container for directives applied to proxied
+resources | Syntax: | <Proxy wildcard-url> ...</Proxy> | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
Directives placed in <Proxy>
sections apply only to matching proxied content. Shell-style
wildcards are allowed.
@@ -361,9 +361,9 @@ server:
SetOutputFilter INCLUDES
<Proxy>
-
Description: | Words, hosts, or domains that are banned from being
-proxied | Syntax: | ProxyBlock *|word|host|domain
-[word|host|domain] ... | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Words, hosts, or domains that are banned from being
+proxied | Syntax: | ProxyBlock *|word|host|domain
+[word|host|domain] ... | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
The ProxyBlock
directive specifies a list of
words, hosts and/or domains, separated by spaces. HTTP, HTTPS, and
FTP document requests to sites whose names contain matched words,
@@ -390,7 +390,7 @@ ProxyBlock *
blocks connections to all sites.
-
Description: | Default domain name for proxied requests | Syntax: | ProxyDomain Domain | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Default domain name for proxied requests | Syntax: | ProxyDomain Domain | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
This directive is only useful for Apache proxy servers within
intranets. The ProxyDomain
directive specifies
the default domain which the apache proxy server will belong to. If a
@@ -403,23 +403,23 @@ will be generated.
NoProxy .mycompany.com 192.168.112.0/21
ProxyDomain .mycompany.com
-
+
This directive is useful for reverse-proxy setups, where you want to
have a common look and feel on the error pages seen by the end user.
This also allows for included files (via mod_include's SSI) to get
the error code and act accordingly (default behavior would display
the error page of the proxied server, turning this on shows the SSI
Error message).
-
Description: | IO buffer size for outgoing HTTP and FTP
-connections | Syntax: | ProxyIOBufferSize bytes | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | IO buffer size for outgoing HTTP and FTP
+connections | Syntax: | ProxyIOBufferSize bytes | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
-
Description: | Container for directives applied to regular-expression-matched
-proxied resources | Syntax: | <Proxy regex> ...</Proxy> | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Container for directives applied to regular-expression-matched
+proxied resources | Syntax: | <Proxy regex> ...</Proxy> | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
The <ProxyMatch>
directive is
identical to the <Proxy>
directive, except it matches URLs
using regular expressions.
-
+
The ProxyMaxForwards
directive specifies the
maximum number of proxies through which a request may pass. This is
set to prevent infinite proxy loops, or a DoS attack.
@@ -427,8 +427,8 @@ set to prevent infinite proxy loops, or a DoS attack.
Example
ProxyMaxForwards 10
|
-
Description: | Maps remote servers into the local server
-URL-space | Syntax: | ProxyPass [path] !|url | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Maps remote servers into the local server
+URL-space | Syntax: | ProxyPass [path] !|url | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
This directive allows remote servers to be mapped into the space of
the local server; the local server does not act as a proxy in the
conventional sense, but appears to be a mirror of the remote
@@ -457,8 +457,8 @@ a subdirectory. eg.
When used inside a <Location>
section, the first argument is
ommitted and the local directory is obtained from the <Location>
.
-
Description: | Adjusts the URL in HTTP response headers sent from
-a reverse proxied server | Syntax: | ProxyPassReverse [path] url | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Adjusts the URL in HTTP response headers sent from
+a reverse proxied server | Syntax: | ProxyPassReverse [path] url | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
This directive lets Apache adjust the URL in the Location
,
Content-Location
and URI
headers on
HTTP redirect responses. This is essential when Apache is used as
@@ -495,16 +495,16 @@ directive.
When used inside a <Location>
section, the first argument is
ommitted and the local directory is obtained from the <Location>
.
-
Description: | Use incoming Host HTTP request header for
-proxy request | Syntax: | ProxyPreserveHost on|off | Default: | ProxyPreserveHost Off | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy | Compatibility: | Available in
+
When enabled, this option will pass the Host: line from the
incoming request to the proxied host, instead of the hostname
specified in the proxypass line.
This option should normally be turned 'off'.
-
Description: | Network buffer size for outgoing HTTP and FTP
-connections | Syntax: | ProxyReceiveBufferSize bytes | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Network buffer size for outgoing HTTP and FTP
+connections | Syntax: | ProxyReceiveBufferSize bytes | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
The ProxyReceiveBufferSize directive
specifies an explicit network buffer size for outgoing HTTP and FTP
connections, for increased throughput. It has to be greater than 512
@@ -513,7 +513,7 @@ be used.
Example
ProxyReceiveBufferSize 2048
|
-
Description: | Remote proxy used to handle certain requests | Syntax: | ProxyRemote match remote-server | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Remote proxy used to handle certain requests | Syntax: | ProxyRemote match remote-server | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
This defines remote proxies to this proxy. match is either the
name of a URL-scheme that the remote server supports, or a partial URL
for which the remote server should be used, or '*' to indicate the
@@ -542,13 +542,13 @@ them.
This option also supports reverse proxy configuration - a backend
webserver can be embedded within a virtualhost URL space even if that
server is hidden by another forward proxy.
-
Description: | Remote proxy used to handle requests
-matched by regular expressions | Syntax: | ProxyRemote regex remote-server | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Remote proxy used to handle requests
+matched by regular expressions | Syntax: | ProxyRemote regex remote-server | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
The ProxyRemoteMatch is identical
to the ProxyRemote
directive, except the first argument is a regular expression
match against the requested URL.
-
+
This allows or prevents Apache from functioning as a forward proxy
server. (Setting ProxyRequests to 'off' does not disable use of the
ProxyPass directive.)
@@ -560,15 +560,15 @@ server. (Setting ProxyRequests to 'off' does not disable use of the
secured your server. Open proxy servers are
dangerous both to your network and to the Internet at large. |
-
Description: | Network timeout for proxied requests | Syntax: | ProxyTimeout seconds | Default: | ProxyTimeout 300 | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy | Compatibility: | Available in
+
This directive allows a user to specifiy a timeout on proxy requests.
This is usefull when you have a slow/buggy appserver which hangs,
and you would rather just return a timeout and fail gracefully instead
of waiting however long it takes the server to return
-
Description: | Information provided in the Via HTTP response
-header for proxied requests | Syntax: | ProxyVia on|off|full|block | Default: | ProxyVia off | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
+
Description: | Information provided in the Via HTTP response
+header for proxied requests | Syntax: | ProxyVia on|off|full|block | Default: | ProxyVia off | Context: | server config, virtual host | Status: | Extension | Module: | mod_proxy |
|
This directive controls the use of the Via: HTTP
header by the proxy. Its intended use is to control the flow of of
proxy requests along a chain of proxy servers. See RFC2068 (HTTP/1.1)
|
|
|