On 22 touko, 20:39, Boris Zbarsky <[email protected]> wrote: > [email protected] wrote: > > If I don't want re-write the URIs, core changes are needed. I can only > > think of checking the content type of the root document for each load > > and if that is multipart/related, then redirect to my protocolWh > > handler. Quick search in cross-reference tells me that NS_NewChannel > > is being called in several places like nsDocShell, nsScriptLoader, > > nsObjectLoadingContent, CSSLoaderImpl etc. The document and its > > related resources loading process is very complex. Would there be any > > central place where to handle the URIs in? Or could anyone think of a > > centralized way of accomplishing the same result? > > You need this for all protocols, not just HTTP, so you can't leverage > the application cache stuff, right?
I'm not so sure. Why would I need anything else but HTTP/HTTPS? > What javascript actually breaks, and why, if you go the URI-rewriting route? Any Javascript that rewrites some URIs itself. This would end up fetching some resources from the network instead of from the archive. Then again, I assume MHTML won't work well with very dynamic content or AJAX anyway. It might be that the URI-rewriting route is the only feasible solution, even if I'm not very fond of it. _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
