My Filter inspects multi-part posts and potentially rejects them before they reach the actual endpoint (jersey, outside my control). Allowing casual multipart parsing (as shown in answer below) solves the exception: Unable to process parts as no multi-part configuration has been provided
A custom CommonsMultipartResolver or the existing resolver work without the error when the property is set. However, the content gets lost after accessing / resolving it.
I could use a custom CommonsMultipartResolver and deal with the lost information as suggested here: Resolving multipart/form-data request in spring filter. However, I am hoping for a cleaner solution adding the filter, without copying the request.