Welcome! Log In Create A New Profile

Advanced

Re: How to close client HTTP/2 connections?

November 23, 2018 09:32AM
> Why do you want to do this?

In a cluster of many nginx servers we had one faulty node that was delivering only errors. In that special case a default vhost replied an "domain not configured" error, because the underlying configuration was inaccessible. The health check was not firing, because such errors are normal (bad bots try to access removed domains or simply make up host headers).

A client that was round-robin balanced to that faulty nginx instance was delivered the error page, but the connection was still active. Every subsequent request to our domain had hit the same bad instance. The google bot uses each connection for 100 requests. They all ran into the error. Same for browsers: When you hit reload, you will run into the same problem until the connection times out.

If the connection was closed immediately there would be a good chance to be load-balanced to another instance.

In http/1 "Connection: close" does the job. but most of our traffic is h2.
Subject Author Posted

How to close client HTTP/2 connections?

filex November 23, 2018 03:49AM

Re: How to close client HTTP/2 connections?

Olaf van der Spek November 23, 2018 09:11AM

Re: How to close client HTTP/2 connections?

filex November 23, 2018 09:32AM

Re: How to close client HTTP/2 connections?

Olaf van der Spek November 23, 2018 09:49AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 181
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready