2010/6/1 Robert Ullmann <rlullmann(a)gmail.com>om>: For requests made in rapid succession, definitely. For requests that are further apart, maybe. No idea. You could find out by trying :) Yes, they all return the same IP address. Roan Kattouw (Catrope)

2010/6/1 Robert Ullmann <rlullmann(a)gmail.com>om>: You can use POST requests for all API modules. Roan Kattouw (Catrope)

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 &lt;roan.kattouw(a)gmail.com&gt; wrote:

On Wed, Jun 02, 2010 at 03:29:25PM +0300, Robert Ullmann wrote: I believe the standard HTML edit form places the hidden fields at the end for the same reason. You could also place the "action" at the end, so if truncated the API request will fail for having no action specified. With the API, you could also use the "md5" option to action=edit (this can also help catch certain charset encoding issues). Or, theoretically, using multipart/form-data instead of application/x-www-form-urlencoded for your POST would cause your post to be malformed if truncated, but I wouldn't be extremely surprised if PHP "fixes" that.

On Wed, Jun 2, 2010 at 4:27 PM, Brad Jorsch &lt;b-jorsch(a)northwestern.edu&gt; wrote: It does.