Use a standard scheme to test potential trustworthiness
In [1] a test was added to to verify trustworthiness of custom schemes. However, the ones using IsOriginPotentiallyTrustworthy fails because non-opaque origin must be a "standard scheme" i.e. follow [2]. This CL adjusts the tests to actually use a "standard scheme", which is closer the intent to test chrome-extension URLs. It also removes corresponding test from SecurityOriginTest, as it does work well with url utils [3]. [1] https://chromium-review.googlesource.com/c/chromium/src/+/2593629 [2] https://tools.ietf.org/html/rfc3986#section-3 [3] crbug.com/1163060 Bug: 1153336, 1163060 Change-Id: I3e7f1d91558a97b1722a742d89c514b984b56ac2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595424Reviewed-by:Mike West <mkwst@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Commit-Queue: Frédéric Wang <fwang@igalia.com> Cr-Commit-Position: refs/heads/master@{#841991}
Showing
Please register or sign in to comment