You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Scott Carpenter <sc...@gmail.com> on 2013/11/20 00:59:49 UTC
Wicket Sessions and Akamai Caching
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
Re: Wicket Sessions and Akamai Caching
Posted by Scott Carpenter <sc...@gmail.com>.
Thanks, guys. I'll take a look!
On Wed, Nov 20, 2013 at 2:13 AM, Martin Funk <ma...@gmail.com> 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 <jeremy@wickettraining.com
> >:
>
> > 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 <scarpentus@gmail.com
> >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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Wicket Sessions and Akamai Caching
Posted by Martin Funk <ma...@gmail.com>.
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 <je...@wickettraining.com>:
> 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 <sc...@gmail.com>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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket Sessions and Akamai Caching
Posted by Jeremy Thomerson <je...@wickettraining.com>.
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 <sc...@gmail.com>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