Skip to main content

Fire Arrow Server 1.9.1

· One min read
Till Gerken
Till Gerken
CTO

Fire Arrow Server 1.9.1 has been released.

  • (bugfix) Fix pre-signed attachment URLs not being recognized after client round-trip

Bug Fixes​

Pre-signed attachment URLs not recognized after client round-trip​

When a client stored an attachment with a pre-signed download URL back to the server (for example, an Attachment.url received from an earlier read), the server is supposed to recognize that URL as its own and replace it with the internal storage reference. This ensures the download link is always freshly signed when the resource is read again, rather than retaining a time-limited token that will eventually expire.

Due to how Azure Storage encodes blob paths, the URL returned to clients could contain percent-encoded path separators (e.g. %2F instead of /). The server did not account for this encoding when trying to match the URL, causing it to silently skip the rewrite. The expired pre-signed URL was then persisted as-is in Attachment.url, permanently breaking any out-of-band download — for example, media fetched by WhatsApp or other messaging platforms that retrieve attachments independently.

1.9.1 correctly handles percent-encoded paths, so pre-signed URLs are now reliably recognized regardless of how the client returns them.