[
https://issues.apache.org/jira/browse/CB-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antony Lees updated CB-1947:
----------------------------
Description:
Given the config
<access origin="http://127.0.0.1*"/> <!-- allow local pages -->
<access origin="https://mysite.com"; subdomains="true"/>
<access origin="http://mysite.com"; subdomains="true"/>
I would expect both the http and https sites to load. However only the
unsecured http URL will load, the secure https URL shows an HTML error page
(it's an iframe)
Even if I add
<access origin="*"/>
the same thing happens
I should add that if I deploy the app straight from eclipse (ie not signing it)
the secure URL works fine, so it is only when the whitelist is enforced that it
doesn't seem to work
was:
Given the config
<access origin="http://127.0.0.1*"/> <!-- allow local pages -->
<access origin="https://mysite.com"; subdomains="true"/>
<access origin="http://mysite.com"; subdomains="true"/>
I would expect both the http and https sites to load. However only the
unsecured http URL will load, the secure https URL shows an HTML error page
(it's an iframe)
Even if I add
<access origin="*"/>
the same thing happens
> Secure whitelisted URLs not loading in Android
> ----------------------------------------------
>
> Key: CB-1947
> URL: https://issues.apache.org/jira/browse/CB-1947
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.2.0
> Environment: Android 2.3 and 4.2
> Reporter: Antony Lees
> Assignee: Joe Bowser
>
> Given the config
> <access origin="http://127.0.0.1*"/> <!-- allow local pages -->
> <access origin="https://mysite.com"; subdomains="true"/>
> <access origin="http://mysite.com"; subdomains="true"/>
> I would expect both the http and https sites to load. However only the
> unsecured http URL will load, the secure https URL shows an HTML error page
> (it's an iframe)
> Even if I add
> <access origin="*"/>
> the same thing happens
> I should add that if I deploy the app straight from eclipse (ie not signing
> it) the secure URL works fine, so it is only when the whitelist is enforced
> that it doesn't seem to work
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
