Skip to content

Conversation

@hdonnay
Copy link
Member

@hdonnay hdonnay commented Jul 10, 2025

The previous way of doing this was (purposefully! there was a test!) inserting invalid characters into values. This does the percent-encoding in one spot, instead of doing a second pass that can introduce disallowed characters.

See-also: quay/claircore#1582

@hdonnay hdonnay requested a review from crozzy July 10, 2025 21:26
Copy link
Contributor

@crozzy crozzy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just one nit, took me a while to page back in char encoding semantics...

The previous way of doing this was (purposefully! there was a test!)
inserting invalid characters into values. This does the percent-encoding
in one spot, instead of doing a second pass that can introduce
disallowed characters.

See-also: quay/claircore#1582
Signed-off-by: Hank Donnay <[email protected]>
@hdonnay hdonnay force-pushed the bug/baggage-encoding branch from 90c8d7a to 08a589d Compare July 11, 2025 17:42
@hdonnay hdonnay merged commit 08a589d into quay:main Jul 11, 2025
3 checks passed
@hdonnay hdonnay deleted the bug/baggage-encoding branch July 11, 2025 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants