I am trying to transparently redirect requests for one JSP page to another, and then forward back to the original when some condition is met. The intended sequence of events is something like:
browser GET protected.jsp filter protected.jsp to login.jsp login.jsp sent to browser browser POST protected.jsp (with login.jsp form data) filter protected.jsp to login.jsp login.jsp tags perform validation, find errors login.jsp sent to browser browser POST protected.jsp (with corrected login.jsp form data) filter protected.jsp to login.jsp login.jsp tags perform validation, login successful login.jsp forwards back to protected.jsp My problem is that the final forward (from login.jsp back to protected.jsp) gets routed back to login.jsp without the filter doing anything. It seems like something is being cached in the Catalina/Jasper code, but I have not managed to find it. Is there a way I can work around this, and still have the browser believe it is requesting protected.jsp for the entire login? I have a number of working alternatives, but all of them result in the browser requesting the login.jsp URL directly, which I would prefer to avoid (I have users who get confused if the wrong URL appears when they open a bookmark). Thanks, Chris -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
