The application routing is not functioning correctly for any routes when query parameters are included in the URL. For example, accessing /example works as expected, but /example?param=value results in a failure or unexpected behavior. This issue prevents proper handling of query parameters across the entire application.
Steps to Reproduce
Define any route in the routing file (e.g., /example).
Start the application and access the route:
First without query parameters (e.g., GET /example): works as expected.
Then with query parameters (e.g., GET /example?param=value): fails.
Observe the behavior:
The route does not match or fails to respond properly when query parameters are present.
Expected Behavior
All routes should handle requests with query parameters without issue, matching the route path and processing the request appropriately.
Actual Behavior
Routes fail to respond or behave unexpectedly when query parameters are appended to the URL.
Stack Trace (if applicable)
Paste any stack traces, error logs, or traceback here. If they’re lengthy, consider using a code block (```) or attaching a file.
Environment Information
OS: Windows 11
Platform and Architecture: x64
Browser (if applicable): Chrome 131
Reproduction Details
Can you reliably reproduce the issue? [Yes/No]: Yes
Does the issue occur with older versions? If yes, please list tested versions:
Input and Output
Provide your input (e.g., code snippet, configuration) and the corresponding output or behavior. Input:
docker-compose up --build --watch --remove-orphans
The issue occurs globally across all routes in the application. This might indicate a configuration problem in the router or middleware that processes incoming requests.
Possible Solution
Investigate and ensure:
Query parameters are correctly parsed by the router.
No middleware is blocking or misconfiguring request handling for URLs with query parameters.
Describe the Bug
The application routing is not functioning correctly for any routes when query parameters are included in the URL. For example, accessing
/exampleworks as expected, but/example?param=valueresults in a failure or unexpected behavior. This issue prevents proper handling of query parameters across the entire application.Steps to Reproduce
/example).GET /example): works as expected.GET /example?param=value): fails.Expected Behavior
All routes should handle requests with query parameters without issue, matching the route path and processing the request appropriately.
Actual Behavior
Routes fail to respond or behave unexpectedly when query parameters are appended to the URL.
Stack Trace (if applicable)
Paste any stack traces, error logs, or traceback here. If they’re lengthy, consider using a code block (```) or attaching a file.
Environment Information
Reproduction Details
Input and Output
Provide your input (e.g., code snippet, configuration) and the corresponding output or behavior.
Input:
Output:
Screenshots or Media
Additional Context
The issue occurs globally across all routes in the application. This might indicate a configuration problem in the router or middleware that processes incoming requests.
Possible Solution
Investigate and ensure: