you're right. But i wanted to make it short, actually my "client" is a middleware (it intercepts requests from the client and (was filtering them and) forwards them to the server - actually, to a servlet). Data used to be filtered in the servlet, but as this "was slowering down the backend" (sic!) this had been removed, and put in some other object, deep in the code, and the "filtering" is done very late, and only on missing params - not on potentially harmfull chars. That's why i felt like *some* filtering had to be done, maybe not in the right place.
And about the most damaging attack, i totally agree with you.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.