10 messages in ru.sysoev.nginxRe: ngx_http_memcached_module question
FromSent OnAttachments
Sean AllenFeb 28, 2008 2:08 pm 
Igor SysoevFeb 29, 2008 8:27 am 
Sean AllenFeb 29, 2008 9:58 am 
Sean AllenFeb 29, 2008 10:25 am 
Sean AllenFeb 29, 2008 11:02 am 
Sean AllenFeb 29, 2008 12:19 pm 
Igor SysoevFeb 29, 2008 12:35 pm 
Igor SysoevFeb 29, 2008 12:38 pm 
Sean AllenFeb 29, 2008 12:58 pm 
Igor SysoevFeb 29, 2008 1:02 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: ngx_http_memcached_module questionActions...
From:Sean Allen (sean@public.gmane.org)
Date:Feb 29, 2008 11:02:25 am
List:ru.sysoev.nginx

On Feb 29, 2008, at 1:25 PM, Sean Allen wrote:

On Feb 29, 2008, at 11:28 AM, Igor Sysoev wrote:

On Thu, Feb 28, 2008 at 05:09:18PM -0500, Sean Allen wrote:

can i do the following:

check memcache for existence of content.

if not continue our normal processing which is currently:

check for static file if it exists, serve it if it doesnt exist, pass request off to upstream server.

The checking local file is faster than memcached, so:

location / { error_page 404 = @memcache; }

location @memcache { set $memcached_key "$uri?$args"; memcached_pass ...

recursive_error_pages on;

error_page 404 = @upstream; }

location @upstream { proxy_pass ...

error_page 404 = @upstream; }

I think I might have this working by moving recursive_error_pages on; into my server { } defs.

this should fill my error log with tons of error messages correct?

well ok so far, it works partially. got the 502 error figured out.

any code that does a redirect, results in 405 error. been digging for an answer. any ideas?

also is there a way to not have all these requests end up in the error log as file not found?