Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    These suffer from the same goofy escaping rules as URLEncoder. Commented Aug 28, 2014 at 22:53
  • 4
    not sure they have the problem. they differentiate for instance "+" or "%20" to escape " " (form param or path param) which URLEncoder doesn't. Commented Apr 16, 2015 at 11:01
  • 1
    This worked for me I just replaced call to URLEncoder() to call to UrlEscapers.urlFragmentEscaper() and it worked, not clear if I should be using UrlEscapers.urlPathSegmentEscaper() instead. Commented Nov 2, 2015 at 12:18
  • 2
    Actually it didnt work for me because unlike URLEncoder it doesnt encode '+' it leaves it alone, server decodes '+' as space whereas if I use URLEncoder '+'s are converted to %2B and correctly decoded back to + Commented Nov 2, 2015 at 17:52
  • 2
    Link update: UrlEscapers Commented Jun 15, 2017 at 9:50