Yes, the content is dynamic, basically a set of JSON RESTful applications we
call feeds that for specific reasons we do not cache but most we do. The
use-case is simple, if we have to release new code these feeds are
down/returning a 503 error but if we had a cache that would serve stale during
Sure is. Look at the stale-if-error stale-while-revalidate
proxy_cache_use_stale proxy_cache_lock etc
Can you describe the use case a bit more? Why don't you want to cache this
particular content?
Is it that its dynamic and a fresher version is always preferable but the stale
is good enough in
I try to use nginx + grpc + grpc-web client JS library
(https://github.com/grpc/grpc-web).
Nginx-1 is compiled using the following setup:
nginx version: nginx/1.15.0
built by gcc 7.2.0 (Ubuntu 7.2.0-8ubuntu3.1~16.04.york0)
built with OpenSSL 1.0.2g 1 Mar 2016
TLS SNI support ena
I’m working through use cases for cache in a presentation and had a thought
jump into my head. We have a server block where most things are cached, but a
few locations are set not to use the cache. But the thought is that even
thought we don’t want to use a local cache and always fetch from upst
Hello!
On Wed, Jun 27, 2018 at 08:25:38PM -0400, Danomi Czaski wrote:
> I get 400 bad request when client certs are used early even though I
> have ssl_verify_client optional.
>
> nginx: [info] 9612#0: *338 client SSL certificate verify error:
> (9:certificate is not yet valid) while reading cli
*That is
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,280293,280320#msg-280320
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
What is not work: nginx immediately returns "502 Bad Gateway" to the client
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,280293,280319#msg-280319
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi everyone,
I've tree different jenkins machine , for serving behing the NGINX.
My sample nginx file shown as below . I have tree different file each
machine .
server {
listen 80;
server_name "";
access_log off;
location /USERNAME {
proxy_pass http:/
> On 28 Jun 2018, at 03:25, Danomi Czaski wrote:
>
> I get 400 bad request when client certs are used early even though I
> have ssl_verify_client optional.
>
> nginx: [info] 9612#0: *338 client SSL certificate verify error:
> (9:certificate is not yet valid) while reading client request header
