Got a question regarding the worker_connections configuration. Is a
worker_connection
essentially
a tcp socket connection or http session?
Via the http_stub_status_module, I can see there are
connections in waiting state, but any new request
will result in a "worker connections are not enough"
ale
On 24/08/2018 08:59:09, James Beal wrote:
We currently use caching for guests, our search pages use long urls to pass the
parameters to our application. Currently searches that worked for logged in
users don't work for guests.
I can show the issue with these two curl examples ( which are not o
This seems intentional, per the documentation at
http://nginx.org/en/docs/http/ngx_http_gzip_static_module.html:
"The following directives are also taken into account: gzip_http_version,
gzip_proxied, gzip_disable, and gzip_vary."
No mention of gzip_types. I recommend only enabling gzip_static in
Thank you for that explanation. I'm still debugging this with our CDN vendor.
They have identified a number of bugs on their end which explain the odd
behavior I've been seeing.
___
Michael Friscia
Office of Communications
Yale School of Medicine
(203) 73
I've noticed for a while that when gzip_static is enabled it checks *every*
file it serves for a .gz extension, not just the ones listed in the gzip_types.
For example in a page with 1 html and 30 images you'll have 61 requests to the
file system: 1 for the correct .html.gz file, 30 for the non-
We currently use caching for guests, our search pages use long urls to pass the
parameters to our application. Currently searches that worked for logged in
users don't work for guests.
I can show the issue with these two curl examples ( which are not obviously
valid searches )
As a guest
jame