CaseMark stops handing document URLs to the browser
A small but meaningful security upgrade to how privileged documents reach the user.
Until now, opening a PDF or Word file in CaseMark's fork meant the browser was sent a short-lived signed link straight to the underlying cloud storage. The team rewired this so the backend fetches the file itself and streams the bytes down to the user, with the right content-type headers and an instruction not to cache. The storage URLs and the API keys behind them never touch the browser, and authentication stays consolidated at a single backend boundary.
A smaller second tweak: the settings page now loads its various account-status checks in parallel behind a spinner, so users no longer briefly flash a misleading "missing key" warning while their profile is still loading.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?