|
Posted by Andy Dingley on October 12, 2007, 11:12 am
Please log in for more thread options
On 12 Oct, 14:32, marco.d...@gmail.com wrote:
> we are considering the use of an IFRAME box. What problems should we expect
> to encounter?
* <iframe> may be targeted by various cross-site scripting (XSS)
attacks
* IE may attempt to guard against these attacks by being awkward about
the <iframe> content it will display.
* IE may require your users to change their security settings to see
this <iframe> content.
* Windows Updates may deliver unpredictable changes to IE and the way
it guards against these attacks, such that a previously deployed web
site or web app suddenly stops working. The suddenness of this is
about the worst part.
* There may be copyright issues about serving other people's content
in an <iframe>
* <iframe>s have some of the disadvantages of frames in general,
particularly for the bookmarking limitations.
* If you serve "live" client-side content from someone else's server,
then you're reliant on their server being reliable.
* If you serve content from someone else's server, they may object to
your use of bandwidth and then limit your access.
* In general, don't assemble content on the client-side. Load it to
the server, cache it, assemble it server-side (SSI or scripting) and
serve one single and simple page.
| 
