[ 
https://issues.apache.org/jira/browse/CB-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839276#comment-13839276
 ] 

Matthew Ronemous commented on CB-4701:
--------------------------------------

I understand your point of view.  If we could we would convert the site in 
question to an HTML5 based application.  However it is an old mission critical 
custom facing website that is used by legacy devices.  The website is legacy 
JSP solution so copying it to the device isn't an option.  We did copy the 
cordova assets to the remote website as a workaround.  This was working before 
on earlier versions so I guess thats the primary question.  What changed to 
cause it not to work?   

> Local file permission error when running www from remote site.
> --------------------------------------------------------------
>
>                 Key: CB-4701
>                 URL: https://issues.apache.org/jira/browse/CB-4701
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 3.0.0
>         Environment: Tomcat Server: JSP legacy website 
>            Reporter: Matthew Ronemous
>            Assignee: Joe Bowser
>            Priority: Minor
>
> http://stackoverflow.com/questions/18138605/permission-error-when-accessing-local-assets-via-remote-website
> My android Cordova project simply references a remote server to get its web 
> content.
> window.location = "http://SERVER/Page.html";;
> In 2.9 I was able to reference file:///android_asset/ to access local files. 
> In config.xml I had <access origin="*" /> and <access 
> origin="http://127.0.0.1*"/> (not certain if both were necessary but it 
> worked).
> In 3.0 I get a permission error when trying to access the files. What is the 
> correct configuration to tell Cordova 3 to enable local file access? In this 
> case I'm trying to host all of the Cordova files cordova.js, ect... as local 
> file assets.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to