Because the certs are parsed when the config is loaded so that you can have a SSL context right from the start. Well before the HTTP layer is touched. If you want dynamic cert loading you have to do it yourself.
At a time I tried that by following a simpler path of modifying stud so that it does on the fly cert loading. Never pursued it further. The thing is you need a context right from the start and then change dynamically to use the server name, AFAICT. Le 9 janv. 2014 20:00, "Larry" <[email protected]> a écrit : > > Thanks, > > I left the cookies out of this context right now I understand. > > But since there is a http request first why doesn't nginx is able to switch > to the right certificate accordingly ? > > Without obliging me to create a new entry for each (which is the route I am > going to take)? > > Posted at Nginx Forum: http://forum.nginx.org/read.php?2,246178,246197#msg-246197 > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
