[Webkit-unassigned] [Bug 138169] WKWebView does not support NSURLProtocol-style interception of http or https

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=138169

Simon Brooks <brookss at vmware.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brookss at vmware.com

--- Comment #49 from Simon Brooks <brookss at vmware.com> ---
(In reply to Ian Ragsdale from comment #43)
> (In reply to Maciej Stachowiak from comment #40)
> > For folks following this bug, who would consider it sufficient to have a way
> > to define per-app or per-WKWebView proxy setting? If it wouldn't be
> > sufficient, could you describe what it might be missing for your use case?
> 
> I believe this would be sufficient for my app's purposes. I think
> per-WKWebView would be preferable to per-app but per-app would likely
> suffice.

Few follow up questions to try and understand what the proxy enablement would actually allow (disclosure - I work with Ian):

Would the proxy configuration allow connection to a local proxy? (and if so would that work even with ATS enabled with the local proxy not being able to offer a valid SSL cert)

how to chain a further proxy that may require user authentication?

Would it be better/more consistent to allow the app to participate in a per-app VPN type configuration, possibly even using a packet tunnel extension provided within the app's own package? I'm not sure that any of the other alternatives maintain the background downloading capabilities.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200127/bc10df43/attachment-0001.htm>