I voted --, and wanted to explain why.
Given all of the fuss over handrolled CGI parsers
lately, I am amazed that you would post your own.
chromatic right now has an excellent explanation
of why you really didn't want to do that. (And yes, you did make most of the common mistakes.)
Additionally you don't seem to be aware of a variety of
race conditions, security holes, etc. For a random instance take
a look at this
and figure out how many of the attacks you could be taken
down with. Oh, better than that, how many of the attacks
are designed to get around checks that you don't even do?
Hopefully you will take this as constructive criticism and
learn how to avoid these problems in the future. But in
the meantime -- for bad advice that will put at risk anyone
who follows it.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||