Ok, this seems to have fixed it: domain1 has a wildcard cert where domain2 is a single name. I had been using: HeadRequire "Host:.*domain1.*" HeadRequire "Host:.*domain2.*"
If I change the latter to HeadRequire "Host:domain1.*" (i.e. remove the leading .*) the correct domain is requested. Not very high tech as I suspected :) On 16/01/2015 06:17, Christian Hailer wrote: > For historical reasons ;) > No, I'm connecting via HTTPS to my backend, I'm just too lazy to reconfigure > the setup... > > Christian > > -----Ursprüngliche Nachricht----- > Von: Adam Gold [mailto:[email protected]] > Gesendet: Freitag, 16. Januar 2015 01:20 > An: [email protected] > Betreff: Re: [Pound Mailing List] mutliple ssl certs and one server > > On 15/01/2015 23:26, Christian Hailer wrote: >> Ah sorry, just saw you tried this. But this is the correct way, I use 7 >> certificates with one apache as backend. Example: >> >> Service >> HeadRequire "Host:.*www.example.com.*" >> BackEnd >> Address 1.1.1.1 >> Port 10443 >> HTTPS >> TimeOut 60 >> End >> End >> > Thanks for the response. Yeah, I did try with that line as well but no joy. > I'm going to review my settings very carefully as maybe I've made some really > dumb mistake. > > I did have a question: why do you have HTTPS in your backend definition? > I thought Pound offloads the https and transmits plain http to the backend. > > -- > 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. > -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
