[Webkit-unassigned] [Bug 209465] [Curl] Proxy setting API does not work until Network process starts.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Mar 31 09:54:43 PDT 2020


--- Comment #5 from Basuke Suzuki <Basuke.Suzuki at sony.com> ---
(In reply to Takashi Komori from comment #4)
> When a browser connects via proxy it send a request line to the proxy as
> almost same as direct connection, and gets response from the proxy.
> Whether using proxy or not, request and response sequence is almost same
> (The request line differs).
> So just checking responses we can't distinct whether the responses come
> directly or via proxy.
> In this test we use the behavior that a browser always connects to the proxy
> server when proxy is set.
> If proxy setting works, the browser connects to specified proxy server
> otherwise it connects to specified URL directly.
> We can check the response is from proxy or not by only checking response.
> In EnableProxyBeforeLoading test, if proxy server is set to
> WKPageLoadURL always connects to it.

Make sense. Looks good to me.

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/20200331/9642f5cb/attachment-0001.htm>

More information about the webkit-unassigned mailing list