/ Zope / Apsis / Pound Mailing List / Archive / 2007 / 2007-06 / Which brings me to what I was origionaly looking at...

[ << ] [ >> ]

[ And just to answer myself... / Malcolm ... ] [ OK, one last question (hopefully) / Malcolm ... ]

Which brings me to what I was origionaly looking at...
Malcolm <lists(at)loadbalancer.org>
2007-06-04 21:57:08 [ SNIP ]
With the following config all requests go to the backend in the first 
group irrespective of the service accessed?

ListenHTTPS 192.168.1.21,443 /usr/local/etc/server1.pem 
UrlGroup ".*"
BackEnd 192.168.1.78,80,1
EndGroup

ListenHTTPS 192.168.1.17,444 /usr/local/etc/server2.pem 
UrlGroup ".*"
BackEnd 192.168.1.16,80,1
EndGroup

i.e. if you try to connect to https://192.168.1.17:444 pound gives a 
response from BackEnd 192.168.1.78,80,1 !!

/NB. The pound version is v1.10/

And apologies for the last 2 posts before thinking, this one I'm pretty 
sure is an issue....

Regards,
Malcolm.
 

RE: [Pound Mailing List] Which brings me to what I was origionaly looking at...
"John D" <jwdavid(at)ibizvision.com>
2007-06-04 23:10:32 [ SNIP ]
In Pound 1.X Listeners are not tied directly to the groups.

Your config will need to look something like this:

ListenHTTPS 192.168.1.21,443 /usr/local/etc/server1.pem
ListenHTTPS 192.168.1.17,444 /usr/local/etc/server2.pem 

UrlGroup ".*"
HeadRequire Host ".*server1.com"
BackEnd 192.168.1.78,80,1
EndGroup

UrlGroup ".*"
HeadRequire Host ".*server2.com"
BackEnd 192.168.1.16,80,1
EndGroup

Hope this helps.

John D.

********** Original Email *********
** To:   pound(at)apsis.ch
** From: lists(at)loadbalancer.org
** Date: Mon, 04 Jun 2007 20:57:08 +0100
**********


With the following config all requests go to the backend in the first 
group irrespective of the service accessed?

ListenHTTPS 192.168.1.21,443 /usr/local/etc/server1.pem 
UrlGroup ".*"
BackEnd 192.168.1.78,80,1
EndGroup

ListenHTTPS 192.168.1.17,444 /usr/local/etc/server2.pem 
UrlGroup ".*"
BackEnd 192.168.1.16,80,1
EndGroup

i.e. if you try to connect to https://192.168.1.17:444 pound gives a 
response from BackEnd 192.168.1.78,80,1 !!

/NB. The pound version is v1.10/

And apologies for the last 2 posts before thinking, this one I'm pretty 
sure is an issue....

Regards,
Malcolm.
 

-- 
To unsubscribe send an email with subject 'unsubscribe' to pound(at)apsis.ch.
Please contact roseg(at)apsis.ch for questions.
http://www.apsis.ch/pound/pound_list/archive/2007/2007-06/1180987028000


Re: [Pound Mailing List] Which brings me to what I was origionaly looking at...
Robert Segall <roseg(at)apsis.ch>
2007-06-05 07:58:36 [ SNIP ]
On Mon, 2007-06-04 at 20:57 +0100, Malcolm wrote:
> With the following config all requests go to the backend in the first 
> group irrespective of the service accessed?
> 
> ListenHTTPS 192.168.1.21,443 /usr/local/etc/server1.pem 
> UrlGroup ".*"
> BackEnd 192.168.1.78,80,1
> EndGroup
> 
> ListenHTTPS 192.168.1.17,444 /usr/local/etc/server2.pem 
> UrlGroup ".*"
> BackEnd 192.168.1.16,80,1
> EndGroup
> 
> i.e. if you try to connect to https://192.168.1.17:444 pound gives a 
> response from BackEnd 192.168.1.78,80,1 !!
> 
> /NB. The pound version is v1.10/
> 
> And apologies for the last 2 posts before thinking, this one I'm pretty 
> sure is an issue....

I think what you really want is

ListenHTTPS 192.168.1.21,443 /usr/local/etc/server1.pem 
ListenHTTPS 192.168.1.17,444 /usr/local/etc/server2.pem 

UrlGroup ".*"
BackEnd 192.168.1.78,80,1
BackEnd 192.168.1.16,80,1
EndGroup

-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904


Re: [Pound Mailing List] Which brings me to what I was origionaly looking at...
lists <lists(at)loadbalancer.org>
2007-06-05 09:13:16 [ SNIP ]
Robert Segall wrote:
>
> I think what you really want is
>
> ListenHTTPS 192.168.1.21,443 /usr/local/etc/server1.pem 
> ListenHTTPS 192.168.1.17,444 /usr/local/etc/server2.pem 
>
> UrlGroup ".*"
> BackEnd 192.168.1.78,80,1
> BackEnd 192.168.1.16,80,1
> EndGroup
>
>   
Robert,

Thank you, but does that mean that both https certs/ports will be load 
balanced over the two servers?
I'd like to have the first cert/port go to one backend and the second 
cert/port go to the other backend.
Is that possible with Pound?

Thanks,
Regards,
Malcolm.



Re: [Pound Mailing List] Which brings me to what I was origionaly looking at...
Robert Segall <roseg(at)apsis.ch>
2007-06-05 09:29:20 [ SNIP ]
On Tue, 2007-06-05 at 08:13 +0100, lists wrote:
> Thank you, but does that mean that both https certs/ports will be load 
> balanced over the two servers?
> I'd like to have the first cert/port go to one backend and the second 
> cert/port go to the other backend.
> Is that possible with Pound?

Only with 2.x, with 1.x you'll need two separate instances.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904


Re: [Pound Mailing List] Which brings me to what I was origionaly looking at...
lists <lists(at)loadbalancer.org>
2007-06-05 09:45:30 [ SNIP ]
Robert,

Ah, that explains it, thanks.


Robert Segall wrote:
> On Tue, 2007-06-05 at 08:13 +0100, lists wrote:
>   
>> Thank you, but does that mean that both https certs/ports will be load 
>> balanced over the two servers?
>> I'd like to have the first cert/port go to one backend and the second 
>> cert/port go to the other backend.
>> Is that possible with Pound?
>>     
>
> Only with 2.x, with 1.x you'll need two separate instances.
>   


MailBoxer