On 13 Jun 2011, at 1:11 PM, Paul Querna wrote:
Why is this in the core?
The example in the documentation doesn't make sense, this data encoded
this way is inline, not the whole response.
This was covered in the original thread, which contains links
explaining what rfc2397 is and what it does:
http://mail-archives.apache.org/mod_mbox/httpd-dev/201105.mbox/%[email protected]%3e
http://mail-archives.apache.org/mod_mbox/httpd-dev/201106.mbox/%[email protected]%3E
http://mail-archives.apache.org/mod_mbox/httpd-dev/201106.mbox/%[email protected]%3E
I think an example in the docs using mod_include should make it
clearer as how to use it out the box, I'll update the docs.
I don't get why this is a filter in httpd core, its a feature of an
app server when its generate its HTML?
In our case we have hundreds and hundreds of separate applications, as
well as a common skin applied to everything using either php,
mod_include or varnish ESI. Trying to create an application between a
file and mod_include et al to create data URLs would have been quite a
sledgehammer, given that we have a filter stack perfectly suited for
the task.
Regards,
Graham
--
