> But with the right combination of modules, it is very easy to see that
> when a module calls ap_custom_response() on some flow, subsequent
> requests with no such call will still get the previously-registered
> response string.
> 
> While I have not hit crashes myself in testing

over in perl-land I maintain Apache-Test skeletons that users can adjust to
easily provide self-contained examples when reporting bugs:

  http://perl.apache.org/~geoff/bug-reporting-skeleton-mp2.tar.gz

now, these packages assume that you have mod_perl installed, so if you don't
there will be lots of tweaking to do.

however, I'd be happy to also maintain a set that are Apache/C-module
specific as well.  the idea would be that everything you have is already
there - just add in your httpd.conf and issue 'make test' and you ought to
have enough to reproduce specific behaviors.  as both stas and I have been
finding, not only are they good for users, but we both use them ourselves as
a quick starting point for reproducing user-reported behaviors.  I also use
it whenever I start to code against Apache internals :)

just a thought.

--Geoff

Reply via email to