Last modified: 2007-01-18 00:01:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8673 - API returning non-RFC-compliant Content-Type header?
API returning non-RFC-compliant Content-Type header?
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
Other All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-17 14:22 UTC by Bulent Murtezaoglu
Modified: 2007-01-18 00:01 UTC (History)
0 users

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


Attachments

Description Bulent Murtezaoglu 2007-01-17 14:22:48 UTC
The query API returns an extra semicolon in the the content-type header.  Example:

With this URL:

http://tr.wiktionary.org/w/api.php?action=query&prop=info&format=xml&titles=foo

this header:

Content-Type: text/xml; charset=utf-8;

is returned. My cursory reading of section 14.17 of RFC-2616 seems to confirm
that the last semicolon is disallowed.  This broke one client I was using
(Common Lisp, Drakma, already patched).
Comment 1 Brion Vibber 2007-01-18 00:01:43 UTC
Fixed in r19427

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


Navigation
Links