views:

52

answers:

1

I am working on an iPad app which has an embedded HTTP server listening on a high port, and I am loading pages from this HTTP server using a UIWebView.

For the functionality of the app, it is important that this works when no network connection is available.

The UIWebView is loading URLs of the form http://localhost:port/path

When I disable Wi-Fi on my iPad and run the application, the UIWebView’s delegate gets a webView:didFailLoadWithError: message with the following NSError object:

Error Domain=NSURLErrorDomain Code=-1009 UserInfo=0x1b4a50 "no Internet connection"

Clearly the SDK is being clever and detecting that it has no Internet connection, but it should be possible to access 127.0.0.1/localhost/::1 without an Internet connection. I will report the bug to Apple but am asking here for advice about possible workarounds for this SDK bug in the meantime.

Please note: changing the architecture of the application is not in scope for this question.

+1  A: 

You may want to investigate defining your own scheme and implementing it with NSURLProtocol instead of running an HTTP server. This will allow you to handle the loading of URLs without having to implement the HTTP protocol, and will get around this issue with the SDK where the HTTP protocol fails early if you have no network connection.

Kevin Ballard
Thank you. This is exactly what I was looking for, and I was even able to have my `NSURLProtocol` subclass respond to the `http` and `https` protocols, effectively overriding the default platform HTTP behaviour. Fantastic.
jbg