We use haproxy, which does all that, including the ability to reload the config gracefully (http://www.mgoff.in/2010/04/18/haproxy-reloading-your-config-with-minimal-service-impact/).
I hear good things about nginx. Tom On Mon, Sep 1, 2014 at 10:45 PM, Geoff Halprin <[email protected]> wrote: > > I'm after recommendations for a Forward HTTP / HTTPS proxy for use in an API > gateway. > > It will need to support: > · Non-authenticated and authenticated access to downstream proxies. > · Direct connection support (duh)... > · Non-Caching. > · High concurrent flow capability. > · Able to support an ordered mapping of either (protocol, host or host > suffix, port), (host or host suffix, port) or (host or host suffix) to next > hop-proxy or direct connection. Wildcard support for host portions. Examples > below. > · Ideally able to update rules without shutting down the proxy; loss of > current requests... > > Examples: > > http://www.outside.dmz:8080 ==> CONNECT proxy1.local:8880 > https://secure.com ==> CONNECT user:[email protected]:80 > https://www.secure.com ==> DIRECT (DNS resolution of www.secure.com) > http://api.other.org ==> DIRECT (DNS resolution of api.other.org) > DEFAULT => <direct> > > Warm regards, > > Geoff Halprin > > _______________________________________________ > Tech mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- Email: [email protected] Work: [email protected] Skype: YesThatTom Blog: http://EverythingSysadmin.com _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
