Hi Chris,
Thanks for your mail. Actually we were analysing our proxy server logs and
saw that a lot of URLs with jsessionid appended were being cached and this
even includes static files. We saw request for static files like images and
.js files being appended with jsessionid. So i think it happen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard,
On 5/21/2010 12:07 PM, Richard Nduka wrote:
> Thanks again for your reply.
>
> 1. We are not using clustering.
>
> 2. I have checked in the locations mentioned and more and cannot see
> anywhere that cookies is disabled.
>
> 3. However wha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard,
On 5/21/2010 11:45 AM, Richard Nduka wrote:
> Secondly, we have not disabled cookies. In our context, we have cookies set
> to true and cookie is enabled in the browser. For some reason, tomcat still
> re-writes the URL and includes the jsess
On 21/05/2010 17:09, Richard Nduka wrote:
> It is a direct request. Typically, it happens for the first time when a user
> enters the application url in a browser and the login page appears with the
> jsessionid appended in the url.
That is expected. Tomcat doesn't know if the browser supports coo
ote:
> >> From: Richard Nduka [mailto:richies4...@gmail.com]
> >> Subject: Re: jsessionid problem
> >
> >> First of all, we are not fronting tomcat with any other web server or
> >> application server apart from the proxy server (Squid) that seats in
> >
but if i change to
HTTPS (8443) then it is appended.
Thanks.
On Fri, May 21, 2010 at 4:59 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Richard Nduka [mailto:richies4...@gmail.com]
> > Subject: Re: jsessionid problem
>
> > First of all, we a
On 21/05/2010 16:59, Caldarale, Charles R wrote:
>> From: Richard Nduka [mailto:richies4...@gmail.com]
>> Subject: Re: jsessionid problem
>
>> First of all, we are not fronting tomcat with any other web server or
>> application server apart from the proxy server (Squid
> From: Richard Nduka [mailto:richies4...@gmail.com]
> Subject: Re: jsessionid problem
> First of all, we are not fronting tomcat with any other web server or
> application server apart from the proxy server (Squid) that seats in
> front of tomcat.
Are you using clustering?
>
gt; > > From: Richard Nduka [mailto:richies4...@gmail.com]
> > > Subject: jsessionid problem
> > >
> > > I have a few quesations i want to ask about jessionid in tomcat.
> >
> > Thanks for asking twice - two minutes apart. A tad impatient, are we?
> >
&
On 21 May 2010 16:16, Caldarale, Charles R wrote:
> > From: Richard Nduka [mailto:richies4...@gmail.com]
> > Subject: jsessionid problem
> >
> > I have a few quesations i want to ask about jessionid in tomcat.
>
> Thanks for asking twice - two minutes apart. A tad i
> From: Richard Nduka [mailto:richies4...@gmail.com]
> Subject: jsessionid problem
>
> I have a few quesations i want to ask about jessionid in tomcat.
Thanks for asking twice - two minutes apart. A tad impatient, are we?
Also too impatient to mention the Tomcat version, JVM
Richard, there are two ways of maitaining sessions:
1) Using cookies (generally Tomcat's preferred way);
2) Using URL rewriting (generally Tomcat's less preferred way, used where a
client has turned off cookies).
There are no other ways of sending session IDs that are supported by all Web
browsers
Hi,
I have a few quesations i want to ask about jessionid in tomcat.
1. In our web based application which runs on HTTPS, we have observed that
the jsessionid is being appended to the URL. On close examination, we have
observed that this is being added by tomcat to the url (Handled by the
encodeR
Hi,
I have a few quesations i want to ask about jessionid in tomcat.
1. In our web based application which runs on HTTPS, we have observed that
the jsessionid is being appended to the URL. On close examination, we have
observed that this is being added by tomcat to the url (Handled by the
encodeR
14 matches
Mail list logo
