Last modified: 2009-03-16 13:43:26 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 T19985, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 17985 - Gzipped API results
Gzipped API results
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-03-15 04:38 UTC by Chad H.
Modified: 2009-03-16 13:43 UTC (History)
4 users (show)

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

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

Description Chad H. 2009-03-15 04:38:48 UTC 
It would be helpful if API requests could specify &gzip=1 if they wish to receive gzipped content. Might as well compress if the client supports it (and is asking for it).
Comment 1 Brad Jorsch 2009-03-15 04:55:26 UTC 
As opposed to just using the "Accept-Encoding" header the client should be sending if it wants gzip?
Comment 2 Roan Kattouw 2009-03-16 13:43:26 UTC 
(In reply to comment #1)
> As opposed to just using the "Accept-Encoding" header the client should be
> sending if it wants gzip?
> 

As Brad suggests here, a gzipped response is already sent if the Accept-Encoding header indicates the client can handle it.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links