When reviewing tests code, so often the developer is not aware of the WebClient#getOptions()#setThrowExceptionOnFailingStatusCode(false) trick and that implies the use of ugly try/catch.

To ease the discovery of such options, the method should be only one-level depth.