|
Going a step further: If it's more or less just a router, is there any special
treatment for any of the various service types? Isn't
specifying protocol "udp" vs "tcp" enough then?
Thanks,
MARK
> -----Original Message-----
> From:
> lvs-users-bounces+msalists=gmx.net@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:lvs-users-bounces+msalists=gmx.net@linuxvirtualserver.
> org] On Behalf Of Mark
> Sent: Tuesday, October 25, 2005 11:01 AM
> To: 'LinuxVirtualServer.org users mailing list.'
> Subject: RE: Please Help for my https problem~!
>
>
> > > Since there seems to be a lot of problems with configuring https,
> > > can somebody comment on what the LVS engine does differently for
> > > http and https mode?
> >
> > nothing. The director is just a router with slightly
> > different rules than a regular layer-4 router, but it's
> > still a router. It doesn't look at the content of packets
> > or treat port 443 any differently than any other port.
> >
>
> That's what I first thought too. But then I have 2 stupid
> questions: why are there 2 options for http and https if they
> do the same
> thing? And more importantly - why did one of them work and
> the other one didn't? Are you sure that it doesn't start doing
> certificate checks or something like that?
> I think I remember getting some error message in the
> ldirectord logs regarding mismatch between certificate name
> and requested URL
> or something like that when I was using "service=https".
> After I changed it to "service=http" it worked.
>
> Thanks,
>
> MARK
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
