[HTTPCLIENT-1746] URLEncodedUtils.parse(String, CharSet) in 4.4 causes an NPE on null input and is not backward compatible

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.5.3, 5.0 Alpha2
• Assignee: Unassigned
• Reporter: Steve Briskin
• Created: 27/May/16 17:55
• Updated: 26/Jan/17 19:30
• Resolved: 03/Jun/16 19:38

Description

In 4.2 and 4.3, URLEncodedUtils.parse(String, CharSet) returns an empty List for a null String input.

In 4.4, URLEncodedUtils.parse(null, Charset.forName("UTF-8")) throws an NullPointerException.

For the sake of API backward compatibility, parse(String, CharSet) should return an empty list.

Note that parse(String, CharSet, char...) does the null check and returns an empty list. I think parse(String, CharSet) should have the same behavior.

Issue Links

• is duplicated by: HTTPCLIENT-1761 Missing null check in parse method
• is duplicated by: HTTPCLIENT-1807 NullPointerException in URLEncodedUtils.parse(String, Charset)