the path is the same, the filename differs. yes you're right, no-store and no-cache didn't change anything. instead of Image i'm using NonCacheableImage as the subclass and now it works fine with any browser.
but thanks for the hint greetz leigh ________________________________ Von: Pointbreak <[email protected]> An: Wicket Users Mailing List <[email protected]> Gesendet: Dienstag, den 10. März 2009, 16:15:15 Uhr Betreff: Re: resource cacheable firefox/opera You use the same url for different images? Firefox uses a memory cache in addition to a disk cache. Check what headers are send with your image. No-store and no-cache headers will NOT prevent firefox3 from using its memory cache (at least not with pages). Your best bet is to use different urls. On Tue, 10 Mar 2009 14:56 +0000, "Arthur Leigh Allen" <[email protected]> wrote: > Hi folks, > > I've implemented a RemoteImage class which extends the Image class. > The method setCacheable works with Internet Explorer but neither with > Firefox nor with Opera.. > If I load an image the first time, the correct image is shown. > When I try to load a different image (path is applied correctly), the old > image is shown. > > What I'm doing wrong? > I'm using wicket 1.3.5. > > === > public > classRemoteImage extendsImage { > publicRemoteImage(String id, finalString path) { > super(id); > > Resource resource = newWebResource() { > publicIResourceStream getResourceStream() { > IResourceStream stream = newFileResourceStream(newFile(path)); > returnstream; > } > }; > > resource.setCacheable(false); > setImageResource(resource); > } > } > > === > > Would appreciate any help. > > Thanks in advance > Leigh > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
