I'm not sure about 1 but the termination of ssl is as follows: the traffic is recived upon the standard port (443) and you need a certificate to achive this. When we want more then one certificate (different domains) WE add a virtual eth and use that (we have 1:1 NAT of external IPv4 addresses). Then after the "termination" the traffic is sent via standard TCP 80 to the webserver. The form you are talking about I'm not sure about but you can demand a certificate from the client if needed (see the config).
3 I think is "Yes" or if it did a http get and acted upon a 200 from the server. Not sure :) // Regards 2012/6/5 P. Broennimann <[email protected]> > Hi there > > I am interested in using pound. I read the published information on your > website but I still have 3 questions (the whole topic is new to me!). > > I made a drawing illustrating my situation. > > 1. It would be nice if, for a same client, both client > application components (html5 web application & javascript webservice > interface) could be routed to the same destination virtual machine. Is this > doable using the pound "session" tracking mechanism? > > 2. If I understood well pound would be "terminating" the SSL > connection. In my case would I need 1 certificate or 2 (per client there > would be 2 tunnels established, one on port 80 and one on port 99)!? > > 3. Somewhere it is stated "*... Pound **can detects when a backend > server fails or recovers, and bases its load balancing decisions on this > information: if a backend server fails, it will not receive requests until > it recovers...*". How does this detection mechanism work? Is this > sothing like a ping? > > Many thanks in advance. > Peter > >
