mod_proxy_html Version 2.4 (Sept-Nov 2004).
+mod_proxy_html Version 3.1 (April 2009).
HTML links are those attributes defined by the HTML 4 and XHTML 1
DTDs as of type %URI. For example, the href
-attribute of the a element. For a full list, see the
-declaration of linked_elts in pstartElement.
-Rules are applicable provided the h flag is not set.
ProxyHTMLLinks directive.
+(the accompanying proxy_html.conf configuration file gives
+you standard HTML4 and XHTML 1, as hardwired in earlier
+mod_proxy_html versions).
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.
onclick.
+Rules are applicable provided the e flag is not set.
+From Version 3, the definition of events to use is
+delegated to the system administrator via the ProxyHTMLEvents
+directive: see proxy_html.conf.
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,10 +127,15 @@ 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 +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.
The character encoding should be declared in HTTP: for example
Content-Type: text/html; charset=latin1
@@ -127,7 +143,7 @@ mod_proxy_html has always supported this in its input, and ensured
this happens in output. But prior to version 2, it did not fully
support detection (sniffing) the charset when a backend fails to
set the HTTP Header.
From version 2.0, mod_proxy_html will detect the encoding of its input +
From version 2, mod_proxy_html will detect the encoding of its input as follows:
From Version 3.1 the above is delegated to +mod_xml2enc, which also expands charset support +and enables you to:
+The HTML meta element includes a form
<meta http-equiv="Some-Header" contents="some-value">
@@ -191,4 +219,12 @@ 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