cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject Re: bug - c2 is caching too aggressively!
Date Sat, 14 Jul 2001 09:15:00 GMT
On Thu, 12 Jul 2001, Donald Ball wrote:

> okay, that's a bad way to state this, but hear me out. c2 is setting the
> HTTP response code 304, SC_NOT_MODIFIED, too aggressively. that is to say,
> it appears that clients who do not have a copy of the resource cached are
> erroneously receiving the 304 response code. a grep of my access_log
> reveals:
>
> 66.45.6.30 - balld [12/Jul/2001:16:48:55 -0400] "GET
> /database/resources/default.css HTTP/1.1" 304 0
> "https://intranet.webslingerZ.com/database/tables/employee_client_table/edit/form?employee_id=8"
> "Mozilla/5.0 (compatible; Konqueror/2.1.2; X11)"
> 66.45.6.30 - balld [12/Jul/2001:16:50:10 -0400] "GET
> /database/resources/default.css HTTP/1.0" 304 0 "-" "Mozilla/4.77
> (Macintosh; U; PPC)"
>
> the first line is from me browsing my site using konqueror. i should be
> getting code 304 in this case - konqueror already has the resource cached.
> the second line is from me browsing the site using a fresh netscape
> instance on a nearby mac with a cleared cache. i should not be getting
> code 304 in this case, afaik. has anyone else experienced this behavior?

The 304 code should only be set if there was a is-modified-since header
presented from the client (browser).

Everything else is nonsens.

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message