@jeffkaufman "I'd rather apply it to this file within the mod_pagespeed repo"

Sounds good to me - but I intended to follow this up:

- Efficiency: I think that we can bail out earlier if we see a response that we don't want to record - DoneAndSetHeaders forces us to buffer the whole file. But it looks like we can make the decision to not record it once we have the response headers.
- Currently, I suspect something nasty might happen when serving out large files (e.g. a benign example would be video). It might be a good idea to put a bound to the amount of data that can be buffered. Thinking aloud, maybe two settings like IproMaxBufferSize en IproMaxConcurrentRecordings would be useful?

Would you prefer me to look at that too, and see if I can fix that as well in the forked files? That way, you only have to review and copy over the changes once.