Re: 1.5.1 vs 1.4.7 RequestDispatcher
response.sendRedirect() is sent to the browser after loading is complete, forward continues execution on the new page directly. I suppose this is expected behaviour. Why would a code stop executing just because of a method call? response.sendRedirect(...) whould be something like Browser.setNextPage(...); and that method call would not cause this function not to complete. I'm sorry for sounding like a monday morning programmer who haven't even got his first cup of coffee yet. Even though it is thursday... P.S. Moving the return statement is the only way to stop execution. D.S. Johan - Original Message - From: Greg Stickley [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Thursday, May 31, 2001 12:19 AM Subject: Re: 1.5.1 vs 1.4.7 RequestDispatcher I had a problem with request.sendRedirect where orion would continue processing the jsp or servlet below the sendRedirect. It's like it ignored the redirect intirely. I had to put a return; statement imediately following the sendRedirect statement. Maybe this is related. --- Kit Cragin [EMAIL PROTECTED] wrote: Is there something that changed between 1.5.1 and 1.4.7 that broke my forward() requests? I have a servlet mapped to /start and protected by a role, user, in web.xml. The servlet obtains a RequestDispatcher to /roles/user/index.jsp. This JSP has an iframe that loads /roles/user/content.html. Under 1.4.7 when I do http://localhost/webapp/start I got a login prompt as expected and everything shows up correctly. Under 1.5.1, the same URL causes 3 login prompts. On the last one, I get a 401 unauthorized on content.html. Anyone know why this could be occuring? Thanks, Kit Cragin VP of Product Development Mongoose Technology, Inc. www.mongoosetech.com __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
1.5.1 vs 1.4.7 RequestDispatcher
Is there something that changed between 1.5.1 and 1.4.7 that broke my forward() requests? I have a servlet mapped to /start and protected by a role, user, in web.xml. The servlet obtains a RequestDispatcher to /roles/user/index.jsp. This JSP has an iframe that loads /roles/user/content.html. Under 1.4.7 when I do http://localhost/webapp/start I got a login prompt as expected and everything shows up correctly. Under 1.5.1, the same URL causes 3 login prompts. On the last one, I get a 401 unauthorized on content.html. Anyone know why this could be occuring? Thanks, Kit Cragin VP of Product Development Mongoose Technology, Inc. www.mongoosetech.com
Re: 1.5.1 vs 1.4.7 RequestDispatcher
I had a problem with request.sendRedirect where orion would continue processing the jsp or servlet below the sendRedirect. It's like it ignored the redirect intirely. I had to put a return; statement imediately following the sendRedirect statement. Maybe this is related. --- Kit Cragin [EMAIL PROTECTED] wrote: Is there something that changed between 1.5.1 and 1.4.7 that broke my forward() requests? I have a servlet mapped to /start and protected by a role, user, in web.xml. The servlet obtains a RequestDispatcher to /roles/user/index.jsp. This JSP has an iframe that loads /roles/user/content.html. Under 1.4.7 when I do http://localhost/webapp/start I got a login prompt as expected and everything shows up correctly. Under 1.5.1, the same URL causes 3 login prompts. On the last one, I get a 401 unauthorized on content.html. Anyone know why this could be occuring? Thanks, Kit Cragin VP of Product Development Mongoose Technology, Inc. www.mongoosetech.com __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
RE: 1.5.1 vs 1.4.7 RequestDispatcher
I am definitely experiencing something very similar. I haven't tried it with a version of Orion prior to 1.4.8, but I find that using RequestDispatcher.forward() produces erratic results, usually without sending any output. I find that calling include() works as advertised. The exact same code with forward() works fine with Tomcat4. I logged bug #482 about this. It would probably help if you added more information: http://bugzilla.orionserver.com/bugzilla/show_bug.cgi?id=482 I will try 1.4.7 and see if it works. BTW, I'm using an HttpServletResponseWrapper subclass; I haven't tried without a wrapper to see if it works. Jeff -Original Message- From: Kit Cragin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 30, 2001 11:49 AM To: Orion-Interest Subject: 1.5.1 vs 1.4.7 RequestDispatcher Is there something that changed between 1.5.1 and 1.4.7 that broke my forward() requests? I have a servlet mapped to /start and protected by a role, user, in web.xml. The servlet obtains a RequestDispatcher to /roles/user/index.jsp. This JSP has an iframe that loads /roles/user/content.html. Under 1.4.7 when I do http://localhost/webapp/start I got a login prompt as expected and everything shows up correctly. Under 1.5.1, the same URL causes 3 login prompts. On the last one, I get a 401 unauthorized on content.html. Anyone know why this could be occuring? Thanks, Kit Cragin VP of Product Development Mongoose Technology, Inc. www.mongoosetech.com
