Repository navigation
fix: Prevent double Base64 encoding on retries - #69
Merged
Merged
Conversation
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.
A 429 retry encoded HTML fields a second time, sending Base64 text instead of the original HTML after decoding. Retries now skip encoding and reuse the already encoded body, preserving the existing in-place mutation behavior without cloning the request body. Encoding also tolerates null page and PDF options.
Adds regression coverage for identical retry payloads, in-place encoding, retry exhaustion, and non-retryable errors across PDF, screenshot, and template operations.
Validation performed before committing: all 57 tests passed, TypeScript checking passed, and ESLint passed for the changed files.