Not having a far future expires header while developing makes some
things, especially debugging JavaScript, much easier.
On Mon, Mar 1, 2010 at 2:39 AM, Stephan Windmüller
<stephan.windmuel...@cs.tu-dortmund.de> wrote:
> On 26.02.2010 16:26, Ulrich Stärk wrote:
>
>> if (productionMode)
>> response.setDateHeader("Expires", lastModified +
>> InternalConstants.TEN_YEARS);
>>
>> Are you in production mode?
>
> You are right, that fixed it.
>
> Thank you very much!
> Stephan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
