Last modified: 2014-02-25 02:13:46 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 T63507, 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 61507 - Let MWHttpRequest set Accept-Encoding: gzip
Let MWHttpRequest set Accept-Encoding: gzip
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.23.0
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 56605
  Show dependency tree / graph
 
Reported: 2014-02-18 19:05 UTC by James Forrester
Modified: 2014-02-25 02:13 UTC (History)
1 user (show)

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

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

Description James Forrester 2014-02-18 19:05:45 UTC 
$req->setHeader( 'Accept-Encoding', 'gzip' ); would be useful, but there isn't support for it.
Comment 1 Alex Monk 2014-02-25 02:13:46 UTC 
Should this even be necessary?

I think that the cURL backend ignores this and sets it's own accept-encoding, and then returns the decoded response. The PHP backend does send this accept-encoding header *if asked by the caller* (e.g. with the code you mentioned), but does not decode the response.

I think we should modify the PHP backend to behave the same as the cURL one, and don't bother relying on the caller to set Accept-Encoding.
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