799198 - Need a way to fetch file:// and http:// resources from the server

Status: NEW

(DevTools :: about:debugging, enhancement, P3)

Description

[Mihai Sucan [:msucan]]

Currently the Web Console actor only gives URIs to the client. The responsibility of fetching a resource pointed at by the given URI falls on the client. This can work in the current local-only setup, but when you do remote debugging you need the server to send you the resource pointed at by the page error, console API, network request, etc.

We need support for this capability not just for the http-based resources. We need this for chrome:// and file:// URIs as well - think B2G debugging.

Comment 1

[Mihai Sucan [:msucan]]

I know there's a way to fetch script sources, but isn't this specialized for scripts? Can we make it more generic, for stylesheets, images and other network requests/file loads? I haven't looked much into this part of the code...

I would imagine a ResourceActor that I could create an instance of, and give it a URI that I want to send to the client, an nsIURI, or even an nsIFile - just like we have object actors.

Comment 2

[Panos Astithas (he/him) [:past] (please ni?)]

I think you need to base your ResourceActor on SourceActor in dbg-script-actors.js. I know that Nick and Dave have been changing this code in the source maps work, but this might not concern you much.

Since you don't use debugger actors in the web console actors yet, you can just go ahead and copy most of the functionality, but when we get to bug 783499 we can think about how to best integrate the two.

Comment 3

[Rob Campbell [:rc] (:robcee)]

this will likely depend on the bulk data bug, says mihai.

Comment 4

[Mihai Sucan [:msucan]]

We need that to transfer images and other binary file types. Otherwise we need to work around with LongStringActor and base64, which are not ideal for the given purpose.

Comment 5

[Panos Astithas (he/him) [:past] (please ni?)]

Filter on BLACKEAGLE2.

Comment 6

[Panos Astithas (he/him) [:past] (please ni?)]

Who am I kidding? I'm not going to work on this any time soon.