On Wed, Aug 5, 2015 at 12:41 AM, Thomas Ward wrote:
>
> > On Aug 4, 2015, at 19:11, Mike MacCana wrote:
>
> > Would nginx accept a patch to include dh_params in the example config?
> I have it on good authority that Maxim or someone has a diff planned to
> change defaults so a patch for that p
Hello all,
I am currently developing an nginx module in order to implement a software
component in our platform.
This module's responsibility is to receive upstream requests, forward them to
multiple hosts (one host per pool, with N pools; we call a pool a shard),
receive all the responses an
Hello!
On Wed, Aug 5, 2015 at 7:21 PM, Maxime Henrion wrote:
> I am currently developing an nginx module in order to implement a software
> component in our platform.
>
> This module's responsibility is to receive upstream requests, forward them to
> multiple hosts (one host per pool, with N poo
I'm happy to publish the first alpha version of the HTTP/2 module.
Please, follow the link to download the patch and to get instructions:
- http://nginx.org/patches/http2/
You can also find additional information in the blog post:
- https://www.nginx.com/blog/early-alpha-patch-http2/
Thanks
Hello!
On Wed, Aug 05, 2015 at 11:21:52AM +, Maxime Henrion wrote:
[...]
> NOTE: I'm not sure whether NGX_DONE above is the correct enum
> value to use, but I have tried NGX_AGAIN and others as well to
> no avail.
NGX_DONE is correct return code. Compare with proxy and/or dav
modules co
