StringUtils.uriDecode now correctly handles non-ASCII characters regardless of the presence of "%" encoding.

Previously, the method took two different paths depending on whether "%" was found, leading to incorrect handling of non-ASCII characters in the absence of "%" encoding.

This fix ensures that all characters, including non-ASCII ones, are properly decoded using the provided Charset, improving the method's reliability and consistency across all inputs.

This change addresses issues with decoding multibyte characters and ensures compatibility with a wider range of character encodings, enhancing the utility's overall functionality.

32360

Comment From: pivotal-cla

@dumbbelloper Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

Comment From: pivotal-cla

@dumbbelloper Thank you for signing the Contributor License Agreement!

Comment From: poutsma

Thank you for submitting a PR. Unfortunately, we have decided to take a different route in 646bd7f8933756802ae9f4e6450f0b2a23191304.