Hi,
As written in the yaws.conf documentation :
"Yaws can virthost several webservers on the same ip address as well as
several webservers on different ip addresses. The one limitation here
is that there can be only one server with ssl enabled per each individ-
ual ip address."
In my quest for understanding yaws, I'm trying something like that to bypass this limit (I introduce a new configuration
paramater sslvirtual) :
<server www.funky.org>
port = 443
listen = 192.168.128.32
docroot = /var/yaws/www_funky_org
<ssl>
keyfile = /etc/funky.key
certfile = /etc/funky.cert
</ssl>
</server>
<server funky.org>
port = 443
listen = 192.168.128.32
sslvirtual = true
docroot = /var/yaws/www_funky_org
<ssl>
keyfile = /etc/funky.key
certfile = /etc/funky.cert
</ssl>
</server>
with this paramater, funky.org is not bind on the socket {192.168.128.32,443} but added in the group
of #sconf corresponding to the first server (same socket) (like in normal HTTP) . The pick_sconf function in ssl context
do now the same thing that in plain context, by comparing Host header to find the good #sconf.
For the test I added the sslvirtual in #sconf.soptions field. All modifications are done in yaws_server (SSL configuration must be strictly identical, otherwise we need to modify yaws_config:search_sconf ,
because, the search uses "listen,port,ssl,severname" fields).
Details :
yaws_server:do_listen(SC,GC) checks if the sslvirtual flag is set in the #sconf.
if yes, instead of try to bind a socket on {Ip,Port} we just return {nossl,undefined,sslvirtual};
yaws_server:gserv(Top, GC, Group0) check is we do_listen returns something like {_,_,sslvirtual}
if yes, gserv/3 do an proc_lib:init_ack(sslvirtual)
yaws_server:start group receive the sslvirtual and do nothing (return false) (it's like the same case that when failonbind is set to false)
pick_sconf in SSL context do the same thing that pick_sconf without SSL
For the certificate generation, I used the extension subjectAltName (in which I set all virtual hosts).
Seems to work.
Did I Miss Something ?
wde
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@...
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
openssl.cnf (3K) 