Hi, On Jan 10, 2008 12:45 AM, Tobias Bocanegra <[EMAIL PROTECTED]> wrote: > but in real life. for example when a form input is used to display > search results. so the content of the resulting page changes if the > underlying search space changes. and since not all apps use proper > cache prevention (like no-cache headers etc.) most proxies do not > cache requests with a query (at least afaik).
As far as I recall (I haven't really worked with low level HTTP in years...) there's a best practice of not caching requests with query parameters if the response doesn't have cache control headers. So yeah, if we don't have those headers, then you're probably right that using query parameters breaks caching. But then again, without those headers caching is in any case a bit tricky. Which brings me to my followup point: How does Sling support HTTP caching? Is there something we should do to improve that? As a "RESTful" web framework, Sling should IMHO have built-in support for things like ETags, Expiration headers, 304 responses, etc. BR, Jukka Zitting
