`org.jsoup.Connection.Response.statusMessage()` returns `null`

[ppalaga]

This seems to be a regression in 1.21.1 against 1.20.1

[ppalaga]

You may want to check for some failing tests in quarkiverse/quarkus-antora#131

[jhy]

Hi -- in 1.21.1 we switched to using the HttpClient by default if available, over the previous default of HttpUrlConnection (#2340).

On review, the HttpClient impl (added in 1.19.1, #2257) misses setting the status message.

[jhy]

Well, the reason that I missed it is that the HttpClient doesn't have a status message, because HTTP/2 doesn't have one.

Need to think on this one if we should have a map of the common ones. Maybe just OK, Not Found, Error.

[ppalaga]

Good to know, I can actually live without status messages.

[jhy]

OK, I have added a minimal set of "OK", "Not Found", and "Error {statusCode}", just to make sure this method doesn't return a null, and to provide something at least marginally useful in a log line.

Would be good if you can verify against your test cases using a snapshot install, to make sure there are no other blockers.

[ppalaga]

Would be good if you can verify against your test cases using a snapshot install, to make sure there are no other blockers.

Even 1.21.1 works for me once I stopped relying on status messages.

Thanks a lot for your fast feedback @jhy!