Is there any WebKit-specific error handling for when something with the proxy configuration goes wrong?
In the failure cases I've been able to test — e.g. failing authentication with the proxy server — WebKit surfaces it through the navigation delegate's didFailProvisionalNavigation callback as a generic:
"Could not connect to the server." — NSURLErrorCannotConnectToHost (code -1004)
Since that's indistinguishable from an ordinary connectivity failure, is there any way to tell proxy/relay failures apart from normal browsing errors? I would want to be able to surface a distinct "proxy unavailable" state to the user rather than a generic connection error.
Topic:
WebKit
SubTopic:
WebViews Q&A