Tim wrote:

> I thought that'd already been explained. But hasn't it occured to you that
> if the proxy has problems with MALFORMED HTML, then so will some browsers?
> There's one solution, and one solution only: Fix up the broken HTML.
>

Entirely right of course, but not the whole story.

A browser expects to work for a single user on a workstation where it
is one of a very few active tasks, and can itself to oodles of
CPU and memory. So it can put a lot of effort into error-correction.

The proxy doesn't have that luxury. It needs to be able to process
thousands of concurrent requests, and cares a lot more about efficiency
than a browser. So it's less forgiving than a typical browser.

mod_publisher offers more options, including expending more resources
on error correction.

--
Nick Kew