8 ms·
Sorry for the confusion. HTTP and HTTPS (both version 1 and 2) are supported for downstream connections (i.e. connection bet. H2O and web browsers). Only plain
by kazuho 12y ago
Sorry for the confusion.
HTTP and HTTPS (both version 1 and 2) are supported for downstream connections (i.e. connection bet. H2O and web browsers).
Only plain-text HTTP/1 is supported for upstream connections (connection bet. H2O and web application servers).
- PythonicAlpha 12y agoThank you very much for the answer! To clarify for my mind: Can I than use H2O to connect to a web-browser via HTTPS and H2O is routing the same request upstream via HTTP to a web application server? (that of course would suffice for me).
- kazuho 12y agoYes, assuming that you wanted to say: "web-browser connect to H2O via HTTPS".
- PythonicAlpha 12y agoOf course! Excuse my bad English!
- mp3geek 12y agoIs spdy supported?
- rgbrenner 12y agospdy == http 2
- PythonicAlpha 12y agoIs it really the same (really asking)?? Sometimes there are subtle protocol changes, when something is standardized -- and as much I understand, HTTP/2 took a while ...
- rgbrenner 12y agothe initial http 2.0 draft was just a copy of spdy (in nov 2012). There have been changes to 2.0, so they aren't exactly the same.. but http 2.0 is meant to completely replace spdy. Any of the servers/clients that support spdy currently will eventually make the minor changes, and call it http 2.0.
- michaelchisari 12y agoDon't be afraid to not add features. I'd love to see something like this stay as a very high speed server, especially with the move towards single-page static apps that connect to restful services. There's plenty of kitchen sinks out there.