HTTPS backends were added in v2.5c... Are you having an issue configuring the feature, or are you using a pound that is older than that, or is it something else?
Joe > -----Original Message----- > From: Jean-Pierre [mailto:[email protected]] > Sent: Tuesday, February 07, 2012 2:05 PM > To: [email protected] > Subject: [Pound Mailing List] HTTPS backend > > I've been using pound for a long while now. > I'm also using pound to terminate my HTTPS connection with a cheapo 1- > subdomain SSL-certificate. > Thanks to Pound I can have a few different machines using 1 IP and 1 > subdomain. > > I now wanted to use pound to proxy my multi-WAN router. > The multi-WAN router uses several modems and with pound I will always > get a connection from a remote location because pound will only proxy > for connections that are UP. This way I don't need to remember IP's (I > can still do this as fallback). > > During configuration I realized for the first time that I can't proxy > to an SSL-connection. > I now switched to http remote access, but this means someone can get my > passwords.... > > Is there a special reason why I can't use https-backend? > SSL-support is already there as a client... > > BTW... I only need SSL-encryption, not 3-rd party authentication. > > JP > > > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
