access to about/home pages cancels the connection process #6
Comments
mtigas
pushed a commit
that referenced
this issue
Feb 14, 2017
Use CKHTTPConnection as a custom NSURLConnection when handling requests from UIWebView. This gives more fine-grained control over the actual connection and SSL handshake than just being a NSURLProtocol delegate, and now we can set explicit SSL options like forcing TLS versions to disable SSL. Also borrow some code from Onion Browser to directly handle data as it comes in before passing it to the WebView (including ungzipping or inflating it) to write our custom Javascript directly into the HTML document data instead of evaluating it after the page loads. This will make it possible to cut off certain Javascript functions before a page can use them (like WebSockets or local storage). Also leave some commented out code for making fake Content-Security-Policy headers in the response, which WebKit will handle properly if seen, to be able to selectively disable all Javascript, fonts, media, external connections, etc. This will eventually be hooked up to per-host security settings expanded from the per-host cookie settings already in place (as in issue #6).
mtigas
pushed a commit
that referenced
this issue
Feb 14, 2017
Open (default), No-connect, and Strict Closes #6
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you use the central icon at the bottom and access the about page or the home page before the connection is complete, it seems to stop the connection process, leaving you with no other option than exiting, killing and restarting the app to perform a new connect.
Also, when you do so, the home page reads "Now connected" even if you are not connected at all.
The text was updated successfully, but these errors were encountered: