Repository navigation
Conversation
carson-codeigniter4
Bot
added
the
bug
gr8man
force-pushed
the
fix/siteurifactory-query-string-truncation
branch
from
November 12, 2026 10:08
1791a5d to
5f1419c
Compare
This branch has not been deployed
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.
Description
Fixes an issue where
SiteURIFactory::parseRequestURI()truncatedQUERY_STRINGto a single character ($query[1]) instead of using the parsed query string segment ($parts[1]) when using query-based routing (/?route?param=val). This preserves GET parameters in$_SERVER['QUERY_STRING'],$_GET, and$_REQUESTwhen the route path is provided via query string.Checklist: