NetworkProcess::preconnectTo preconnects to custom URL schemes, while NetworkConnectionToWebProcess::preconnectTo does not. The former's behavior should match the latter's. This will also fix the debug test failures in TestWebKitAPI.WebKit.DownloadNavigationResponseFromMemoryCache and TestWebKitAPI.ContentFiltering.LazilyLoadPlatformFrameworks introduced by https://bugs.webkit.org/show_bug.cgi?id=207777. The reason for the debug test failure is that both of these tests register a custom HTTP scheme handler, and the scheme handlers are returning responses to the preconnect request which is causing the assert in PreconnectTask::didReceiveResponse to fire.
<rdar://problem/59606178>
Created attachment 391214 [details] Patch
Created attachment 391217 [details] Patch
Comment on attachment 391217 [details] Patch Clearing flags on attachment: 391217 Committed r257008: <https://trac.webkit.org/changeset/257008>
All reviewed patches have been landed. Closing bug.