Check a saved catalog frame policy and its ancestors
Admin ·
A catalog is part of a studio’s document interface. Review the policy recorded on the catalog response and compare it with the expected containing origins.
Check the catalog frame chain
Choose Load example and Check framing policy. The capture begins with an informational 103 and ends with status 200. The protected document origin is https://catalog.example.com.
The two declared ancestor origins are the catalog and https://studio.example.com. In the enforcing policy, the catalog matches 'self' and the studio matches its explicit HTTPS source. Both rows report Matches.
Read the recorded precedence
The saved response also includes X-Frame-Options: DENY. The current HTML model checks the enforcing frame-ancestors directive first and sets aside that X-Frame-Options field.
A separate report-only CSP declares frame-ancestors 'none'. Its disposition appears in the report. To compare another saved scenario, update the declared chain and read the result for each ancestor.
W3C CSP Level 3, frame-ancestors navigation response checkWHATWG HTML, the X-Frame-Options header
Keep the capture with the report
Download the JSON report to retain the response block, policy dispositions and ancestor results. Input origins and captures are analyzed on this device.
Check unsupported expressions in the saved policy when the report says Review. A default-src directive does not supply a frame-ancestors rule.
W3C CSP Level 3, frame-ancestors navigation response checkWHATWG HTML, the X-Frame-Options header
Common questions
Does SAMEORIGIN apply to just the nearest frame?
In the current HTML model, all containing ancestors must be same-origin with the framed document.
How are repeated frame-ancestors declarations handled?
The first declaration in a policy is used. Separate enforcing policies are each checked against the chain.