Closed
Bug 1325278
Opened 7 years ago
Closed 7 years ago
Optionally provide access to responseBody for webextensions
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1255894
People
(Reporter: mzelina, Unassigned)
Details
Attachments
(2 files)
6.91 KB,
patch
|
Details | Diff | Splinter Review | |
6.58 KB,
application/zip
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/20100101 Firefox/50.0 Build ID: 20161129173726 Steps to reproduce: The full response of an HTTP request is not available to the webextension framework. Expected results: It would be nice to optionally have a responseBody attribute accessible in the browser.webRequest.onCompleted listener.
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
The patch I sent has the responseBody in byte array format. It's the responsiblity of the webextension to, for example, gunzip content if it's zipped. I figured the burden shouldn't be on firefox to decode the data since asking for this will already add a burden to the browser.
Reporter | ||
Comment 3•7 years ago
|
||
If the content-encoding is gzip, this extension will inflate to plaintext. Otherwise, the responseBody will be shown as a byte array.
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•