Stipe,
now, I think as we "went that way" for the other issues, black/white lists, prefered-smsc-id, etc. this would be the better way to go.
Obviously it would be a "add-on" in the first place, in order not to break configs. Afterwards we'd cut out the "old way" support in order to have it one way.
Could it be done as say an http-proxy-host-exceptions-regex or a ./config option for the "in the meantime" handling? Getting the latest CVS and then re-patching it again is really a pain. Especially since I'll soon be running load balanced servers and would have to do so multiple times, possibly at multiple sites.
Jon
