Well the params object also contains POST data, so I think there's a higher risk of spaces and new lines showing up in values, especially for apps that accept free flowing text. There are definitely a few tradeoffs to consider, which I guess is why this wasn't implemented before!