srcache-nginx-module cache response other than 200.

harshad.yeola · 2015-09-17T17:03:51+00:00

Hello! On Mon, Sep 14, 2015 at 9:34 PM, Martin Gee wrote: > I have a shared library I'm loading using ffi.load > > I'd like use the error log from...

srcache-nginx-module cache response other than 200.

harshad.yeola

Hi ,

I am using WordPress with redis as page cache. I have installed nginx with srcache-nginx-module.

I have explicitely define in nginx config which response is to be cached. Still sometimes it cache non 200 response.

Here is part of my configuration.

location /redis-fetch {
    internal  ;
    set $redis_key $args;
    redis_pass  127.0.0.1:6379;
}
location /redis-store {
    internal  ;
    redis2_query  set $arg_key $echo_request_body;
    redis2_query expire $arg_key 3600;
    redis2_pass  redis_localhost;
}

location ~ \.php$ {

  set $key "nginx-cache:$scheme$request_method$host$request_uri";
  try_files $uri =404;
  
  srcache_store_statuses 200;
  srcache_fetch_skip $skip_cache;
  srcache_store_skip $skip_cache;

  srcache_response_cache_control off;

  srcache_fetch GET /redis-fetch $key;
  srcache_store PUT /redis-store key=$key;
  add_header X-Cache $srcache_fetch_status;
  #add_header X-Cache-2 $srcache_store_status;

  include fastcgi_params;
  fastcgi_pass php;
}

I am still getting this issue frequently.

agentzh

Hello!

On Thu, Sep 17, 2015 at 5:03 PM, Harshad Yeola wrote:
> I am using WordPress with redis as page cache. I have installed nginx with
> srcache-nginx-module.
> I have explicitely define in nginx config which response is to be cached.
> Still sometimes it cache non 200 response.
> Here is part of my configuration.
>

Apparently you need to provide more details for the issue. Otherwise I
cannot debug the issue for you. It'll be best if you can provide a
*minimal* and *standalone* example that can easily reproduce the issue
on *my* side. Failing that, please provide the *complete* nginx
debugging logs for the very guilty request storing the non-200
responses and the subsequent request fetching it.

Also, you are recommended to try out the latest OpenResty formal
release if you are not using it already.

Please check out the following document for more details on reporting
a problem effectively:

http://openresty.org/faq.html#how-should-i-report-a-problem

Oh, BTW, you may want to enable the connection pool for redis via the
standard keepalive directive in the upstream {} block. This can give a
nice speedup and you don't have to worry exhaust the port range.

Regards,
-agentzh