Capable URL proxy and egress

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

URL-sourced markdown is fetched through the Capable proxy unless the domain is on the tenant's approved egress list, in which case the browser fetches it directly. The app's own declared egress covers only Capable hosts (static.app, client.api.app, server.api.app, ws.api.app, plus Sentry), which is why an unapproved README URL is proxied rather than fetched by the reader.

#Where you do it

A Confluence page holding a Markdown (Capable) macro that renders the Mermaid project readme, including its logo, description, status badges and a gantt chart image, with a floating macro toolbar offe
A readme held in a public repository is fetched and rendered on the page rather than linked to.

Task

Where

Add a markdown document to a page

Confluence editor → /Markdown (Capable) [Suite] or /Markdown macro (Capable) [standalone], or the Markdown byline entry on a published page

Point a macro at a README on GitHub, GitLab or Bitbuck

Configure Markdown → Markdown from URL

Insert an image or diagram from the Capable library

Editor toolbar → + → Image 'From library' or Diagram 'From library'

#Settings that affect this

Setting

Where

What it does

Global settings → Capabilities → Markdow

-

Hiding Markdown removes it from the Capable nav bar and the content byline menu across the site (app property capable-global-hidden-capabilities). It does NOT stop existing macros from rendering.

Space settings → Space Capability Settin

-

Auto shows the byline entry only when the page already carries markdown; Always pins it in every page's byline in that space; Never hides it there. Stored on the space property <APP_HASH>_capable under capabilities.alway

Global settings → Features → AI integrat

-

'Allow AI-powered features across Capable. Turn off to disable AI for all users.' Turning it off removes the Studio (Generate markdown with AI) section from the markdown catalogue. Studio additionally requires the app's

#Limits that apply here

Limit

Value

What happens

URL fetch size limit

2.5 MB

A URL-sourced document larger than 2.5 MB is rejected with 413; a disallowed content type is rejected with 415. The proxy also upgrades http to https, refuses non-http(s) schemes, and blocks IP litera

MCP / Rovo document size cap

512 KB (524,288 characters)

Creating or updating a markdown asset through the Capable tools refuses (rather than truncates) anything larger, with a message telling the caller to split it.

Customer egress domains

1 group, 10 domains

Hard cap on how many domains an admin can approve for direct browser fetching.

Better with company.