Because sendRedirect is fundamentally completely different to the
RequestDispatcher? It sends a 302 response back to the client and the client
browser re-requests the new URL. RequestDispatcher only performs internal
includes and forwards, so the client never knows it was used.
If you need fo forward to another URL, you can always use a full URL.
Not much point arguing over it though, the spec team did at length and IMHO
the good guys lost ;)
-mike
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Manne Fagerlind
> Sent: Saturday, March 17, 2001 12:55 AM
> To: Orion-Interest
> Subject: RE: offtopic: Path issues
>
>
> I don't see this as a spec bug, I think it's quite deliberate.
> Sometimes you
> need to redirect to sth outside the web app. What'd be the point of having
> sendRedirect() duplicate the functionality of the RequestDispatcher?
>
> /Manne
>
> >NOTE: All JSP commands are relative to the web app root EXCEPT
> >response.sendRedirect() which is relative to the host (stupid
> spec bug!) so
> >you need to put an rcp in front of that.
>
>
>
