I've encountered the problem again that I described in some posts from
last month.
I had figured that the problem was resolved when I explicitly included
the jsessionid as a param with the URL. The situation was this: I have a
page that refreshes every few seconds with updates to a list of
Alright, now I'm really baffled. Below, I've copied my original post
about the discrepancy that's been puzzling me. Please consult that for a
description of the web app and the TEST environment.
My web app had been working just fine in the TEST environment, PROVIDED
I included the initial session
Mark,
My web app had been working just fine in the TEST environment, PROVIDED
I included the initial session ID as a param to the URL used on the
cancel/switch-to-batch form. But starting just this morning, it was
failing again, DESPITE my using the session ID as a param to the URL on
the
Hi chris,
I think your suggestion about multiple windows was a good guess. It
would account for all the behavior, except that I'm quite sure I wasn't
using a different window. I mean, the web app responds with a page that
refreshes itself after a set, short amount of time, presenting a
progress
Mark,
I think your suggestion about multiple windows was a good guess.
[snip]
No, no HTTPS-to-HTTP stuff; all requests are going to a port dedicated
to Tomcat (8088).
And the Firefox cookies options form is set so that cookies are kept
until they expire which I believe is the default
Mark,
Take a look at the LiveHttpHeaders plug-in for Firefox. It may help you
debug this on the client side.
Temporarily enabling the RequestDumperValve on the server side will
enable you to see if cookies are reaching the server.
HTH,
Jon
Aronszajn, Mark wrote:
Thanks for the
From: Aronszajn, Mark [mailto:[EMAIL PROTECTED]
Subject: a discrepancy in webapp behavior in two environments
This is fine, but what I don't understand is why specifying a
jsessionid param value is necessary in the TEST environment and
not necessary in the DEVELOPMENT environment. I also
Thanks,
Could you explain how the configuration of a firewall would have such
effect on whether the original HttpSession object gets retained? I'm not
being skeptical here at all, and sorry if it's a dumb question: I'm just
ignorant of the sorts of considerations that might be relevant and would
From: Aronszajn, Mark [mailto:[EMAIL PROTECTED]
Subject: RE: a discrepancy in webapp behavior in two environments
Could you explain how the configuration of a firewall would have such
effect on whether the original HttpSession object gets retained?
If you're not appending jsessionid ro the
Thanks for the information. I had checked Firefox in each environment (I think
I mentioned this) to be sure that cookies were allowed, but I didn't realize
that a firewall might block cookies.
I really appreciate the help.
Mark
-Original Message-
From: Caldarale, Charles R
10 matches
Mail list logo
