comment on

Rather simple reason that CGI.pm isn't doing what you'd like it to:

Your incomming XML is likely unquoted.

Let's assume you're trying to pass in this small XML string (I'll do the example in GET, since CGI.pm handles GET and POST transparantly): "<xmltag>Tulips & Flowers<xmltag>".

in a get request this is going to look like:
script.pl?xml=<xmltag>Tulips & Flowers<xmltag>

Ick! Since you haven't followed the specs for escapeing URLs, it's going to get nasty.

Get the people who are sending your request to properly escape the data:

my $newval = CGI::escape(qq("<xmltag>tulips &amp; Flowers:</xmltag>));
[download]

$newval will now look more like: %3Cxmltag%3Etulips%20%26amp%3B%20Flowers%3A%3C%2Fxmltag%3E

Which is how it should look if you're following the standards for URL quoting.

Now, using CGI.pm:

use CGI.pm

my $q = new CGI;

my $xml = CGI::unescape($q->param('xml'));
[download]

Voila!

In reply to Re: CGI.pm problems by Illiad
in thread CGI.pm problems by c-era

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> <u> <ul>
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 janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks