# Cache: fix sending of stale responses

**URL:** <https://www.ruby-forum.com/t/cache-fix-sending-of-stale-responses/191881>\
**Category:** NGINX\
**Created:** [July 20, 2010, 8:24am UTC](https://www.ruby-forum.com/t/cache-fix-sending-of-stale-responses/191881 "2010-07-20T08:24:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Davide\_DSAmico](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/eb9ed0/32.png) [@Davide\_DSAmico](https://www.ruby-forum.com/u/Davide_DSAmico)\
**Post date:** [July 20, 2010, 8:24am UTC](https://www.ruby-forum.com/t/cache-fix-sending-of-stale-responses/191881/1 "2010-07-20T08:24:40Z")

</div>

On 19/07/10 20.01, removed\_email\_address@domain.invalid wrote:

> 1. Re: Rewrite Performance Question (Juergen G.)
> 
> come some take a look at these rewrite rules if they are ok regarding  
> }
> 
> > Hi,  
> > ? ? ? ? ? ?rewrite ^(.\*)$ [http://www.forum.de:81](http://www.forum.de:81) last;  
> > }
> 
> _Phillip B Oldham_  
> should be taken regarding content, nor must you copy or show them to anyone.
> 
> > > ? ? ? ? ? ?rewrite ^/(.\*)$ [http://www.forum.de:81/$1](http://www.forum.de:81/$1) permanent;  
> > > server  
> > > Also, in the second server it’s better to use usual names instead of regex:
> 
> Content-Type: text/plain; charset=KOI8-R
> 
> > > > ```
> > > > break;
> > > > 
> > > > ```
> > > 
> > > server  
> > > ;  
> > > To: removed\_email\_address@domain.invalid  
> > > Thanks to Laurence Rowe.  
> > > [Igor Sysoev](http://sysoev.ru/en/)  
> > > Message-ID: [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)
> 
> On Thu, Jul 15, 2010 at 01:51:36AM +0300, bvidinli wrote:
> 
> > ```
> > set $test "";
> > return 444;
> > 
> > ```
> 
> Content-Type: text/plain; charset=UTF-8  
> it would be nice if the config supports simple (extended)  
> [forum.net](http://forum.net)  
> Date: Mon, 19 Jul 2010 20:40:26 +0400
> 
> > Changes with nginx 0.8.46 19 Jul 2010  
> > same in CHANGES and [CHANGES.ru](http://CHANGES.ru)).  
> > To: removed\_email\_address@domain.invalid  
> > ReplyTo: removed\_email\_address@domain.invalid  
> > “uwsgi\_cache\_bypass”, and “s?gi\_cache\_bypass” directives.
> 
> * * *
> 
> Date: Mon, 19 Jul 2010 18:00:55 +0000  
> From: Igor S.
> 
> ```
> *) Feature: the "proxy_cache_bypass", "fastcgi_cache_bypass",
> "uwsgi_cache_bypass", and "s?gi_cache_bypass" directives.
> 
> *) Bugfix: nginx did not free memory in cache keys zones if there was
> an error during working with backend: the memory was freed only
> after inactivity time or on memory low condition.
> 
> ```

Well, after this release, have I still to apply these patches?

[[PATCH 1 of 2] Cache: fix sending of empty](http://nginx.org/pipermail/nginx-devel/2010-January/000101.html)?  
[[PATCH 2 of 2] Cache: fix sending of stale responses](http://nginx.org/pipermail/nginx-devel/2010-January/000102.html)

I mean, it seems it’s a bug introduced in nginx-devel 0.8.31 and it’s 6  
months old, so could you apply these patches on the official tree (or  
tell me why not)?

Thanks for your work,  
d.