You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Jsoup.connect(url) with an url http://xxx/api/test/%2B32123, but Jsoup is making the request as http://xxx/api/test/+32123, causing it to be interpreted as 32123 by the backend.
I am experiencing a similar case that probably has the same cause as this issue. We are passing in a URL of the form: http://xxx/api/123+456. The URLBuilder decodes the URL path: URI uri = new URI(..., decodePart(this.u.getPath()), ...);
In 1.15.3 the plus sign wasn't decoded to a space and the URL still works fine.
Also, encoding the plus sign as %2B works as the decoding will decode it to a plus sign. (But I don't think that's a proper solution.)
Thanks for the report and apologies for the issue! Have fixed this by reverting to the previous behavior of not encoding supplied paths, other than normalizing to ASCII.
I'm using
Jsoup.connect(url)
with an urlhttp://xxx/api/test/%2B32123
, but Jsoup is making the request ashttp://xxx/api/test/+32123
, causing it to be interpreted as32123
by the backend.This looks related to #1914, #1902, #1936 and #1928.
Downgrading to 1.15.3 works.
The text was updated successfully, but these errors were encountered: