Brian Clozel ad007caebc Refine multipart converter registration in HttpMessageConverters ...

As of #33894, `HttpMessageConverters` auto-detects converters and use
custom-provided ones to configure a collection of converters for the
client or the server.
Right now the multipart converter is only configured if core converters
(JSON, XML...) are configured/detected. We do not reuse the base
converters (resource, string, byte array) for the multipart converter
as it applies different encoding defaults (ISO for the main ones, UTF-8
for multipart).

This commit refines the configuration to not only include the multipart
converter when core converters are present, but also if any other
converter was configured.

Closes gh-35203

2025-07-15 14:45:28 +02:00

..

src

Refine multipart converter registration in HttpMessageConverters

2025-07-15 14:45:28 +02:00

spring-web.gradle

Merge branch '6.2.x'

2025-06-29 17:42:35 +02:00