Hi,
That's nice. Would be even nicer if the documentation mentioned that
somewhere (;-)
What it does say is "The API takes its input through parameters in the
query string." Without a hint of using posted "form" data. Not even in
the section on editing, which gives an example with the text in the
query string.
I thought it was pretty odd, but hey, that's what it *says* !
I did find a very serious bug. At present my network connection is
troublesome, often returning 0 data, or truncated data. (This makes it
a good test environment ;-). Take a look at this edit:
http://en.wiktionary.org/w/index.php?title=User%3AInterwicket%2FFL_status&a…
(and preceding and following if you like) The text was truncated and
the page updated anyway. The server isn't noticing that the read data
doesn't add up to the content-length. (And there isn't any particular
terminator, like </api> when reading things.) I think this is a
serious bug?
I've protected against it by encoding the token *after* the text,
title, and edit summary. Presumably no token means it won't edit?
with my best regards,
Robert
On Tue, Jun 1, 2010 at 6:26 PM, Roan Kattouw <roan.kattouw(a)gmail.com> wrote:
2010/6/1 Robert Ullmann <rlullmann(a)gmail.com>om>:
Hi,
Thanks, I've coded it (very easily, somewhat less code than there was,
"urllib2" just makes things more complicated than the httplib I/F ;-)
Does the API put *really* want the text in the encoded URL? It does
work ... but isn't it sometimes kinda long?
You can use POST requests for all API modules.
Roan Kattouw (Catrope)
_______________________________________________
Mediawiki-api mailing list
Mediawiki-api(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api