This smells like an issue with maxQueryString, although I would have expected a different HTTP code.
maxQueryString