Thanks for the code Philippe. I'm going to try it.
I think it'd be cool if the proxy automatically ran the validator on the
page being proxied and the javascript that was added to the page by the
proxy would write the results to a logger window or alert.
Is this an easy thing to do with HTTP::
There's a rule of thumb that goes along the lines of "bugs lurk where
many changes are made to the source code", because it's a sign of "we're
just not getting this area right."
Has anyone tried to use checkin/diff info to find areas to focus on for
testing? Anyone tied it to a coverage tool?
