is there any way to just write plain text into the body of a

Question

is there any way to just write plain text into the body of a post request with the ktor client I have the following code ``` val content = identifier cdp 9055274 identifier cdp 9111757 identifier cdp 9135021 trimIndent val response = httpClient patch lt String gt url api rest v1 products header Authorization Bearer $ token accessToken contentType ContentType application vnd akeneo collection+json body = content ``` and it seems like regardless of what I m writing into the body the string TextContent ByteArrayContent the body is always serialized into json again

marstran · Answer

How is `httpClient` defined Maybe you can try with a client where the JSON feature isn t installed

df · Answer

of course that would work it just feels pretty bad to have two clients injected because one of the requests requires a non json body

df · Answer

``` fun httpClient objectMapper ObjectMapper settings AkeneoClientSettings HttpClient return HttpClient CIO defaultRequest url host = settings host protocol = URLProtocol HTTPS install JsonFeature serializer = JacksonSerializer objectMapper propertyNamingStrategy = PropertyNamingStrategy SNAKE CASE install Logging logger = Logger SIMPLE level = LogLevel ALL expectSuccess = false ```

df · Answer

that s the client definition

df · Answer

and tbh i don t really understand why it s serializing the body again The json feature should only kick in for application json content types

df · Answer

okay the last issue is explained by `value startsWith application amp amp value endsWith +json `

marstran · Answer

Right maybe you could set the Content Type header to `text plain`

df · Answer

unfortunately the server rejects requests if the wrong content type header is sent

marstran · Answer

Hmm how is that wrong if what you want is to send plain text content

df · Answer

gt Content type Equal to application vnd akeneo collection+json no other value allowed

df · Answer

because that s how it s documented

marstran · Answer

Ok

df · Answer

In their definition it seems to be some kind of json if you have one json object serialized per line

df · Answer

instead of having a proper json array

marstran · Answer

What exactly happens to the body when you send the string with that content type

df · Answer

```HttpClient CONTENT HEADERS HttpClient BODY Content Type application vnd akeneo collection+json HttpClient BODY START HttpClient identifier cdp 9055274 n identifier cdp 9111757 n identifier cdp 9135021 ```

df · Answer

okay what seems to work for now is the following ``` install JsonFeature serializer = JacksonSerializer objectMapper propertyNamingStrategy = PropertyNamingStrategy SNAKE CASE receiveContentTypeMatchers = listOf object ContentTypeMatcher override fun contains contentType ContentType Boolean return ContentType Application Json match contentType ```

df · Answer

i still think the design could be improved I don t see a reason why we can t have a OutgoingContent implementation that is not touched by any serializer sth like RawContent body ByteArray

Rustam Siniukov · Answer

did you try something like this ``` val response = httpClient patch lt String gt url api rest v1 products header Authorization Bearer $ token accessToken body = TextContent content ContentType application vnd akeneo collection+json ```

df · Answer

I did but it still applies the json serialization to the body

Rustam Siniukov · Answer

can you file an issue please <https youtrack jetbrains com newIssue project=KTOR amp draftId=25 3074517>

df · Answer

Of course Do you just want me to describe my use case I m not sure if one of the things I tried should have worked and is a bug or if everything works as intended and my use case is simply not covered

Rustam Siniukov · Answer

Example that I showed should not be intercepted by the serializer But please make sure that you don t set `ContentType` in header only in `TextContent` But I think that maybe it makes sense to skip serialization for all children of `OutgoingContent` Ticket will be helpful ti think about usecases and agree on the solution