fix(canvas): normalize legacy attachment content URLs #1845
Reference in New Issue
Block a user
Delete Branch "fix/legacy-content-attachment-uri"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
/workspaces/<ws>/content/<file>/contentattachment URIs to the current/pending-uploads/<file>/contentendpoint.Why
External/poll-mode attachment messages can still contain the older content URL shape. The live canvas currently treats that as a non-platform image URL, causing the browser to request a route that no longer exists.
Verification
npm test -- --run src/components/tabs/chat/__tests__/uploads.test.tsgit diff --check[core-qa-agent] APPROVED
Reviewed regression coverage and local verification. Canvas now treats the legacy /workspaces//content//content shape as a platform attachment and rewrites it to the current pending-upload endpoint; malformed legacy paths remain raw. No QA findings.
[core-security-agent] APPROVED
Reviewed auth boundary: the new resolver only recognizes relative legacy platform content URLs and keeps third-party HTTP(S) URLs on the unauthenticated external path. Platform bytes still fetch through the existing auth-header flow. No security findings.
/qa-recheck
/security-recheck