Repository navigation
Preserve Repeater response bytes in Hex, downloads and saved projects - #28
Merged
Merged
Conversation
This was referenced Sep 30, 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
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.
What changes
Repeater previously converted response bodies into UTF-8 text before Hex could inspect them: bytes
00 ff 80 41became replacement characters. It now retains the original wire response and inspection body separately through asynchronous completion, API snapshots, per-tab history and project persistence.Validation
Limits
Text views remain readable interpretations. The binary views/downloads preserve the selected bytes. Past-send history is session-only, and saving current response bytes increases project size. Brotli/zstd decoding and immediate socket cancellation remain separate work.
Owner: Bikebrainz.
All eight CI jobs passed on bb3c029: https://github.com/Bikebrainz/Nullock/actions/runs/36656946504