Yet another example of why not to roll your own.
First of all you assumed that the query string only has
one name/value pair. What if it has more? Use a hash?
Well what if there are multiple name/value pairs? What if
someone for testing turns a post back into a get to
collect a URL and then wonders why their code broke?
Plus did you consider the poor schmuck who will use your
code with form data that has been modified in escaping? At
least you warned people that you got the first wrong. But
you should also be pointing people to URI::Escape so they
can decode the data.
No, it is far better to do as CGI intentionally does and
leave get/post transparent within the CGI so that the
developer can easily switch, and just use hidden form
elements as they were intended rather than trying to mix
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible editor
Want more info? How to link
or How to display code and escape characters
are good places to start.