Remove SecurityPolicy APIs for handling a trustworthy safelist
This CL removes the following methods: WebSecurityPolicy::AddOriginToTrustworthySafelist SecurityPolicy::AddOriginToTrustworthySafelist SecurityPolicy::IsOriginTrustworthySafelisted Outside tests, these methods are only used to populate SecurityPolicy's safelist from SecureOriginAllowlist. The last one is only called from SecurityOrigin::IsSecure and SecurityOrigin::IsPotentiallyTrustworthy, but they can rely on SecureOriginAllowlist::IsOriginAllowlisted instead. Some tests also rely on SecurityPolicy::AddOriginToTrustworthySafelist, but they can directly set the command line parameters to configure the allow list accordingly. There is no observable behavior change but this makes easier to compare SecurityOrigin::IsSecure and SecurityOrigin::IsPotentiallyTrustworthy with network::IsURLPotentiallyTrustworthy, to facilitate unification of all these APIs. Bug: 1153336 Change-Id: I2df13abbdf697ec78136a16373b0b9fc6372bf88 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2612947Reviewed-by:Mike West <mkwst@chromium.org> Reviewed-by:
Sean Topping <seantopping@chromium.org> Commit-Queue: Frédéric Wang <fwang@igalia.com> Cr-Commit-Position: refs/heads/master@{#844000}
Showing
Please register or sign in to comment