My understanding is that abrupt client disconnects are transparent through nginx -- the connection to upstream is closed and the upstream should handle that as it can. Please correct me if I am wrong. Is there a way to use a call-back (or something similar, a redirect), in nginx.conf, for client disconnects? This would be useful when the upstream is not good at directly handling the disconnect (nby George Nica - Nginx Mailing List - English
Thank you Maxim. Adding an extra variable to the spnego auth module sounds intriguing, but also challenging because; as you mention "rate limiting happens before access checks" and this module mainly deals with access checks until now. Sounds like an extra level of proxying is the way ahead for now. It would be nice if Kerberos were supported directly by nginx. :)by George Nica - Nginx Mailing List - English