Hi bliako,
Thanks for taking the time to answer me. I tried your suggestion splitting the host and API path from the request and I also put the '&format=json' into each request string before calling post, so the "&token=$token" is then put last in the edit request.
I'm afraid the result is a step back. Now I get an API help page in HTML from the first post. This I get at the first log attempt to get the token, which worked fine before. I updated the post sub like this
sub post {
my $query = shift @_;
# my $req = "$api?$query"; # This removed
print "Fetching data with: POST $api $query\n" if $debug;
print Dumper $client;
$client->POST($api, $query);
if ( $client->responseCode() == 200 ) {
print "Got Data OK, decoding ... " if $debug;
print Dumper $client->responseContent() ;
my $data = $JSON->decode( $client->responseContent() );
print Dumper $data;
return $data;
}
else {
print "Failed with code $client->responseCode()\n";
print Dumper $client->responseContent();
}
}
If Is switch this line:
$client->POST($api, $query);
To This
$client->POST("$api?$query");
Then I get back to where I was before. I get the Token, but can't get wiki to accept it for the edit
Cheers, R.
Pereant, qui ante nos nostra dixerunt!
-
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.
|