Implement SecurityOrigin::IsPotentiallyTrustworthy with network::IsOriginPotentiallyTrustworthy
After previous refactoring, the body of SecurityOrigin::IsPotentiallyTrustworthy is essentially equivalent to network::IsOriginPotentiallyTrustworthy, except that it first DCHECKs the protocol is not "data" and handles opaque origins specially. This CL relies on network's method to implement SecurityOrigin's one in order to reduce code duplication. There should be no visible behavior change. Bug: 1153336 Change-Id: Ib88bd716174d4ac68c50bcc99a82fd2e51303b93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2615260Reviewed-by:Mike West <mkwst@chromium.org> Commit-Queue: Frédéric Wang <fwang@igalia.com> Cr-Commit-Position: refs/heads/master@{#844028}
Showing
Please register or sign in to comment