EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, April 10, 2002 9:55 AM
Subject: Re : Re: urlencoded session html-redirection-bug
> >When you encode the url, the first time the jsessionid is attached to the
> >URL,
> >but if your browser have cookies enabled, a
Am Mittwoch, 10. April 2002 10:29 schrieben Sie:
> Are there special reasons why you redirect in the html and not
> with response.sendRedirect ?
yes - a response.sendRedirect won't be recognized by the user! I want the
user to see, that something happened - and after a few seconds he is going to
deUrl())
> -Ursprüngliche Nachricht-
> Von: Michael [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 10. April 2002 09:55
> An: Giorgio Ponza
> Cc: [EMAIL PROTECTED]
> Betreff: Re : Re: urlencoded session html-redirection-bug
>
> is misunderstood by many browsers (NS 4.
>When you encode the url, the first time the jsessionid is attached to the
>URL,
>but if your browser have cookies enabled, a cookie is assigned and the
>jsessionid parameter
>is not shown anymore.
thanks for your comment - but this isn't the problem!
to handle the first-time URLencode af
When you encode the url, the first time the jsessionid is attached to the
URL,
but if your browser have cookies enabled, a cookie is assigned and the
jsessionid parameter
is not shown anymore.
I tried this widh IE5 IE6 an NE4.7 and works. If you disable cookies, you'll
see the URL always
with the
