[eluser]Derek Allard[/eluser]
Quote:Thanks Derek. IF I do turn on global XSS filtering, could I simply do a:
No, you'd still want to use the input class as you did above.
Quote:...and safely assume that all the POST data has already been filtered? Is there no way to manually do this
(the docs say that turning global XSS on causes major overhead)?
Actually, the docs say "a bit of processing overhead", but then later on, "fair amount"

I've never noticed much overhead, and I've always recommended to people to turn it on globally, but each developer needs to make that call. input->post() can accept an array if you want to feed it the whole post stream. In general, I'd encourage you to harvest each item individually if only to keep the code clear and obvious, but again, this is not always the "best" approach. Again, each developer needs to judge for themselves.
Quote:Also, is XSS filtering all that is needed to ensure that the data is 'cleansed'?
For the purposes of XSS, I'd say yes. For other things (SQL injection, mail injection, etc) then no.