CaseMark pulls document previews back behind its own front door
Client files now load through Mike's backend instead of sending the browser a signed link straight to storage.
CaseMark's document viewer used to hand the browser a temporary signed link and let it fetch files directly from Case Vault, the fork's document store. That link was visible in network traffic, and the cross-origin trip was also making previews fail outright in production with a "failed to load" error.
CaseMark fixed both at once by routing each file through Mike's own backend. The document now loads on the app's own domain, the app's login and permission checks stay the gatekeeper, and storage credentials never reach the browser. The honest cost: the backend holds each file fully in memory before sending it, with no streaming. Teams pushing large documents to many users at the same time will want to watch that ceiling before rolling it out widely.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?