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/

Reply via email to