Enable API Before Sync and Return 503 When Not Synced #1155
Conversation
This file contains 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
feat: 503 on api when not synced
Enable api before sync
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
This PR introduces two changes to improve API behavior during synchronization:
Return HTTP 503 When Not Synced
API endpoints now return a 503 status if Blockbook is unsynced, helping clients detect incomplete synchronization. Status of the Blockbook in the response was preserved.
Allow API Access Before Sync Completes
Added an
enableAPIBeforeSyncflag to optionally allow API access before full sync, useful in read-only scenarios.Changes:
Updated
jsonHandlerto return 503 if not synced.Added
enableAPIBeforeSyncflag for optional API access during sync.Impact:
Improves API flexibility for clients by providing better control over sync-dependent responses.