Avoid reparsing Content-Security-Policy headers in AncestorThrottle
The logic checking the X-Frame-Options header in the AncestorThrottle was manually parsing the Content-Security-Policy headers for finding out whether the 'frame-ancestors' directive was used (since the X-Frame-Options header should be ignored if the 'frame-ancestors' CSP directive is being used). With this change we use instead the already parsed Content-Security-Policy in parsed_headers for checking that. This avoids unnecessary additional parsings of the CSP headers in the AncestorThrottle. Bug: 1032139 Change-Id: Ibe0c64cd7eb1e6f8ff0fa915a81db6248399da1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2292051Reviewed-by:Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Antonio Sartori <antoniosartori@chromium.org> Cr-Commit-Position: refs/heads/master@{#789919}
Showing
Please register or sign in to comment