Ok,
What about the other way around. Is it possible to disable http2 for one
server block, via config or via code?
Other than that, what are the alternatives? One listen on one IP for http2
and on another for http1?
Thanks!
On Thu, Jun 23, 2016 at 7:06 AM, itpp2012
wrote:
> Valentin V. Barten
Hi,
Is it possible to enable http2 in only one of several name-based servers?
I have the following scenario:
server {
listen 443 ssl;
server_name www.example.com;
ssl_certificate www.example.com.crt;
...
}
server {
listen 443 ssl http2;
server_name
2016 at 6:47 AM, B.R. wrote:
> Testingin production?
> Well you are not the only one... far from that.
>
> There are other means to create 'realistic' traffic on benches, provided
> you are thinking those tests well, though.
> ---
> *B. R.*
>
> On Mon, Jan
.
On Sun, Dec 20, 2015 at 11:04 AM, Valentin V. Bartenev
wrote:
> On Friday 18 December 2015 15:55:47 Marcelo MD wrote:
> > Hi,
> >
> > Recently we added a 'thread_pool' directive to our main configuration. A
> > few hours later we saw a huge increa
Hi,
Recently we added a 'thread_pool' directive to our main configuration. A
few hours later we saw a huge increase in the connections_writing stat as
reported by stub_status module. This number reached +- 3800 and is stuck
there since. The server in question is operating normally, but this is ver
