Hello Costin, thank you very much for your reply.
> -----Original Message----- > From: Costin Manolache [mailto:cos...@gmail.com] > Sent: Tuesday, May 29, 2012 9:09 AM > To: Tomcat Developers List > Subject: Re: Possible IIS SPDY Redirector for Tomcat > > > For server-to-server ( i.e. IIS to tomcat ) you shouldn't need NPN or > SSL. > SSL may make sense. You would need to set the tomcat connector to > accept > non-NPN/SSL connections. [...] > Same, it should be possible to tweak tomcat connector to not require > compression. Ok, that would be cool if Tomcat can be configured that header compression and NPN should not be used (or no SSL at all). SSL/TLS connections (without NPN) are supported natively by .Net so that a NPN TLS tunnel wouldn't be needed then. > Google servers (AFAIK) support both 2 and 3. > > I'm working on a 3 implementation for tomcat - the hard part is the > flow > control. The even harder part is finding time to work on it... Ok, thank you for your efforts! > > IMHO this is the right thing to do - with SPDY you'll also be able to > proxy > to other servers (nodejs, jetty, etc). Disabling NPN/compression should > be > very easy - but there are some missing things in 'proxy mode' - in > particular ability to pass the 'source IP', info about original certs, > etc. > Each is relatively simple ( define an X-header, cut&paste from ajp impl > ) > > > Costin Yes, I agree. I could modify the SPDY redirector so that it appends x-headers for the client IP etc. (but currently I don't know much about transferring certificates - is that what "CREDENTIAL" frame in SPDY is for?) Thanks! Regards, Konstantin Preißer --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
