ReadMeFeed / Community knowledge

#content-negotiation

Real questions. Useful conversations. Find the people who know your stack.

Article0 replies2,131 followingPosted 21 Jan 2026, 20:38 UTC126.2K views4,697 votes

Kraken JS Content Negotiation Per-Route API Format Selection

When Accept headers cause unexpected Kraken API responses, explicit renderer registration and route-level negotiation prevent 406 errors and format mismatches.

Community & Careers · Blog

krakenjs

Tasadduq Burneyowner

Started21 Jan 2026, 20:38 UTC

Level 38Owner35,775 rep points

Community & Careers

Article0 replies3,384 followingPosted 11 Sept 2025, 22:19 UTC69.3K views3,898 votes

Serving JSON and XML from One Ktor Endpoint with Content Negotiation

Ktor's ContentNegotiation plugin lets one route serve JSON and XML based on the client's Accept header. Here's how to configure it, when to override it per route, and how to test the negotiation contract.

Community & Careers · Blog

content-negotiation rest-api

ktor

Community & Careers

Article1 reply1 comment4,255 followingPosted 10 Sept 2026, 11:39 UTC41.5K views3,912 votes

owner commented

Ktor ContentNegotiation: A Practical Guide to JSON Serialization with kotlinx.serialization

Ktor’s ContentNegotiation plugin with kotlinx.serialization turns JSON handling into a declarative line of code. This blog walks through setup, a concrete example, performance trade‑offs, common pitfalls, and a quick benchmark test.

Community & Careers · Blog

content-negotiation kotlinx-serialization

ktor

Community & Careers

Article1 reply1 comment2,121 followingPosted 08 Sept 2025, 03:38 UTC91.5K views3,903 votes

helper commented

Zero‑Boilerplate JSON in Ktor with kotlinx.serialization

Learn how Ktor’s ContentNegotiation plugin, paired with kotlinx.serialization, automatically handles JSON request and response bodies so you can focus on business logic.

Community & Careers · Blog

serialization content-negotiation

ktor

Community & Careers

Question1 answer4,861 followingPosted 29 Apr 2025, 12:07 UTC130.7K views3,149 votes

owner answered

Ktor Client and kotlinx.serialization JSON: Typed Response Deserialization Across Client Engines

When Ktor's client ContentNegotiation plugin is paired with kotlinx.serialization JSON, typed response bodies are deserialized using the installed Json instance and reified type parameters. The integration boundary appears straightforward for a single engine, but the research notes that engine behavior and coroutine suspension are not uniform. Across CIO, Ok

Community & Careers · Editorial question

content-negotiation kotlinx-serialization http-client

Community & Careers

Question1 answer620 followingPosted 06 Sept 2024, 19:13 UTC65.4K views615 votes

owner answered

Ktor ContentNegotiation converter trade-off: kotlinx.serialization strictness versus Jackson unknown-field defaults

When configuring ContentNegotiation in a small Ktor application, the choice between kotlinx.serialization and Jackson affects how the service behaves when clients send JSON properties the server model does not declare. The goal is to select a converter that supports a rolling upgrade without rejecting requests containing added fields from updated clients. ko

Community & Careers · Editorial question

content-negotiation kotlinx-serialization

ktor

Community & Careers

Question1 answer3,942 followingPosted 11 Nov 2023, 02:14 UTC48.3K views4,906 votes

helper answered

MissingRequestContent error & large body buffering in Ktor

MissingRequestContent error & large body buffering in Ktor Ktor buffers the entire request body by default when call.receive is used. For payloads larger than a few megabytes this can lead to significant memory spikes and, if the body is empty but a Content-Type is declared, the framework throws the MissingRequestContent error before any application logi

Community & Careers · Editorial question

content-negotiation request-body

ktor

Community & Careers

Question1 answer693 followingPosted 19 Aug 2020, 23:09 UTC37K views2,992 votes

owner answered

Ktor Server ↔ Ktor Client: Content Negotiation Interoperability

Ktor Server ↔ Ktor Client: Content Negotiation Interoperability When a Ktor Server and a Ktor Client are deployed together, both sides must agree on how JSON payloads are serialized. The current ContentNegotiation plug‑in allows separate registration of kotlinx.serialization or gson , but the API does not provide a single, unified configuration path. This fr

Community & Careers · Editorial question

content-negotiation websocket json-serializer