workaround for reachability when already online

[Sega-Zero]

No description provided.

[Sega-Zero]

more info on #65 (sorry, couldn't find how to set pull request there)

[tonymillion]

The problem here is that 0 flags can indicate no connectivity.

As I've said before you shouldn't use Reachability to determine if you should make a network request, you should always try the request and if it fails queue it up to be executed once Reachability indicates network is reachable.

[Sega-Zero]

The bad thing is that this flag==0 happens right in the case you've described. and when the internet becomes online, only flag==0 is received. no kSCNetworkReachabilityFlagsReachable at all. and this happens both 10.9 and 10.10 but not all machines

[Sega-Zero]

I found the reason of this behavior: the problem was that i was creating Reachability with full url, not the host. in this case reachability always sends 0 in flags

I think the constructor should be aware of that and extract correct host value

[tettoffensive]

@Sega-Zero I was wondering why reachability was always backwards when i started up my app for Reachability with @"http://myurlhere.com/" I would first get reachable, then unreachable next (even though it was always reachable. Your last comment here fixed this issue!

[NSURL URLWithString:@"http://myurlhere.com/"].host was the fix.