Hello, Robert Segall <[email protected]> (Fri Jun 24 18:06:50 2011): > > we are currently in a situation where the actual IP of the Backend may … > > change. As of pound 2.5 it looks like the hostname is resolved just once … > > Thank you for the patch. For the moment I am quite sceptical about it, > as DNS lookups are expensive operations (the reason the results are > cached). We'll look at it again if there is massive demand for it.
For this reason an extra option was invented. Thus the extra DNS lookups are only done if the backend is marked as "dynamic". For (at least our) usage pattern performance is not important, but flexibility. > > As an aside, just for my curiosity: what is the usage pattern that would > require such a scenario? (Speaking as part of the same company as the OP and as initiator of the patch in question.) 1) From my Android phone I'm connecting to the our calendar server. This server runs at a cheap dialin DSL connection, changing it's IP once a day. (But updating it some dyndns service.) The used software on the android is stupid enough to resolve the IP address of the calender server at configuration time. Now we're using the patched pound on a central server (having a fixed IP) to forward the requests to the moving target. 2) At the some server behind a cheap dialin DSL connection some https based service is running, but unfortunately the IP address changes once a day. Some software is stupid enough not to allow an import of our own CA certificate. Now a patched version of pound is used to service as man in the middle on a central server, using an "officially singed" certificate. Based on the URL requested it forwards/proxies the requests via https to the above mentioned service. *) I've split it into two use cases, but actually both cases are combined. -- Heiko :: dresden : linux : SCHLITTERMANN.de GPG Key 48D0359B : 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B
signature.asc
Description: Digital signature
