Thanks for the answer,

I tried using a client in bash (modified from [1] to exit after getting the edit token), and it seems to work : I do get an edit token after logging in.

I then modified the bash example to have more information on what is sent/received (--trace, ...), and I noticed than curl is sending back the cookies in a single header (instead of one header for each cookie as Apache HttpClient is doing by default).

So, I changed my own code to force grouping cookies in a single header (by setting http.protocol.single-cookie-header to TRUE), and it seems to work now.

Thanks a lot !

Nico

[1] https://www.mediawiki.org/wiki/API:Client_code/Bash

On Mon, Jul 14, 2014 at 3:59 PM, Brad Jorsch (Anomie) <bjorsch@wikimedia.org> wrote:

The headers you provided appear correct. Are you able to log into Waze wiki using another framework? If so, it might be useful to compare the headers between the successful client and yours to identify what the difference might be. Perhaps Waze's infrastructure is somehow screwing up on the obsolete RFC 2965 cookie headers, for example.

The different style of cookie name is nothing to worry about, it's just a matter of different settings for $wgSessionName.

_______________________________________________
Mediawiki-api mailing list
Mediawiki-api@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api