Well, you could always do $self->proxy->{loop} = 0 but that would break the encapsulation.

Breaking the loop will prevent new childs to be forked, but the living one will at least finished the active connections before dying (they will not accept new connections).

Should I make loop() a read-write accessor in 0.16?

I'm stupid: HTTP::Proxy forks to start its children, and the main process never directly handles connections (except in very rare cases such as when too many child processes are started). So the only process that would be able to correctly handle that piece of information never actually sees it.

What you want is some way for the main process and its child process to communicate.

At this time, HTTP::Proxy has no built-in way to do this. :-( The main problem is that, when I'll have added this possibility, then I'll need to build some way for the main process to act on the received information (yet another hook somewhere).

You have another option: to create a global variable $main::PID (initialised to $$) and then have one of the child processes kill the parent whith the appropriate signal.