httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: 2.2 mod_http_proxy and "partial" pages
Date Tue, 06 Dec 2005 16:19:19 GMT

On Dec 6, 2005, at 9:29 AM, Brian Akins wrote:

> I have a serious issue.  It seems that if something happens during  
> a proxy request after mod_http_proxy starts reading from the  
> backend server, no error is reported. (IE, see what happens when  
> ap_pass_brigade  returns non success).  The problem is that this  
> "partial page" may be cached because r->status is a cacheable code,  
> but the response is actually "broken."  The result is that the  
> broken version may be cached and served again and again.
>
> Should we break RFC (maybe) and change r->status to 503 (for  
> example) so cache can check letter.
>
> Note: this is using our internal mod_cache, but looks like the  
> issue would be the same in stock mod_cache.
>

Hmmm. I haven't taken a look yet, but is seems to me that
only complete responses should be cached, not partial, and
as such we need some better mechanism in place for that
"Not Cache-able", "Could be Cache-able" and "To-Be-Cached"
state tree.

Mime
View raw message