Question

64

Chrome Extension - How to get HTTP Response Body?

rated 0 times [ 69] [ 5] / answers: 1 / hits: 68843 / 11 Years ago, fri, august 30, 2013, 12:00:00

It seems to be difficult problem (or impossible??).
I want to get and read HTTP Response, caused by HTTP Request in browser, under watching Chrome Extension background script.
We can get HTTP Request Body in this way

chrome.webRequest.onBeforeRequest.addListener(function(data){

    // data contains request_body

},{'urls':[]},['requestBody']);

I also checked these stackoverflows

Chrome extensions - Other ways to read response bodies than chrome.devtools.network?

Chrome extension to read HTTP response

Is there any clever way to get HTTP Response Body in Chrome Extension?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

kylanalis

Add To Favorites

Follow

Total Points: 438

Total Questions: 85

Total Answers: 102

Location: Barbados

Member since Sun, Nov 27, 2022

1 Year ago

kylanalis questions

1 How to pass State in Context React

Sat, Oct 2, 21, 00:00, 3 Years ago

1 How to get rid of or remove spinners/arrows in react-select?

Tue, Oct 13, 20, 00:00, 4 Years ago

1 [NodeJs][Sequelize] ReferenceError: Cannot access 'ModelName' before initialization

Sat, Apr 11, 20, 00:00, 4 Years ago

1 How can I load a local image in THREE.js?

Thu, Feb 13, 20, 00:00, 4 Years ago

1 trigger('change') is not working on Select

Tue, Jan 7, 20, 00:00, 4 Years ago

View All

answered 11 Years ago johnnyblaynes · Accepted Answer

I can't find better way then this anwser.

Chrome extension to read HTTP response

The answer told how to get response headers and display in another page.But there is no body info in the response obj(see event-responseReceived). If you want to get response body without another page, try this.

var currentTab;

var version = 1.0;



chrome.tabs.query( //get current Tab

    {

        currentWindow: true,

        active: true

    },

    function(tabArray) {

        currentTab = tabArray[0];

        chrome.debugger.attach({ //debug at current tab

            tabId: currentTab.id

        }, version, onAttach.bind(null, currentTab.id));

    }

)





function onAttach(tabId) {



    chrome.debugger.sendCommand({ //first enable the Network

        tabId: tabId

    }, Network.enable);



    chrome.debugger.onEvent.addListener(allEventHandler);



}





function allEventHandler(debuggeeId, message, params) {



    if (currentTab.id != debuggeeId.tabId) {

        return;

    }



    if (message == Network.responseReceived) { //response return 

        chrome.debugger.sendCommand({

            tabId: debuggeeId.tabId

        }, Network.getResponseBody, {

            requestId: params.requestId

        }, function(response) {

            // you get the response body here!

            // you can close the debugger tips by:

            chrome.debugger.detach(debuggeeId);

        });

    }



}

I think it's useful enough for me and you can use chrome.debugger.detach(debuggeeId)to close the ugly tip.

sorry, mabye not helpful... ^ ^