URI query parse errors during parameter extraction throw an unhandled IllegalUriException #1043
Labels
3 - in progress
Someone is working on this ticket
help wanted
Identifies issues that the core team will likely not have time to work on
t:routing
Issues related to the routing DSL
Milestone
If parsing the URI query fails during parameter extraction, the resulting
IllegalUriException
is unhandled, leading to (by default) a 500 being sent back to the client, rather than a 400 as might be expected.For example, if we
curl -i http://localhost:8080/?a==
the following route (appropriately bound):We see in the logs:
The client receives:
The text was updated successfully, but these errors were encountered: