11:04 1-10-2015 nginx 188.8.131.52 Kitty
Whats small and slender red and peach, blue eyes, white face with
whiskers, pink bow ? She ain't really that nice, she ain't even
pretty but she gets the job done so here’s Kitty! Remember kids,
as long as it SMELLS like orange juice, you can drink it.
The nginx Kitty release is here!
Based on nginx 1.9.6 (29-9-2015) with;
+ lua-nginx-module v0.9.17 (upgraded 29-9-2015, *_by_lua_block)
+ nginx-module-vts (fix for nginx starttime going haywire)
* prove06 is still being worked on
+ Source changes back ported
+ Source changes add-on's back ported
+ Changes for nginx_basic: Source changes back ported
* Known broken issues: ajp cache
* Scheduled release: no, maintenance release, h2/Lua fixes
* Additional specifications: see 'Feature list'
Builds can be found here:
Follow releases https://twitter.com/nginx4Windows
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261976,261976#msg-261976
Anyone know how the least_conn upstream option works in nginx plus?
"Specifies that a group should use a load balancing method where a request
is passed to the server with the least average response time and least
number of active connections, taking into account weights of servers"
How does nginx plus use the three variable to determine which server to
Is the "total" weight dynamically determined as: weight * 1/response time *
active connections or some other formula?
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261971,261971#msg-261971
I just migrated a new customer to nginx/php-fpm and notice a considerable
delay with requests.
nginx Version 1.9.5 compiled from rpm with http/2
I noticed that the site was slower with an avg ttfb of ~1.1s.
Only until i got to test static assets did i discover that the time to first
byte for js/css was the same 1.1s.
Switching to nginx 1.8 bring the response time back to normal of ~0.145.
Did i stumble on a bug?
Anything i can give you guys to troubleshoot this figure out why 1.9.5. is
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,261944,261944#msg-261944
I tried the 1.9.5 release with http2 and it worked fine, but Ajax request
especially were problematic.
I did get errors like:
And the status code was 0. With the former spdy support I didn't have any
problems. I'm also using fastcgi and PHP5 in this server where I tried it.
What could cause these problems?