I'm running a SAAS service running via NGINX and have been running tcpdump
to look at the incoming packets for HTTP queries. Many of the HTTP queries
are bigger than the MTU of 1,500 bytes and therefore arrive as 2, 3, or 4
packets. I noticed that for some customers there are significant delays
bet
Hi Maxim,
Thank You for your answer. It really makes sense, however, in the
mentioned case, I could see an elevation of the number of occurrences just
after the migration from nginx 1.6 to nginx 1.8.
This behaviour affects < 0.2 % of our requests, but it means hundreds of
requests per ho
Hello!
On Thu, Sep 10, 2015 at 01:30:46PM -0400, biazus wrote:
> Hey Guys,
>
> I've been using nginx 1.8.0 for a couple of months, and I noticed a critical
> message at error log informing that "cache file has too long header".
>
> 2015/09/10 17:11:03 [crit] 27245#0: *10686 cache file
> "/data
Hey Guys,
I've been using nginx 1.8.0 for a couple of months, and I noticed a critical
message at error log informing that "cache file has too long header".
2015/09/10 17:11:03 [crit] 27245#0: *10686 cache file
"/data/smallfiles/http/6/d8/f5df8d6eda60819319688d1bc0cb2d86" has too long
header
Ho
After frustration on this, I decided to make a simple web service to solve
it. Please see http://www.nginxformatter.com :).
Enjoy :)
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,250211,261555#msg-261555
___
nginx mailing list
nginx@nginx.o
Hello Folks,
How can we remove request url being logged in nginx error logs. For example
it looks something like:
2015/09/01 15:26:03 [error] 30547#0: *208725 upstream prematurely closed
connection while reading response header from upstream, client:
123.123.50.44, server: test.example.com, reque
I'll also be stuffing my suitcase as much as I can with cool hardware to
play with at the Google Cloud sponsored Hackday event on the Tuesday of
the conference.
This is aimed at the developers / devops / sysadmins out there who won't
be doing our training classes. It will be a great day to hack on
