You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Becky Gibson <gi...@gmail.com> on 2013/01/30 22:27:24 UTC

SOLVED the iOS FileTransfer Errors I was seeing

I took the time to reacquaint myself with the Jasmine tests and also did
some debugging to see why I was consistently getting a failure in the
FileTransfer tests.

I was specifically having problems with the download to an unknown host.
 After looking at (and taking the time to understand) the tests I realize
that foobar.apache.org SHOULD be in the whitlelist.  I was getting a fail
in the download from unknown host test due to my internet provider trying
to return a "helpful" search assist page for foobar.apache.org!  Since the
internet provider url was not in the whitelist, I was getting a whitelist
error back in the payload rather than a failure.  When I put the internet
provider (*verizon*) in the whitelist I get a timeout.   However, when I
run in 3G mode the download  unknown host test passed (although others fail
due to timeouts).

Whew - mystery solved.

Re: SOLVED the iOS FileTransfer Errors I was seeing

Posted by Andrew Grieve <ag...@chromium.org>.
Wow! That's a fun one! I'm trying to think of a way we can make these tests
more robust, but just using a local server won't let you test
whitelist-related issues :(.


On Wed, Jan 30, 2013 at 4:39 PM, Michal Mocny <mm...@chromium.org> wrote:

> That is ridiculous.. but sadly becoming common for many 404 pages these
> days.  A good solution is to use a different DNS, such as the public one
> provided by google (8.8.8.8).
>
> -Michal
>
>
> On Wed, Jan 30, 2013 at 4:27 PM, Becky Gibson <gibson.becky@gmail.com
> >wrote:
>
> > I took the time to reacquaint myself with the Jasmine tests and also did
> > some debugging to see why I was consistently getting a failure in the
> > FileTransfer tests.
> >
> > I was specifically having problems with the download to an unknown host.
> >  After looking at (and taking the time to understand) the tests I realize
> > that foobar.apache.org SHOULD be in the whitlelist.  I was getting a
> fail
> > in the download from unknown host test due to my internet provider trying
> > to return a "helpful" search assist page for foobar.apache.org!  Since
> the
> > internet provider url was not in the whitelist, I was getting a whitelist
> > error back in the payload rather than a failure.  When I put the internet
> > provider (*verizon*) in the whitelist I get a timeout.   However, when I
> > run in 3G mode the download  unknown host test passed (although others
> fail
> > due to timeouts).
> >
> > Whew - mystery solved.
> >
>

Re: SOLVED the iOS FileTransfer Errors I was seeing

Posted by Michal Mocny <mm...@chromium.org>.
That is ridiculous.. but sadly becoming common for many 404 pages these
days.  A good solution is to use a different DNS, such as the public one
provided by google (8.8.8.8).

-Michal


On Wed, Jan 30, 2013 at 4:27 PM, Becky Gibson <gi...@gmail.com>wrote:

> I took the time to reacquaint myself with the Jasmine tests and also did
> some debugging to see why I was consistently getting a failure in the
> FileTransfer tests.
>
> I was specifically having problems with the download to an unknown host.
>  After looking at (and taking the time to understand) the tests I realize
> that foobar.apache.org SHOULD be in the whitlelist.  I was getting a fail
> in the download from unknown host test due to my internet provider trying
> to return a "helpful" search assist page for foobar.apache.org!  Since the
> internet provider url was not in the whitelist, I was getting a whitelist
> error back in the payload rather than a failure.  When I put the internet
> provider (*verizon*) in the whitelist I get a timeout.   However, when I
> run in 3G mode the download  unknown host test passed (although others fail
> due to timeouts).
>
> Whew - mystery solved.
>