Hello!

On Sun, Jul 09, 2017 at 10:55:02PM -0400, motor 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.

Feel free to post the patch to nginx-devel@ mailing list. Some
generic recommendations can be found here:

http://nginx.org/en/docs/contributing_changes.html

As of now another patcheset to introduce HTTP/2 support is being
reviewed, as available here:

http://mailman.nginx.org/pipermail/nginx-devel/2017-June/010209.html

It also have quite a few "compromises" though, so nobody knows
which one is better, at least without seeing your version.

--
Maxim Dounin
http://nginx.org/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx