Adding the PDF's host to the Suite's approved domains made the embed stop working
What you are seeing
Adding the PDF's host to the Suite's approved domains made the embed stop working.
#Why it happens
An approved host is fetched directly by the reader's browser instead of through Capable's proxy, and most PDF hosts do not permit browsers on other domains to read their files.
#What to do
Remove the domain from the approved list so the proxy is used again, or attach the PDF to the page. Only approve a host you know serves files with cross-origin access enabled.
#Settings involved
Setting | Where | What it does |
|---|---|---|
Approved external domains (Capable Suite | Capable Suite admin > Capable settings > Egress | - |
Edition | Capable Suite capability list | - |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Approved external domains (Suite) | 10 domains | One fixed group, admin-only to save. |
#A few things that catch people out
Approving the PDF's host under the Suite's Egress settings can break the embed rather than help it, because the file is then fetched directly by the browser and most PDF hosts refuse that.
#Related
Pasting a PDF link into the editor does not create a PDF embed
The macro does not claim pasted links; there is no automatic conversion.
Signed-out readers on a public page see "Sign in to view this PDF" or "PDF unavailable" instead of t
Signed-out visitors are never issued a Capable access token, so the app cannot fetch the f
Export and published sites
The rest of this family.
Found it? Good.
