<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">Are the any plans to add this feature?</div><div class="">If one has less software to run stuff, and if hitch can be avoided in some use cases, I think that would be a plus.</div><div class=""><br class=""></div><div class="">Thanks for you answer.</div><div class=""><br class=""><div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Best Regards,</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Danila</div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 13 Sep 2018, at 21:42, Maxim Dounin <<a href="mailto:mdounin@mdounin.ru" class="">mdounin@mdounin.ru</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello!<br class=""><br class="">On Thu, Sep 13, 2018 at 09:26:31PM +0300, Danila Vershinin wrote:<br class=""><br class=""><blockquote type="cite" class="">Hello,<br class=""><br class="">I’m trying to basically use nginx as replacement to hitch (for Varnish).<br class=""><br class="">Request goes like this: browser → nginx (stream SSL) → varnish (HTTP2 on) → backend HTTP<br class=""><br class="">stream {<br class=""> server {<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>listen 443 ssl;<br class=""> ssl_certificate /etc/letsencrypt/live/<a href="http://example.com/fullchain.pem" class="">example.com/fullchain.pem</a>;<br class=""> ssl_certificate_key /etc/letsencrypt/live/<a href="http://example.com/privkey.pem" class="">example.com/privkey.pem</a>;<br class=""> proxy_pass 127.0.0.1:6081;<br class=""> proxy_protocol on;<br class=""> }<br class="">}<br class=""><br class="">With the above, I’m getting HTTP/1.1 in browser.<br class="">When I replace nginx with hitch, I get HTTP/2.<br class=""><br class="">From Hitch docs: "Hitch will transmit the selected protocol as part of its PROXY header” Does nginx have same capability?<br class=""><br class="">In general, is nginx capable of being SSL terminator for HTTP/2 backends using TCP streams? (while delivering HTTP/2 to supporting clients). I’m interested in using TCP streams since only those will allow use of PROXY protocol to upstream.<br class=""></blockquote><br class="">Currently no, as stream module in nginx cannot be configured to <br class="">choose a parituclar ALPN protocol when terminating SSL.<br class=""><br class="">-- <br class="">Maxim Dounin<br class=""><a href="http://mdounin.ru/" class="">http://mdounin.ru/</a><br class="">_______________________________________________<br class="">nginx mailing list<br class="">nginx@nginx.org<br class="">http://mailman.nginx.org/mailman/listinfo/nginx</div></div></blockquote></div><br class=""></div></body></html>