Ktor 2.3 ContentNegotiation plugin overriding user‑specified Content‑Type header
When using Ktor’s ContentNegotiation plugin to serialize a request body, the goal is to have any manually supplied Content-Type header remain unchanged in the outgoing request. However, the plugin’s documentation only states that it adds the Content-Type header when it is missing, leaving the precedence rule undefined when a header is already present. Observ
ktor