Skip to content

fix: correct opt-in ServletEnv charset mismapping when parsing query strings - #481

Merged
chadlwilson merged 1 commit into
jruby:1.3-stablefrom
chadlwilson:1.3-servlet-env-tidy
Sep 8, 2026
Merged

fix: correct opt-in ServletEnv charset mismapping when parsing query strings#481
chadlwilson merged 1 commit into
jruby:1.3-stablefrom
chadlwilson:1.3-servlet-env-tidy

Conversation

@chadlwilson

@chadlwilson chadlwilson commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Also unifies the query parsing on Rack 2.2's proper validated parser and compares against DefaultEnv in specs.

This makes migration to Rack 3 much easier since we are re-using a version-appropriate parser.

This should be low risk, as the ServletEnv is opt-in, and to my knowledge doesn't seem frequently used (still marked as EXPERIMENTAL).

…y strings

Also unifies the query parsing on Rack 2.2's proper validated parser and compares against DefaultEnv.
@chadlwilson chadlwilson changed the title test: add spec to compare servlet env vs default env parsing of some edge cases fix: correct opt-in ServletEnv charset mismapping when parsing query strings Sep 8, 2026
@chadlwilson chadlwilson added this to the 1.3.1 milestone Sep 8, 2026
@chadlwilson
chadlwilson marked this pull request as ready for review September 8, 2026 09:46
@chadlwilson
chadlwilson merged commit b33c6f9 into jruby:1.3-stable Sep 8, 2026
12 checks passed
@chadlwilson
chadlwilson deleted the 1.3-servlet-env-tidy branch September 8, 2026 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant