cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: Change to iOS whitelist behavior?
Date Fri, 01 Feb 2013 19:11:00 GMT
CDVSound.m doesn't set the User-Agent, which I think means it's not being
restricted to the white-list.


On Fri, Feb 1, 2013 at 1:45 PM, Shazron <shazron@gmail.com> wrote:

> Not that I am aware of. There might be something related to the user-agent
> changes. Let me verify your results.
>
>
> On Fri, Feb 1, 2013 at 9:03 AM, Becky Gibson <gibson.becky@gmail.com>
> wrote:
>
> > Did I miss a change in our whitelist implementation on iOS?
> >
> > It used to be that I had to make sure audio.ibeat.org was in the
> whitelist
> > before running the mobile-spec media tests.   When testing with 2.4rc2 I
> > noticed this is no longer the case.  My whitelist is:
> >
> > <access origin="http://www.google.com" />
> >
> >     <access origin="*.apache.org*"/>
> >
> >     <access origin="cordova-filetransfer.jitsu.com" />
> >
> >     <access origin="whatheaders.com" />
> >
> > Yet the media plays just fine.  I suspect this change has been in there
> for
> > awhile.  Previously I just assumed media was working because my whitelist
> > was <access origin="*" />
> >
> > When testing with a changed whitelist via config.xml completely removed
> my
> > test app from the device and did a build clean before running again.
> >
> > It looks like whitelist checking doesn't even occur for the media url.
> >
> > just curious!
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message