| From: Riccardo [mailto:[EMAIL PROTECTED]
| Sent: Thursday, 26 July, 2007 16:10
|
| Maybe I should define some headers management rule within the webapp..
| I haven't measured the time exactly, but i find quite interesting that
| this caching effect lasts around 2 minutes, than disappears. I wond
On 7/26/07, Rainer Jung <[EMAIL PROTECTED]> wrote:
Hi Riccardo,
if I understood your description correct, your Tomcat server itself
communicates with another backend to get the report. In this sentence it
is important, that Tomcat and not the browser talks to this backend.
You are right, when
Hi Riccardo,
if I understood your description correct, your Tomcat server itself
communicates with another backend to get the report. In this sentence it
is important, that Tomcat and not the browser talks to this backend.
I expect that you do this via HTTP as well. Note that there is no HTTP
On 7/26/07, Len Popp <[EMAIL PROTECTED]> wrote:
I don't think Tomcat caches cookie values. I could be wrong about
this, but it seems to me that Tomcat just gets the cookie value from
the request sent by the browser.
I did a test to check this.
After running a report I deleted the cookie from Fi
I don't think Tomcat caches cookie values. I could be wrong about
this, but it seems to me that Tomcat just gets the cookie value from
the request sent by the browser.
Maybe you should log the value of the cookie in various different
spots so you can follow the cookie's progress and see where it g
