Skip to main content

Fire Arrow Server 2.1.5

· 2 min read
Till Gerken
Till Gerken
CTO

Fire Arrow Server 2.1.5 has been released.

  • (bugfix) Reading externalized Binary content with $binary-access-read no longer fails with 500 Internal Server Error

Bug Fixes​

Reading externalized binary content failed with a server error​

When a Binary resource's content is offloaded to external storage, $binary-access-read streams the stored bytes back to the caller. Before 2.1.5, calling $binary-access-read on such a Binary failed with 500 Internal Server Error and returned no content, even for a caller with the correct read access. Any workflow that stored a Binary with inline data — for example, through a transaction bundle — and later read its content back through $binary-access-read hit this error.

The cause was a missing timestamp. When the server retrieved the stored content details from external storage, it did not include the "last modified" time, which is required to build the Last-Modified response header. The absent value aborted the read before any bytes were streamed.

Starting with 2.1.5, the server restores that timestamp from the stored object's metadata, falling back to the object's creation time for content written before this metadata was recorded. $binary-access-read now returns the stored bytes with a valid Last-Modified header instead of failing. No configuration change is required, and binary content written by earlier versions is handled through the creation-time fallback.

This complements the 2.1.4 fix that allowed $binary-access-read through your existing read rules: with both releases, a permitted caller can now both reach the operation and receive the externalized content.