Ok thanks Roan. I thought so. Perhaps a note should be made on the Wiki documenting the API that the login parms on the query don't work.
I tried messing with the cookies using the php_http extension, and I eventually gave up when this error appeared: HTTP/1.1 500 Internal Server Error Date: Mon, 22 Oct 2007 21:02:05 GMT Server: Apache/2.2.3 (Unix) DAV/2 mod_ssl/2.2.3 OpenSSL/0.9.8d PHP/5.2.0 mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.7 X-Powered-By: PHP/5.2.0 Content-Length: 79 Connection: close Content-Type: text/html register_globals security paranoia: trying to overwrite superglobals, aborting. How the heck did this happen? Can someone write a simple sample PHP app that logs in issues query and echos the results? I thought this would be simple but evidently not. Is there some additional setting/config I need to make on the wiki itself in order to allow a php program to issue a query just like a human using a browser? sgg ---- Roan Kattouw <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] schreef: > > So, am I misusing the login parms somehow on the query url? Are the login > > parms not working? Should I use cookie manipulation instead? > > > Yes, you should use cookies. You'll get a cookie sent to you on > action=login, which you should send back at every next request. In PHP, > Snoopy [1] makes handling cookies easier. Login parameters the way you > tried to use them currently don't work. Maybe they will in the future, > who knows. > > Catrope > > [1] http://snoopy.sourceforge.net/ > > > _______________________________________________ > Mediawiki-api mailing list > [email protected] > http://lists.wikimedia.org/mailman/listinfo/mediawiki-api _______________________________________________ Mediawiki-api mailing list [email protected] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
