ap_custom_response allocates memory from a request pool and places a pointer to that in a static structure (non-request-pool based). http://bugs.apache.org/index.cgi/full/8334 Slightly older version of same bug: http://bugs.apache.org/index.cgi/full/6336 Anybody care to take a look at the patch included with 8334 and see if it is right? It shifts the custom_response from a global (only needed to be called once) to something that must be called per-request. I think this is the right thing to do though, but I'm not 100% sure. -- justin
