| Summary: | webkit-pdfjs-viewer URI scheme should not be blocked by CSP | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | Assignee: | Patrick Griffis <pgriffis> | |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bugs-noreply, mcatanzaro, thorton, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Michael Catanzaro
2022-07-28 16:44:34 PDT
(In reply to Michael Catanzaro from comment #0) > It's an implementation detail of the website. I meant to write: it's an implementation detail of WebKit, not something that the website could be expected to know about. Patrick says we need to call LegacySchemeRegistry::schemeShouldBypassContentSecurityPolicy from somewhere. Not clear where would be the nicest place to do this, since it only needs to happen once, not once for each PDFDocument. (In reply to Michael Catanzaro from comment #2) > Patrick says we need to call > LegacySchemeRegistry::schemeShouldBypassContentSecurityPolicy from > somewhere. Not clear where would be the nicest place to do this, since it > only needs to happen once, not once for each PDFDocument. Well that was a dumb question. We should do it wherever we register the scheme. (In reply to Michael Catanzaro from comment #3) > Well that was a dumb question. We should do it wherever we register the > scheme. Well it's more complicated than this. The scheme is never actually explicitly registered anywhere. It's just hardcoded into LegacySchemeRegistry.cpp. Pull request: https://github.com/WebKit/WebKit/pull/2922 Committed 253040@main (e9c47d55c988): <https://commits.webkit.org/253040@main> Reviewed commits have been landed. Closing PR #2922 and removing active labels. |