Running a load test against a webflux application, I experienced garbled requests under (moderately) heavy load: once in a while (i.e. 1 in 10 to 50.000 requests), the deserialization of the request body into the @RequestBody field yields wrong results.
In these bad results, field values are set to another field's value - but truncated to the lenght of the original field.
Garbeled Request (example):
The error only appears with authentication (basic auth) enabled.
I've created a test project to reproduce and better describe the error: