When client does not specify its charset in Content-Type header of a request, a server use default charset(ISO-8859-1). Therefore parameters of a request is encoded in other than default charset without telling what charset they use , the params can't be decoded properly via wrap-params middleware. And i see that a complete accurate auto-detecting charset is almost impossible, IMO, it might be good that a user have a chance to use their own function to detect charset when wrap-param middleware process decode params.
When client does not specify its charset in Content-Type header of a request, a server use default charset(ISO-8859-1). Therefore parameters of a request is encoded in other than default charset without telling what charset they use , the params can't be decoded properly via wrap-params middleware. And i see that a complete accurate auto-detecting charset is almost impossible, IMO, it might be good that a user have a chance to use their own function to detect charset when wrap-param middleware process decode params.