Hi, Has anyone else observed the following behavior, and if so, could they explain it to me? Better still, could they explain how to avoid it? Or am I going mad?
To summarize, this is what I see happening (details below): 1. If I go straight to the frameset page, invoke an action on one of its child pages, then reload the frameset, the child request I see invoked during the reload is that for the last request invoked on the child page, rather than that previously invoked for that child page by the frameset's frame's src parameter. This is the same for both Internet Explorer 6.0 (IE) and Netscape 6.2 (NS). 2. If, on the other hand, I go to the frameset page by submitting an action that struts looks up in struts-config.xml, then forwards to that same frameset page, the exact sequence of requests submitted by the browser resulting from the same user actions seems to vary. Specifically, the child page request submitted as the result of the reload/refresh seems to be that originating from the frameset's frame's src parameter for IE, but that submitted for NS is still that for the last request invoked on the child page itself. Any info relating to similar experiences appreciated! Thanks, Vaughan. --------------------------------------------------- Details Below --------------------------------------------------- I have a frameset page called framesWithError.jsp. This contains the following single frame: <frameset rows="100%"> <frame name="test" src="testPage.html?origin=frameset"> </frameset> testPage.html is the following: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML> <HEAD> <TITLE>Test Page</TITLE> <META HTTP-EQUIV="Expires" CONTENT="0"> <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"> </HEAD> <BODY> <FORM> <INPUT TYPE="hidden" NAME="origin" VALUE="page"> <BUTTON TYPE="submit" NAME="submit" VALUE="submit"> SUBMIT </BUTTON> </FORM> </BODY> </HTML> Making these part of a struts web app, and hitting the submit button on testPage results in the following request being submitted: http://homer:8080/frames/testPage.html?origin=page&submit=submit If I go straight to the URL of the frameset page in either Internet Explorer 6.0 (IE) or Netscape 6.2 (NS), then hit the submit button on testPage.html (in the frame), and lastly hit the browser's Reload or Refresh button, I see the same sequence of requests being submitted by the browser: 1.http://homer:8080/Frames/framesWithError.jsp 2.http://homer:8080/Frames/testPage.html?origin=frameset 3.http://homer:8080/Frames/testPage.html?origin=page&submit=SUBMIT <- SAME 4.http://homer:8080/Frames/framesWithError.jsp <- start of reload 5.http://homer:8080/Frames/testPage.html?origin=page&submit=SUBMIT <- SAME (request from page) Using Netscape 6.2 (NS), if instead I go to the URL http://homer:8080/frames/updateBean.do?action=showErrorFrame, repeating the same sequence of actions as described above, I see more or less the same thing. I believe the significant thing that struts does with this initial URL is look up the corresponding struts-config.xml entry and forward the request to the same frameset page framesWithError.jsp: <!-- Update Bean --> <action path="/updateBean" type="com.tumbleweed.tsg.ca.web.action.UpdateBeanAction" name="updateBeanForm" input="/updateBean.jsp"> <forward name="showErrorFrame" path="/framesWithError.jsp"/> </action> The sequence of requests submitted by the browser in this case is: 1.http://homer:8080/frames/updateBean.do?action=showErrorFrame 2.http://homer:8080/frames/testPage.html?origin=frameset 3.http://homer:8080/frames/testPage.html?origin=page&submit=submit <- SAME 4.http://homer:8080/frames/updateBean.do?action=showErrorFrame <- start of reload 5.http://homer:8080/frames/testPage.html?origin=page&submit=submit <- SAME (request from page) Now I perform EXACTLY the same sequence of actions with Internet Explorer 6.0 (IE), starting with the URL http://homer:8080/frames/updateBean.do?action=showErrorFrame, I see a different sequence of requests submitted from the browser: 1.http://homer:8080/frames/updateBean.do?action=showErrorFrame 2.http://homer:8080/frames/testPage.html?origin=frameset <- SAME 3.http://homer:8080/frames/testPage.html?origin=page&submit=SUBMIT 4.http://homer:8080/frames/updateBean.do?action=showErrorFrame <- start of reload 5.http://homer:8080/frames/testPage.html?origin=frameset <- SAME (request from frameset) ___________________________________________________ Vaughan Jackson Development Tumbleweed Communications [EMAIL PROTECTED] / +1 (650) 216 2532 ___________________________________________________ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>