On Thu, Oct 23, 2008 at 2:12 AM, Tore Eriksson
<[EMAIL PROTECTED]> wrote:
>> Tore Eriksson wrote:
>> > Hello everybody,
>> >
>> > As I found a solution to my problem, I thought I would share it in case
>> > someone else comes up against the same issue. The reason for the client
>> > not acting on t
> Tore Eriksson wrote:
> > Hello everybody,
> >
> > As I found a solution to my problem, I thought I would share it in case
> > someone else comes up against the same issue. The reason for the client
> > not acting on the redirect is that sendRedirect does not send any
> > Content-length header, a
Tore Eriksson wrote:
> Hello everybody,
>
> As I found a solution to my problem, I thought I would share it in case
> someone else comes up against the same issue. The reason for the client
> not acting on the redirect is that sendRedirect does not send any
> Content-length header, and the client
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tore,
Tore Eriksson wrote:
> The reason for the client
> not acting on the redirect is that sendRedirect does not send any
> Content-length header, and the client will then wait for an eventual
> Content body until the servlet finishes. This could be
Hello everybody,
As I found a solution to my problem, I thought I would share it in case
someone else comes up against the same issue. The reason for the client
not acting on the redirect is that sendRedirect does not send any
Content-length header, and the client will then wait for an eventual
Co
Hello again,
Thanks for the response, but it seems like my phrasing was a bit unclear.
The problem is not the second redirect - in fact there will be no
multiple redirects. The second redirect is only there for the case when
less than 25 hits are found and the first redirect is not called. The if
Maybe a solution could be to use AJAX client side to make the multiple
requests.
The client make the first request, when the server answers the client make
the following request and so on.
So the desired effect should be reached.
Regards
Luca
-
Tore
Your code below is written as though the 'out' was like writing data to
a console. The processing in a servlet is part of a request/response
cycle, where the 'request' tells it what to do and the response is the
reply.
Because of the nature of the request/response cycle you only get on
