Repository navigation
fix(ai): reject non-url-safe record cursor characters - #319
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.
Refs #264. Reject standard Base64
+and/before passing a record cursor to the URL-safe decoder. The canonical round-trip already rejects both, so the accepted wire format andREQUEST_FIELD_INVALIDremain unchanged. Keep the existing framing, padding and canonical checks. All record cursor callers share this decoder.Python 3.15.2 baseline warning is emitted for the slash variant of the existing malformed-alphabet test. Local CPython 3.11.18: 39 state-range tests passed, configured Ruff and diff checks passed. Python 3.15 is pending natural CI. This change does not alter I/O behavior or close #264.