Does anyone know how to get the page source of a page as a string without using XMLHttpRequest?

The closest I have got is "pageSource = window.document.documentElement.innerHTML;"
But that is not identical to the original source.

XMLHttpRequest works, but it is a bit slow. I was hoping to be able to read from the in memory cache. Opening a new tab with "view-source:url" is quick, I would like to get that speed.

I've also tried a hidden IFRAME with src "view-source:url", but that just says "Failed to load resource". I can't find any way of creating an invisible chrome window or tab to try extracting from it.

Here is one page of stuff I was trying:
http://stackoverflow.com/questions/2...ge-source-code

Hi twinsen,

Here's a sample code I use in SingleFile to get the current document HTML content, it's not the exact content but it is very near.

Code:

function getDoctype(doc) {
	var docType = doc.doctype, docTypeStr;
	if (docType) {
		docTypeStr = "<!DOCTYPE " + docType.nodeName;
		if (docType.publicId) {
			docTypeStr += " PUBLIC \"" + docType.publicId + "\"";
			if (docType.systemId)
				docTypeStr += " \"" + docType.systemId + "\"";
		} else if (docType.systemId)
			docTypeStr += " SYSTEM \"" + docType.systemId + "\"";
		if (docType.internalSubset)
			docTypeStr += " [" + docType.internalSubset + "]";
		return docTypeStr + ">";
	}
	return "";
}

var htmlContent = getDoctype(document) + document.documentElement.outerHTML;

I hope it can help you.

Thanks for that, its got some of the stuff that I was missing when using innerHTML.
The worst time for XMLHttpRequest for a few sample sites was 1.1 seconds, whereas your code worst time was 40 milliseconds.
I think the minor differences in content are worth it for the speed increase.

Actually, i was facing the same issue when porting JSONView to Chrome. Some users found that XHR was not acceptable.

Nevertheless, it seems that chrome will offer soon an extension API to do this kind of stuff more easily.

Define Chromium extensions API for networking

Define an API for Chromium extensions to access the network stack. We already defined an API that exposes proxy settings to extensions. (willchan)

cf : http://www.chromium.org/developers/d.../network-stack

If you want to get it after the page's JS has affected it and all you can do it pretty much the same way you did originally, just with outerHTML:

Code:

pageSource = window.document.documentElement.outerHTML

But yeah, not the raw source like view-source without XHR or a future API like above.