You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
in our system we have to use cross-origin isolation, including 'Cross-Origin-Embedder-Policy: require-corp' policy.
Therefore when I'm loading Status Embed frame the browser requires 'Cross-Origin-Resource-Policy: cross-origin' header in a response.
It is absent so frame is not loaded.
How is Status Embed supposed to be loaded in this case? May CORP header be added, or we should change something on our side?
This is Jesse from the Statuspage support team. Welcome to the community and thanks for reaching out about how you would work with CORP headers. If you are using the recommended status embed then this is not something that can really be changed since it is a pre-built tool.
In your case, it would make sense to create a custom status embed instead. Essentially, it's just calling our Status API and you could modify it from there. Hopefully that is helpful for you on this!