Re: Fwd: Default certificate wrongly delivered.

On Sat, Feb 23, 2013 at 2:07 PM, Baptiste wrote: > Note that you can also send the SNI in a HTTP header, like: > > http-request set-header X-SSL-SNI %[ssl_fc_sni] > > cheers > > Excellent idea! Thanks! Cheers, Kenneth

Re: Fwd: Default certificate wrongly delivered.

Note that you can also send the SNI in a HTTP header, like: http-request set-header X-SSL-SNI %[ssl_fc_sni] cheers On Sat, Feb 23, 2013 at 12:59 PM, Kenneth Mutka wrote: > On Sat, Feb 23, 2013 at 12:47 PM, Willy Tarreau wrote: >> >> Hi, >> >> On Sat, Feb 23, 2013 at 08:54:17AM +0100, Kenneth

Re: Fwd: Default certificate wrongly delivered.

On Sat, Feb 23, 2013 at 12:47 PM, Willy Tarreau wrote: > Hi, > > On Sat, Feb 23, 2013 at 08:54:17AM +0100, Kenneth Mutka wrote: > > On Fri, Feb 22, 2013 at 4:14 PM, Lukas Tribus > wrote: > > > > > If you upgrade to a recent snapshot you can use the strict-sni feature > > > [1]. This way, when th

Re: Max Sessions and source balancing

On Thu, Feb 21, 2013 at 11:09:22AM -0800, Bryan Talbot wrote: > I believe the answer to both of your questions is "no". > > The configuration directives you've specified will be followed: if more > than maxconn concurrent requests are needed for a particular server, > additional requests will be q

Re: Fwd: Default certificate wrongly delivered.

Hi, On Sat, Feb 23, 2013 at 08:54:17AM +0100, Kenneth Mutka wrote: > On Fri, Feb 22, 2013 at 4:14 PM, Lukas Tribus wrote: > > > If you upgrade to a recent snapshot you can use the strict-sni feature > > [1]. This way, when the client doesn't provide SNI, the handshake is > > aborted. > > > > I'

Re: [PATCH 1/7] Correct logic in cut_crlf()

On Wed, Feb 20, 2013 at 06:33:08AM +0100, Krzysztof Olędzki wrote: > On 2013-02-13 09:48, Simon Horman wrote: > > > >>And add: > >>while (*s == '\r' || *s == '\n') > >>before "*s++ = '\0';" > >> > >>.. so we properly split "line1\r\nline2". > > > >I see cut_crlf used to truncate strings at th