Return the right value for rawResponse in CDP

[molant]

Right now rawContent returns a Buffer with the right size but no content, and rawResponse doesn't return anything.

• rawContent
• rawResponse

[molant]

Can't find a way to get the byte for any of those :(
I've opened this issue in the hopes of getting someone to answer...
Moving this back to the backlog.

[molant]

rawContent is done. I'm still clueless on how to obtain rawResponse. If we have to do another request from node then I think we should change that property to be asynchronous so we don't request it if not needed.

[molant]

Updating the title to better reflect what is missing.

[molant]

@paulirish, @ebidel, do you know if there is a way to get the real bytes of a response? I can get the decoded ones but nothing else :(
If not, we might have to rely on request and use the same headers than the original request.

[paulirish]

@molant replied on ChromeDevTools/devtools-protocol#12 -- It seems like doing a followup request from node is the only workaround for this right now.

[alrra]

@paulirish Thanks for looking into it!

[molant]

If we have to use request to do the reply we need to take into account the headers and cookies used in originally.

[molant]

Also, I think that we should change the type of rawResponse from Buffer to Promise<Buffer>. The reason is that not all the rule configurations require this value and we will be making extra requests that are not needed and thus wasting time and bandwidth. We could potentially do the same for rawBody, I've seen it takes sometimes a bit to get the data too.

[molant]

After syncing with @alrra my current plan for this is to:

• make rawResponse and rawBody methods that return a Promise<Buffer>. This way we are not making things when we don't need.
• user requester to get the rawResponse in remote-debugging-connector. Looks like this is the only way to get the response. We will use the same headers as the original request