RE: Ajax

Marco,

Not a bad article, although it's a bit alarmist, IMHO. 

It should come as no surprise to anyone that it's a big bad world out
there, and you have to make sure that your code handles the unexpected.
This is, in many ways, no different from problems caused by not
validating input ON THE SERVER SIDE and only doing in in JS on the
client side. You must always validate requests on the server side even
if you do it also on the client side.

Also, and perhaps more importantly, this isn't so much a problem because
of Ajax as it is a problem because Yahoo isn't in complete control of
the HTML sent to the browser. This isn't their fault, it's a nature of
being a e-mail service. I would agree with the article that we're likely
to see increases in attacks like these within services that display
other peoples HTML, services like Blogs, webmail, mashups, public
portals, etc. HOWEVER, that is a fry cry from the types of applications
most of us are deploying. In our applications we are typically in
complete control of the HTML sent to the browser. We're designing it,
we're coding it, and we don't allow just anyone to add their code into
the mix.

In short, this isn't an attack caused by Ajax as much as it's one caused
by a web site that displays other peoples HTML.

-Walden