Use explicit third-party domains in PrefetchBrowserTests
PrefetchBrowserTest.CrossOriginWithPreload is currently failing when split cache and UseRegistrableDomainInNetworkIsolationKey are enabled. The cause is the cross_origin_server_'s URLs only differing from the embedded_test_server's in the port used, resulting in an identical scheme and eTLD+1. We thus explicitly specify third-party domains that differ in eTLD+1, also changing other tests for consistency. We also disable HTTPS to avoid SSL certificate errors from mismatched host names. Bug: 1035499 Change-Id: Ibb6b566814743343a93e6538cecd1f5771486810 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2001140 Commit-Queue: Alex Turner <alexmt@chromium.org> Reviewed-by:Shivani Sharma <shivanisha@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#731999}
Showing
Please register or sign in to comment