https://bz.apache.org/bugzilla/show_bug.cgi?id=59045
--- Comment #12 from Yann Ylavic <[email protected]> --- (In reply to Ruediger Pluem from comment #11) > > Hm. Is another output filter really the best solution? It has to be passed > for every run of the output chain. > How about setting a note to c->notes in check_pipeline that informs > mod_reqtimeout to step out of our way temporarily? This removes the need for > mod_reqtimeout to second guess from other conditions that it has to step out. It's not really an heavy filter, not sure it performs slower than an apr_table lookup... This filter shouldn't be noticeable from a performance POV, and I think it is sane in any case, do we (will) control all the speculative/non-blocking (administrative) reads between requests? The "notes" could possibly be added for individual modules (if needed) to handle a temporary state (those that currently disable mod_reqtimeout completely, for no good reason IMHO), but that's another story I think. But I'm not totally opposed to your solution either, maybe other opinions? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
