Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by kazuho on Thursday December 25, 2014 @05:25PM
(#8797368)
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).
Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by michaelchisari on Thursday December 25, 2014 @06:50PM
(#8797541)
Don'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.
Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by PythonicAlpha on Thursday December 25, 2014 @05:43PM
(#8797404)
Thank 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).
Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by kazuho on Thursday December 25, 2014 @06:28PM
(#8797500)
Yes, assuming that you wanted to say: "web-browser connect to H2O via HTTPS".
Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by PythonicAlpha on Thursday December 25, 2014 @06:55PM
(#8797547)
Of course! Excuse my bad English!
Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by mp3geek on Thursday December 25, 2014 @05:48PM
(#8797422)
Is spdy supported?
Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by rgbrenner on Thursday December 25, 2014 @06:17PM
(#8797479)
spdy == http 2
Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by PythonicAlpha on Thursday December 25, 2014 @06:20PM
(#8797487)
Is 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 ...
Re:Show HN: Initial release of H2O, and why HTTPD performanc...
by rgbrenner on Thursday December 25, 2014 @06:24PM
(#8797493)
the 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.
I am not so much into web-servers (yet), but I found this in the feature list:
Are there any plans to add also HTTPS-support for reverse proxy? Since I have to include a secondary (Tornado) web-server unto my stack for dynamic pages.It also puzzled me, that https is not supported, but in the benchmarks I found a part: "HTTPS/2 (reverse-proxy)". As I said, I am not so much in Web-servers and https/2, but that was a little confusing.