[PATCH] Added the $proxy_protocol_server_{addr,port} variables

# HG changeset patch # User Chris Branch # Date 1516111627 0 # Tue Jan 16 14:07:07 2018 + # Node ID 5cd4799781372a9d405b3d8e62f39ca3c76720c6 # Parent 93abb5a855d6534f0356882f45be49f8c6a95a8b Added the $proxy_protocol_server_{addr,port} variables. diff -r

[PATCH] Tests: added tests for proxy_protocol_server_{addr, port} variables

# HG changeset patch # User Chris Branch # Date 1516111868 0 # Tue Jan 16 14:11:08 2018 + # Node ID 1c5977148c79eba0f14e60df134a7cace77d3207 # Parent 6ca8b38f63b61c6c00ac4c9e355a7909dbb6aeb2 Tests: added tests for proxy_protocol_server_{addr,port} variables.

Re: yield 499 while reading client body and client prematurely closed connection

Hello! On Mon, Jan 15, 2018 at 09:59:53PM -0800, tokers wrote: > # HG changeset patch > # User Alex Zhang > # Date 1516079440 -28800 > # Tue Jan 16 13:10:40 2018 +0800 > # Node ID 9ca5af970d2296a02acefb3070237c5f52119708 > # Parent

Fix "header too long" error

# HG changeset patch # User Vadim Fedorenko # Date 1516103689 -10800 # Tue Jan 16 14:54:49 2018 +0300 # Node ID deaa364977488f3390d48306c34dc80961e54e14 # Parent fbf6a421212b291cbacfcfc503173c0168449165 Fix "header too long" error This error occurs in rare cases