The syntax for ap_register_output_filter() specifies the handler 'key' used in the AddOutputFilter configuration directive. The ap_hook_handler() call does not specify the handler key from the corresponding AddHandler configuration directive. As a consequence, the specified handler function must look at and accept or decline each request. By contrast, output filters only see requests in which they have interest.
Is there a rationale for this? Am I missing a register_hook function that would allow me to set a key for a response handler? I'm looking at trace statements and my handler must reject PNG files and so forth...seems like this is less efficient than it could be. I'm probably missing something. mma
