add timestamps to frame retrieval API#56
Merged
Merged
Conversation
robertmcabee
approved these changes
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@robertmcabee
When fetching each frame, the frontend needs to read the
X-Frame-Timestampresponse header before consuming the body as a blob, since headers become inaccessible after the body is read, and then store each frame as an object containing both the blob URL and that timestamp string rather than just a bare URL. Any code that previously looped over the frames array treating each element as a URL directly (like the GeoTIFF parser) needs to be updated to pull the URL offframe.urlinstead.