trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Galić <>
Subject Re: Proxying to dynamically changing origin servers
Date Tue, 30 Aug 2011 14:33:28 GMT

----- Original Message -----
> Hi everybody,
> [Please CC me in replies, I am not currently subscribed to this
> mailing
> list.]
> For a research project, we currently have an interesting problem to
> solve: to connect HTTPS clients to dynamically changing, internal
> servers. One approach that we are currently evaluating is to use a
> publicly accessible HTTP proxy with CONNECT support to "tunnel" the
> HTTPS connections to the internal servers. However, the internal
> addresses may change dynamically. The question is therefore if
> Traffic
> Server can be configured to (or if it is easy to write a plug-in to):
> a) be used in "normal" proxy server mode for clients with explicit
> proxy
> server configuration to use the CONNECT call for some HTTPS URLs; and
> b) for the origin server resolving to be done dynamically based on
> internal look-up tables. E.g. the URL
> specified by any client in the
> CONNECT request should be mapped to host (the HTTPS
> server
> may use as its server address, but the IP will
> change dynamically).

It seems to me all that is required is to set the DNS TTL very low. 

> I am aware that this is a mix between reverse proxy functionality
> (mapping to internal servers) and normal proxying (CONNECT to
> client-specified, different URLs). Based on the SDK documentation, I
> am
> also unsure which kind of plug-in would be required to make this
> work.
> The backup plan is to use a "normal" proxy with dynamic DNS for
> resolving the internal IP addresses, but we would like to avoid this
> complexity if possible.
> Are we on the right track and is this possible with Traffic Server?
> best regards,
> Rene


Igor Galić

Tel: +43 (0) 664 886 22 883
GPG: 571B 8B8A FC97 266D BDA3  EF6F 43AD 80A4 5779 3257

View raw message