Last modified: 2009-05-04 07:07:14 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T20662, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 18662 - edittoken broken on test.wp when specifying json callback


Summary:	edittoken broken on test.wp when specifying json callback

Status:	RESOLVED DUPLICATE of bug 16616

Product:	MediaWiki
Classification:	Unclassified
Component:	API (Other open bugs)
Version:	unspecified
Hardware:	All All

Importance:	Normal major (vote)
Target Milestone:	---
Assigned To:	Roan Kattouw

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-05-03 19:25 UTC by Derk-Jan Hartman
Modified:	2009-05-04 07:07 UTC (History)
CC List:	3 users (show)

See Also:
Web browser:	---
Mobile Platform:	---
Assignee Huggle Beta Tester:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Derk-Jan Hartman 2009-05-03 19:25:38 UTC

works: http://test.wikipedia.org/w/api.php?format=jsonfm&action=query&prop=info&rvprop=content&intoken=edit&titles=User:TheDJ

broken: http://test.wikipedia.org/w/api.php?format=jsonfm&callback=darn_it&action=query&prop=info&rvprop=content&intoken=edit&titles=User:TheDJ

results in:
"warnings": {
		"info": {
			"*": "Unrecognized value for parameter 'intoken': edit"

Comment 1 Roan Kattouw 2009-05-03 20:09:13 UTC

This is expected behavior: when JSON is used with callback, tokens and other user-specific data are not supplied for security reasons. This is documented at http://www.mediawiki.org/wiki/API:Data_formats#JSON_callback_restrictions

Comment 2 Splarka 2009-05-04 01:19:36 UTC

Should this be duped to 16616 or left open as a separate issue catcher?

Comment 3 Roan Kattouw 2009-05-04 07:07:14 UTC

(In reply to comment #2)
> Should this be duped to 16616 or left open as a separate issue catcher?
> 

Good point, I'd forgotten about that one.

*** This bug has been marked as a duplicate of bug 16616 ***

Note You need to log in before you can comment on or make changes to this bug.

Wikimedia Bugzilla is closed!

Search

Personal tools

Navigation

Links