On 2014-02-03 19:01, Valentin V. Bartenev wrote:
> Sorry for the late answer.
Hi! No problem at all!
> This behavior cannot be avoided since even if you do not advertise SPDY via
> NPN/ALPN for some virtual hosts, but do for another, then browsers still be
> able to request any of them using a
On Thursday 23 January 2014 15:54:58 Alex wrote:
> > On Thu, Jan 23, 2014 at 11:17:42AM +, Pankaj Mehta wrote:
>
> Hi,
>
> > These blocks have different ssl certificates. I understand that if I enable
> > SNI in nginx and the client supports it, then we have a predictable
> > behaviour where
Thanks Maxim, very helpful.
Pankaj
On 23 January 2014 11:49, Maxim Dounin wrote:
> Hello!
>
> On Thu, Jan 23, 2014 at 11:17:42AM +, Pankaj Mehta wrote:
>
> > Hi,
> >
> > I am struggling to get any documented reference for my problem in nginx
> > docs. Hope someone can help before I delve i
> On Thu, Jan 23, 2014 at 11:17:42AM +, Pankaj Mehta wrote:
Hi,
> These blocks have different ssl certificates. I understand that if I enable
> SNI in nginx and the client supports it, then we have a predictable
> behaviour where nginx will use the correct ssl parameters from the server
> blo
Hello!
On Thu, Jan 23, 2014 at 11:17:42AM +, Pankaj Mehta wrote:
> Hi,
>
> I am struggling to get any documented reference for my problem in nginx
> docs. Hope someone can help before I delve into nginx code:
>
> I want to have multiple server blocks for the https port 443, they will
> serv
Hi,
I am struggling to get any documented reference for my problem in nginx
docs. Hope someone can help before I delve into nginx code:
I want to have multiple server blocks for the https port 443, they will
serve different hostnames. Each block will have it's own ssl configuration.
For example:
