thank you, Rob!
(thank you, Michael)
... it sounds consistent. once more again to
secure, i understand it correct:
a forward in opposition to a redirect is some
server-internal operation, whose result is send
back to the browser. as the browser itself don't realize it,
the anchor at the url has not the desired effect.
ok. that a redirection with a anchor-url operates, is
clear.
is there a trick to anyhow get some related behavior
with forward to work?
or is this not necessary, because i can access the
original session object at the second
page in the case of a redirect as well?
(i think this was my error in reasoning, that i have to
use a forward when using sessions)
thank you again,
bAs T.
Rob Tanner schrieb:
> When you do a RequestDispatcher.forward(), that's an internal
> operation, and not a redirect send back to the browser. In the latter
> case, the browser initiates a new GET request to the new URL. In the
> former case, the page at the RequestDispatcher.forward() address is
> simply sent to the browser without the browser being any the wiser. In
> that sense, it's the same kind of thing as an internal redirect in
> Apache.
>
> Whether the address "example.jsp#position1" is a good URL or a bad URL
> or whether it's a tomcat bug or a serverlet 2.2 spec bug that an
> exception wasn't thrown is something I don't know. But going back to
> my first point, since the browser is unaware of the forward anyway,
> anchors won't work. Do a redirect to the browser instead.
>
> -- Rob
>
> --On Monday, March 05, 2001 10:09:24 AM -0800 Filip Hanik
> <[EMAIL PROTECTED]> wrote:
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
