|
Michael, I have discovered similar but not identical results. Perhaps the difference is by me using ie 4.0 whereas you are using ie 5.0. What is happening I think is a browser issue, as Netscape seems to work fine as long as I disable document caching in my Preferences for Advanced-> Cache. But if I use IE (or Netscape which caches a document once per session) then I get output displayed from my 2nd servlet, but the url in the address field still shows the first servlet. I think this is a browser bug for IE. What's really happening is this: 1. the SignOut servlet is called and it executes 2. res.sendRedirect(SignIn) is returned to IE 3. IE looks in its cache and finds that the http://host/servlet/reg.SignIn is already there 4. IE does not send out a request to http/WebSphere to serve SignIn, instead it displays the cached copy 5. IE does not update the URL on the address field to say http://host/servlet/reg.SignIn 6. Worse, if I hit refresh while http://host/servlet/reg.SignOut is still there, IE sends a request to the http server only for SignIn! I discovered this by placing System.out.println's for SignIn and SignOut. IE treats the URL as if it is SignIn even though it displays it to us as SignOut. Subject: RE: Servlets From: "Gibbons, Michael" <bmis04@xxxxxxxxxxxxxxxxxxxxxx> Date: Mon, 11 Sep 2000 14:07:59 -0400 Hi Art, Thanks for responding. maybe I could be clearer. I have a servlet called SignOut. It retrieves the session and does an invalidate() and then does res.sendRedirect("/servlet/reg.SignIn") When I use ie 5.0 this is what happens. The output from /servlet/reg.SignIn is displayed but the url in the address field on the browser says /servlet/reg.SignOut even though the page is the result of the SignIn servlet. Also, at the bottom of the browser window there is a status bar that is populated as the servlet is executing. After the results of the SignIn servlet are displayed the status bar continues to be populated until I hit the stop button on the browser. Thanks -----Original Message----- From: owner-java400-l@midrange.com [mailto:owner-java400-l@midrange.com]On Behalf Of francess@us.ibm.com Sent: Monday, September 11, 2000 1:21 PM To: JAVA400-L@midrange.com Subject: Re: Servlets 1. It is not clear to me what the motivation is for wanting to clean up. Are objects being left around, i.e. not being gc'd? Is the browser not displaying what's expected from the redirected-to servlet? Or.....? 2. When I issue a sendRedirect( ), my browser displays the name of the redircted (called) servlet. When you say redirect, do you mean sendRedirect( )? Or are you using something else, like forward( )? Art Smet. "Gibbons, Michael" <bmis04@MARYWOOD1.MARYWOOD.EDU>@midrange.com on 09/08/2000 12:57:15 PM Please respond to JAVA400-L@midrange.com Sent by: owner-java400-l@midrange.com To: "'Java-L'" <java400-L@midrange.com> cc: Subject: Servlets Hello, I have a servlet that calls an RPG program, then retrieves a session object, invalidates() it and does a redirect to another servlet. I wonder if someone could help me with 2 things. 1. After the called servlet completes the status bar in ie 5.0 shows as something is running. I stepped thru it with debug and everything looked good. Is there some kind of cleanup I should be doing the servlet that invalidates? 2. After the called servlet completes the URL being displayed is the name of the servlet that does the redirect. How come the name of the redirected(called) servlet is not in the URL? THANKS in ADVANCE Michael P. Gibbons Manager of Programming & Technical Services MARYWOOD UNIVERSITY 2300 Adams Ave. Scranton, PA 18509 +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.