On Tue, Jul 21, 2009 at 9:38 AM, indika kumara <[email protected]>wrote:
> yes asankha , > > I thought, it may be possible to read HTTP request headers before the > SSL handshake is finished and the pick based on URI header what is the > service name and then pick correct SSL context. I was wrong. Before > the SSL handshake is finished, it seems impossible to read Http > headers. Therefore, when synapse need to present multiple identities > as servers, need to have different https listeners. +1. I guess this is the only solution we got in the listener side. Thanks, Hiranya > > > Thanks > Indika > > > > > Indika is also mentioning another - slightly different scenario, where > > Synapse needs to present multiple server certificates to its clients - > > however, this requires listening on multiple ports - and I do not think > > there is any other possibility at all to get around it. But this could > > be achieved fairly easily by allowing multiple https listeners on > > multiple sockets > > > > cheers > > asankha > > > > -- > > Asankha C. Perera > > AdroitLogic, http://adroitlogic.org > > > > http://esbmagic.blogspot.com > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Hiranya Jayathilaka Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
