Todd McGrath wrote:
Perplexed by a problem I'm having:
I have a custom login solution that writes a string to
a user's HttpSession Object:
session.setAttribute("login", new
java.util.Date().toString());
In the app, I have a controller servlet that checks
for this session attribute
As far as I remember, there is another difference between sendRedirect() and
RequestDispatcher.forward(). I once tested both alternatives, and I found
that with forward(), the client never gets to know that he hase been sent to
another page, i.e. the URL does not show, the reload button reloads
Title: RE: HTTPSession timeouts in SSL environment
Hi Chris,
you are right.
using a RequestDispatcher only redirects the request on the server side, wihtout informing the client.
a sendRedirect() will ask the client to go to another page, thus changing header info and the whole thing
Christian Sell wrote:
As far as I remember, there is another difference between sendRedirect() and
RequestDispatcher.forward(). I once tested both alternatives, and I found
that with forward(), the client never gets to know that he hase been sent to
another page, i.e. the URL does not show,
september 2000 11:17
To: Orion-Interest
Subject: Re: HTTPSession timeouts in SSL
environment
As far as I remember, there is another difference
between
sendRedirect() and
RequestDispatcher.forward(). I once tested both
alternatives,
and I found
that with forward(), the cl
