Support custom scheme or domain for local content on Android

[AshleyScirra]

Feature Request

As of cordova-ios 6.0.0, you can use the following in config.xml:

<preference name="scheme" value="app"/>
<preference name="hostname" value="localhost"/>

Then the app runs on app://localhost instead of file://. This does not appear to work on Android though - having tried it the app still runs at a file:// URL.

Motivation Behind Feature

Running on file: brings a number of origin-related problems. Notably on file:, the browser treats every resource as a different origin, causing some features to be blocked. In particular, fetch() cannot be used at all, because it's actually written in to the specification that it can just throw on file: protocol and that's what Chromium chooses to do.

Further, this will allow Cordova Android apps to more closely align their codebases with iOS, since in both cases it can be running on the same URL (app://localhost) with identical capabilities regarding the security origin, use of fetch(), etc.

Alternatives or Workarounds

Right now we are forced to use cordova-plugin-file to read local files, and in many cases use some ugly code involving blobs and blob URLs to work around restrictions with file: URLs. We also have to maintain two significantly different codepaths, one using fetch(), the other using cordova-plugin-file methods.

[jcesarmobile]

Google engineers have recommended to discourage custom schemes in Android apps in this ionic webview issue, so I don't think this is something we should do in cordova-android.

But maybe, as ionic webview does, intercept the requests so they load as http/https urls. That should fix some of the mentioned problems.

But even that, I don't think it should be in cordova-android for now, should start as a separate plugin as cordova-plugin-wkwebview-engine and if people uses it, integrate it in cordova-android later on.

[AshleyScirra]

Ah, I see, interesting.

It sounds like an alternative could be to host on a custom local domain, e.g. https://cordova.local. I imagine this then makes it clear whether the request should be served locally by matching the cordova.local domain on the request, and then everything is still treated as same-origin and using the well-defined and stable https scheme. (Would that work? It seems odd to use https without a certificate, but if that will do the job then I think it's fine)

The real motivation here is to not use file: due to the cross-origin obstacles it would throw in the way, so a custom domain on https would still solve the original problem. So could that work instead?

[brody2consult]

host on a custom local domain, e.g. https://cordova.local.

Or maybe use .localhost tld for an extra 0.001 % safety factor ref:

• https://en.wikipedia.org/wiki/.localhost
• https://en.wikipedia.org/wiki/.local

It seems odd to use https without a certificate

Maybe use http scheme?

[dpogue]

A few notes:

• The WebViewAssetLoader option mentioned by the Google folks requires using the AndroidX WebView, not the built-in WebView.
• The default/suggested URL origin for WebViewAssetLoader is https://appassets.androidplatform.net
• No certificate is needed for HTTPS because it's intercepted on the device before a request is made
• HTTPS is encouraged because lots of web platform functionality is being disabled for non-secure origins

[AshleyScirra]

A key detail is the webview should still think the page is in a secure context, since some features are gated behind that. I'm not sure if a URL like http://cordova.localhost will quality as a secure context. If it does not it would be preferable to use https.

[breautek]

But even that, I don't think it should be in cordova-android for now, should start as a separate plugin as cordova-plugin-wkwebview-engine and if people uses it, integrate it in cordova-android later on.

Just noting that a solution like this should solve #560 ... where the current workaround is to use the ionic webview.

[AshleyScirra]

Note: this may also be necessary to support JavaScript Modules (#1142).

[jcesarmobile]

This PR that uses the WebViewAssetLoader will allow to load apps from https, the <preference name="hostname" value="localhost"/> will be available, the scheme will not, will always use https.

[hariprakashnagar]

Is it possible to change app://localhost to http://localhost/ on Cordova ios >6. We are facing an issue with Cross Origin because app://localhost is not a valid domain.

[breautek]

Is it possible to change app://localhost to http://localhost/ on Cordova ios >6. We are facing an issue with Cross Origin because app://localhost is not a valid domain.

Short answer is this isn't possible.

On iOS the WKURLSchemeHandler is the backing API and only allows you to use a scheme that is not already registered. This means that all well known standard schemes like http or https is automatically not supported by the iOS API.

On Android, the WebViewAssetLoader is the backing API and it only supports setting either http or https as the scheme. So this creates a situation where you cannot make the two platforms consistent.

Your backend must either enable all domains using a wildcard for the Access-Control-Allow-Origin response header, or your backend must read the request's Origin header and dynamically set the Access-Control-Allow-Origin response header accordingly if the Origin is a value that you expect.

[hariprakashnagar]

Is it possible to change app://localhost to http://localhost/ on Cordova ios >6. We are facing an issue with Cross Origin because app://localhost is not a valid domain.

Short answer is this isn't possible.

On iOS the WKURLSchemeHandler is the backing API and only allows you to use a scheme that is not already registered. This means that all well known standard schemes like http or https is automatically not supported by the iOS API.

On Android, the WebViewAssetLoader is the backing API and it only supports setting either http or https as the scheme. So this creates a situation where you cannot make the two platforms consistent.

Your backend must either enable all domains using a wildcard for the Access-Control-Allow-Origin response header, or your backend must read the request's Origin header and dynamically set the Access-Control-Allow-Origin response header accordingly if the Origin is a value that you expect.

Yes, we can do this but PDF embed viewer does not work with Web view [Mobile browser] if we use from hosted URL.