I think we could make this by default in wicket. Until then, you can make a filter, that checks if the request contains wicket-ajax header, and when it does, add the cache-control no-store header.
-Matej On 6/27/07, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]> wrote: > Hi > > We are having some troubles using wicket and Oracle web server. It's > some of our ajax calls that just hangs. By hanging I mean that if we > click an ajax triggering control, if fires the event and just never gets > a response. Debuggin a little deeper it seems that wicket does not even > gets the request. We are suspecting that it has something todo with the > oracle web cache. > > So the ajax call sends some attributs with it to avoid being cached, > however it's missing the cache-control="no-store". We are not sure > that this are causing our troubles. How can I make the ajax call include > the attribute? > > Has anybody some ideas about this? > > > I've tested the application on jetty, and here it works without any > problems. > > > any help highly appreciated. > > > regards Nino > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user