5 ms·

Do I understand this right? It supports HTTP/2, but doesn't support HTTPS. Therefore it supports HTTP/2 in a mostly unusable form, because browser vendors (for

by hannob 10y ago

Do I understand this right? It supports HTTP/2, but doesn't support HTTPS. Therefore it supports HTTP/2 in a mostly unusable form, because browser vendors (for good reasons) decided to support HTTP/2 only over HTTPS.

ruben_varnish 10y ago
Yes, Varnish does h2c so for HTTPS you will need something like 1.4 or later: https://hitch-tls.org/ https://hitch-tls.org/ Made by Varnish Software to provide a "browser-vendor-compliant" HTTP/2 stack.
- jamwt 10y ago
  Hmm... you guys sure have pretty thoroughly sanitized all references to Stud at this point in code, documentation, READMEs, etc. :-(
  - lkarsten 10y ago
    Hi jamwt. We haven't forgotten your(?) excellent work on stud! Both changes.rst and the man page explain where Hitch came from. Hitch has seen significant changes since we forked stud 0.3.2, for example proper reload/sighup support, an improved configuration format, and OCSP stapling. Running it on a large scale (cert/ip -wise) also works better now. If you're ever in our parts of the world, let us know and we'll buy you some beers/coffee/$beverage and tell you all about how your old project is doing.
    - phkamp 10y ago
      Pssst, jamwt! Don't let them buy you beer. Insist on tasting their homebrew instead.
  - ruben_varnish 10y ago
    The reference to Bump is also on the copyright notice on the license file. As Lasse pointed out, we never meant to take away any merit from your work. If you feel we could highlight the Hitch's origin from Stud better, let us know how. We are open to suggestions. And yes, if you ever come to Oslo, you have an open invitation to come by an test our homebrew :)
vertex-four 10y ago
You could put a TLS proxy in front of it, I think? Though you'd have to implement ALPN or NPN in the proxy. (Apparently Hitch, above, does.)
phkamp 10y ago
The reason I don't want to link Varnish against a SSL library, is that in my considered opinion, they all suck. From a purely operational point of view, you are better of with two different SSL proxies in front if your Varnish (or other webserver), so that you can turn OpenSSL off in even-numbered weeks and the other (pick your poison) in odd-numbered weeks. The code to hold safely onto your certificate and do all the songs and dances involved in SSL/TLS, is under all circumstances something which should be isolated in as small a process/protection domain as possible.
- encoderer 10y ago
  This is why i love hn. Thanks for answering this!
- convolvatron 10y ago
  they do. they really do. i've read your screed about this and i completely agree. absolutely appalling. in particular a marked inability to handle thread concurrency, which is pretty fatal to varnish. however. given that tls is operationally important. and using an additional proxy causes a lot of configuration and performance headaches. isn't there any better path forward?

by hannob 10y ago

ruben_varnish 10y ago

Yes, Varnish does h2c so for HTTPS you will need something like 1.4 or later: https://hitch-tls.org/ https://hitch-tls.org/ Made by Varnish Software to provide a "browser-vendor-compliant" HTTP/2 stack.

jamwt 10y ago
Hmm... you guys sure have pretty thoroughly sanitized all references to Stud at this point in code, documentation, READMEs, etc. :-(
- lkarsten 10y ago
  Hi jamwt. We haven't forgotten your(?) excellent work on stud! Both changes.rst and the man page explain where Hitch came from. Hitch has seen significant changes since we forked stud 0.3.2, for example proper reload/sighup support, an improved configuration format, and OCSP stapling. Running it on a large scale (cert/ip -wise) also works better now. If you're ever in our parts of the world, let us know and we'll buy you some beers/coffee/$beverage and tell you all about how your old project is doing.
  - phkamp 10y ago
    Pssst, jamwt! Don't let them buy you beer. Insist on tasting their homebrew instead.
- ruben_varnish 10y ago
  The reference to Bump is also on the copyright notice on the license file. As Lasse pointed out, we never meant to take away any merit from your work. If you feel we could highlight the Hitch's origin from Stud better, let us know how. We are open to suggestions. And yes, if you ever come to Oslo, you have an open invitation to come by an test our homebrew :)

vertex-four 10y ago

You could put a TLS proxy in front of it, I think? Though you'd have to implement ALPN or NPN in the proxy. (Apparently Hitch, above, does.)

phkamp 10y ago

The reason I don't want to link Varnish against a SSL library, is that in my considered opinion, they all suck. From a purely operational point of view, you are better of with two different SSL proxies in front if your Varnish (or other webserver), so that you can turn OpenSSL off in even-numbered weeks and the other (pick your poison) in odd-numbered weeks. The code to hold safely onto your certificate and do all the songs and dances involved in SSL/TLS, is under all circumstances something which should be isolated in as small a process/protection domain as possible.

encoderer 10y ago
This is why i love hn. Thanks for answering this!
convolvatron 10y ago
they do. they really do. i've read your screed about this and i completely agree. absolutely appalling. in particular a marked inability to handle thread concurrency, which is pretty fatal to varnish. however. given that tls is operationally important. and using an additional proxy causes a lot of configuration and performance headaches. isn't there any better path forward?