|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
legitimate use of recursive document loading into IE4
- To: NTBUGTRAQ
LISTSERV.NTBUGTRAQ.COM - Subject: legitimate use of recursive document loading into IE4
- From: ezines <ezines
SLEEPI.DEMON.CO.UK> - Date: Wed, 18 Mar 1998 22:20:26 +0000
- In-Reply-To: <890110889.0518709.0
vms-backup.dc.lsoft.com> - Reply-To: ezines <ezines
SLEEPI.DEMON.CO.UK> - Sender: Windows NT BugTraq Mailing List <NTBUGTRAQ
LISTSERV.NTBUGTRAQ.COM>
[in reference to recursive bug in IE4] >Seems to me that these are just obvious coding bugs that do not detect a >recursive case without an exit. I wonder if it is possible to write a >useful web page using this technique, I think so, if you were using javascript. 2 or more Documents could be combined into one, and the different parts could be displayed using 'document.write()'s to form the different parts of the page depending on what the page's parent URL, or frame name, etc. was. > calling one's self, or if all such >cases are bogus. If this is a useful programming technique, then it >would be very difficult to detect a non-function exit clause and most >probably IE would have to limit the depth of recursion to solve this >problem. Maybe if the recursion case was looked for only after the document had been completely loaded (i.e. after the javascript had been executed). -- Ben Isaacs
- Prev by Date: MS Word connected to DB/2: Cleartext host uid & pwd in document!
- Next by Date: NTFS Alternate Data Streams
- Prev by thread: MS Word connected to DB/2: Cleartext host uid & pwd in document!
- Next by thread: Re: legitimate use of recursive document loading into IE4
- Index(es):