One more thing,
You might also look for the string 786297600 somewhere in configurations or
your webapp, because that is the seconds since the epoch that would result
in December 1st, 1994, 16:00 GMT. Is it always exactly the same value? - Yes
it's always the same value
On Mon, Jun 1, 2015 at
Thanks Rainer for the tips. Here is the follow up.
1. Added quot;%{Expires}oquot; to logging valve pattern in the
server.xml, sets the correct headers expires on the webserver side, doesn't
set the 1994 year one. But still when I look at the browser, the double
header appear the one from 1994
Hi Kurtis,
It is a possibility I guess, but my timezone is EST.
Thanks,
Emir
On Mon, Jun 1, 2015 at 3:14 PM, Kurtis Rader kra...@skepticism.us wrote:
On Mon, Jun 1, 2015 at 11:18 AM, Emir Ibrahimbegovic
emir.ibrahimbego...@gmail.com wrote:
You might also look for the string 786297600
On Mon, Jun 1, 2015 at 11:18 AM, Emir Ibrahimbegovic
emir.ibrahimbego...@gmail.com wrote:
You might also look for the string 786297600 somewhere in configurations
or your webapp, because that is the seconds since the epoch that would
result in December 1st, 1994, 16:00 GMT. Is it always
Am 30.05.2015 um 02:26 schrieb Emir Ibrahimbegovic:
I've got an app that runs on a tomcat web server, and I use mod-jk on my
apache web server side.
I think I've managed to configure everything to work seamlessly, I ran
into issues when I wanted to cache static assets on webserver, for some
I've got an app that runs on a tomcat web server, and I use mod-jk on my
apache web server side.
I think I've managed to configure everything to work seamlessly, I ran into
issues when I wanted to cache static assets on webserver, for some reason
my response headers expires is set to **1994**,
