…config Conflicts: CHANGES
when spliting get key value params on /=/ there should be a limit of 2 as the value itself could contain = so currently it, and data after it, will be lost with no limit: .../...?foo=bar=10&baz=boz will now parse as: foo => "bar=10", baz => "boz" previously it would parse as: foo => "bar", baz => "boz"
I was considering subclasses the Dancer::Response object in some tests. This would have caused very confusing failures.
Sometimes we already have a response object. This fix makes sure that we consistently recognize it as a response object and behave accordingly.
…params('fieldname') returns an arrayref of them