mod_proxy_html Version 2.4 (Sept-Nov 2004).
+mod_proxy_html From Version 2.4 (Sept 2004). +Updates in Version 3 (Dec. 2006) are highlighted.
linked_elts in pstartElement.
-Rules are applicable provided the h flag is not set.
+Rules are applicable provided the h flag is not set.
+From Version 3, the definition of links to use is
+delegated to the system administrator via the ProxyHTMLLinks
+directive.
An HTML link always contains exactly one URL. So whenever mod_proxy_html
finds a matching ProxyHTMLURLMap rule, it will apply the
-transformation once and stop processing the attribute.
l flag, which causes processing
+a URL to continue after a rewrite.
Scripting events are the contents of event attributes as defined in the
HTML4 and XHTML1 DTDs; for example onclick. For a full list,
see the declaration of events in pstartElement.
-Rules are applicable provided the e flag is not set.
ProxyHTMLEvents
+directive.
A scripting event may contain more than one URL, and will contain other
text. So when ProxyHTMLExtended is On, all applicable rules
will be applied in order until and unless a rule with the L flag
@@ -116,11 +128,18 @@ apply the appropriate rules in generating output. HTML saves a few bytes.
If you declare a custom DTD, you should specify whether to generate HTML or XHTML syntax in the output. This affects empty elements: HTML <br> vs XHTML <br />.
+If you select standard HTML or XHTML, mod_proxy_html 3 will
+perform some additional fixups of bogus markup. If you don't want this,
+you can enter a standard DTD using the nonstandard form of
+ProxyHTMLDTD, which will then be treated as unknown
+(no corrections).
The parser uses UTF-8 (Unicode) internally, and -mod_proxy_html always generates output as UTF-8. This is -supported by all general-purpose web software, and supports more -character sets and languages than any other charset.
+mod_proxy_html prior to version 3 always generates output as UTF-8. +This is supported by all general-purpose web software, and supports more +character sets and languages than any other charset. +Version 3 supports, but does not recommend different outputs, using +theProxyHTMLCharsetOut directive.
The character encoding should be declared in HTTP: for example
Content-Type: text/html; charset=latin1
mod_proxy_html has always supported this in its input, and ensured
@@ -139,11 +158,28 @@ information.
<meta http-equiv="Content-Type" ...>, any charset declared
here is used.
ProxyHTMLCharsetDefault value is assumed.
In version 3.0, this remains the default, but +internationalisation support is further improved, and is no longer +limited to the encodings supported by libxml2:
+ProxyHTMLCharsetAlias directive enables server
+administrators to support additional encodings by aliasing them to
+something supported by libxml2.apr_xlate, which on most platforms
+is a wrapper for the leading conversion utility iconv.
+Because of undocumented behaviour of libxml2, this may cause problems
+when charset is specified in an HTML META element. This
+feature is therefore only enabled when ProxyHTMLMeta is On.The HTML meta element includes a form
<meta http-equiv="Some-Header" contents="some-value">
@@ -191,12 +227,4 @@ and after, and possibly in the middle of, a page. To work around this, set the
force-response-1.0 environment variable in httpd.conf.
For example,BrowserMatch MSIE force-response-1.0