From: Andre Malo Date: Mon, 9 Dec 2002 12:16:26 +0000 (+0000) Subject: clarify the no-proxy explanation of Addoutputfilterbytype. X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c9df4db49c49555f87b9588ff25924c1e5b4d38e;p=thirdparty%2Fapache%2Fhttpd.git clarify the no-proxy explanation of Addoutputfilterbytype. Thanks to Rich for pointing out. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97816 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 99cedab5edc..b6fb96ef4fe 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -233,7 +233,7 @@ response without an explicit character setForceType. Setting the content type within a (non-nph) CGI script is also safe.

-

The output filters are never applied on proxy requests.

+

The by-type output filters are never applied on proxy requests.

See also

top

AllowOverride Directive

Description: Types of directives that are allowed in diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index ccac3047766..071780850e3 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -203,7 +203,7 @@ response without an explicit character set ForceType. Setting the content type within a (non-nph) CGI script is also safe.

-

The output filters are never applied on proxy requests.

+

The by-type output filters are never applied on proxy requests.