This is very specific to your case, not a general Wicket case. Setting the cache timeout the same as the session timeout seems like a better way to do this.
Martijn
On 1/27/06, Gili <[EMAIL PROTECTED]> wrote:
Hi,
Can we modify the default behavior of the Image component (the relevant
code is inside its onComponentTag()) such that it always appends
"jsessionid" onto its SRC url?
As previously discussed, currently we general identical URLs across
sessions, the browser caches these images, but underlying image might
change from session to session and the browser will display an incorrect
(cached) image.
I think appending the jsessionid to the URL is a very easy and generic
fix for this and I'd like to see it go into core. What do you think?
Thanks,
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Living a wicket life...
Martijn Dashorst - http://www.jroller.com/page/dashorst
Wicket 1.1.1 is out: http://wicket.sourceforge.net/wicket-1.1
