This subject has been discussed here:
https://trac.nginx.org/nginx/ticket/923
I think it is a good idea to have this support.
On Sun, Jul 9, 2017 at 7:55 PM, motor <nginx-forum at forum.nginx.org> wrote:
> The following post is based on the assumptions that 1. upstream HTTP/2
> support is not available in nginx at the moment, and 2. said feature is not
> firmly excluded from nginx's future road map :)
>> We've been internally using an nginx patch (authored by me) which provides
> this feature in our nginx instances that front-end etcd servers.
> Please let me know if this patch can be a candidate for review and
> potential
> merge.
>> In case the answer is yes, a heads up: said implementation has been subject
> to a few 'compromises' due to internal deadlines, so I might need a fair
> bit
> of technical guidance/discussion to iron out some design/implementation
> issues.
>> Posted at Nginx Forum: https://forum.nginx.org/read.> php?2,275391,275391#msg-275391
>> _______________________________________________
> nginx mailing list
>nginx at nginx.org>http://mailman.nginx.org/mailman/listinfo/nginx>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20170709/b38a6cb9/attachment-0001.html>