Okay, this is probably a stupid question. I have been using Mason (1)
forever. I have a number of applications deployed using it. I have never
really worried about XSS attacks or input cleaning, but one of my customers
reminded me today that because of this it could be relatively easy for
people to, for example, inject scripts into a page.
Normally I don't care. These applications are not exposed to the outside
world. But is there a nice, simple way that people are sanitizing their
Mason arguments on the way in to reduce the risk of this sort of thing?
--
Shane McCarron
halindr...@gmail.com
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
