Thanks for everyone's replies! Thank you all so much! I'd definitely look into selectors and virtual URI mapping to solve our issues.

Thanks again,
Po Ki

On Sep 30, 2008, at 10:26 AM, Giancarlo F. Berner wrote:

Hi Po Ki

I am not quite sure if you want to cache URL with parameters in the first place. Typically the "?" is used to pass caching in Web servers. Simplified: requests with a "GET" method and parameters are NOT answered from a cache. I personally would go with this de facto standard and use "?" for not getting a cached response.

If you want to cache parameters, I use the "selectors". A selector is a "dot separated value between URI label and extension". For example, your request could look like http://example.com/index.test.html, where "test" is the selector. The response of this URL will be cached. You can of course use multiple selectors (e.g. /page.test1.test2.html).

Use "Resource.getSelector()" to get a String of all selectors.

/giancarlo


On Sep 30, 2008, at 6:51 AM, Po Ki Chui wrote:

Hi all,

I wonder if Magnolia EE 3.5.8 is capable to cache URL with parameters (i.e. http://example.com/index.html?param=test). Your answer is appreciated.


Thanks,
Po Ki

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------



----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to