jsp:forward problem

rushman · October 14th, 2005, 12:56 PM

Taken from http://www.jspinsider.com/content/js...le_Redirection

Quote:

quote:The forward action ends execution of the current JSP page and removes any existing buffered output. The new page has access to following objects (Application, Request, Session) as the starting file. A new pageContext object is generated for the page. To the browser it will appear you have the originally requested page not the page to which you are transferred.

Quote:

- You can forward to a text file(HTML), a CGI script, a servlet or another JSP page.
- You can only forward to a new page provided no output of the original page has been sent to the browser.

My question is: WHAT IF some output has been sent to the browser?

How can I forward/redirect to another JSP without causing the output stream to close?

I know that I can output a script with window.location.href = 'myPage.jsp'. The problem is that I possibly post lots of parameters to the destination page. I can't use myPage.jsp?param=blabla&param=blibli&param=... because sometimes I will go beyond the browser's maximum URL length .

Any help will be greatly appreciated,

RushMan

Dijkstra's law on Programming and Inertia:

If you don't know what your program is supposed to do, don't try to write it.

angrycat · October 24th, 2005, 10:36 AM

How can I forward/redirect to another JSP without causing the output stream to close?

If you are talking about output to the browser then I dont think you can, when you redirect your code will ignore output, even if it is encountered before the redirect statement.

Server side stuff will sill be completed though, which is something you need to watch out for if you are using re-direct to return someone to the login screen if they do not have access.

In this instance you would add a return; statement directly after the response.sendRedirect(); in order to kill the process.

I discovered this when I noticed database records were still being updated after the redirect statement.

So, in short, you will continue to execute stuff on the server, but not in the browser, I think!!