Thanks, guys. I'll take a look!
On Wed, Nov 20, 2013 at 2:13 AM, Martin Funk <[email protected]> wrote: > Hi, > > the explanation in wicket guide might give further insight: > http://wicket.apache.org/guide/guide/chapter11.html#chapter11_9 > > mf > > > Am 20.11.2013 um 06:04 schrieb Jeremy Thomerson <[email protected] > >: > > > Pages that are session-specific should not be cached in a way that allows > > the cached response to be given to multiple users. Stateful forms are > > session-specific. > > > > > > On Tue, Nov 19, 2013 at 6:59 PM, Scott Carpenter <[email protected] > >wrote: > > > >> I have a client Wicket web site and they are using Akamai for caching. > They > >> wanted to cache more aggressively but it seems there's an issue with > >> expired sessions. When a user hits a cached version of a page with a > form > >> and tries to submit it, a 500 error is raised. (I'm relaying this from > at > >> least two sources removed, so by now I might have the details thoroughly > >> obfuscated.) > >> > >> I was hoping from this list I could get some pointers on best taking > >> advantage of Akamai, and how I might work around issues like this. > Please > >> let me know if and what further information would be useful in > answering. > >> > >> Thank you! > >> > >> Scott > >> > > > > > > > > -- > > Jeremy Thomerson > > http://wickettraining.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
