Karen Asmarian

@davidtothdev could you share more details about your use case? Or, if possible, create an example repo, where the issue is reproducible. That would help a lot.

Looks like the issue is that Spring adds the `Content-Type`, `Transfer-Encoding` and `Date` headers as well as the default response body after the internal filters have finished processing the request...

I think it can be helpful to make the right filtering decision if it had more context. As you mentioned, at least to know if it's a request/response and what's...

We could have a look, yes, but I can't tell you any timeline promises. If you have time and desire, please feel free to suggest the changes, and we'll review...

You have a point here, as the response is copied in `LocalResponse` classes, the allocation of memory is doubled. We could use the `max-body-size` to enforce a limit, let's say,...

After some internal discussions with the team, it doesn't look like we'll be able to address this fully without changing how Logbook works entirely. The problem is that Logbook buffers...

Ah, @whiskeysierra is right, the buffering will be used only if the request is eligible for the logging. Do you think it would help if we mention that `logbook.write.max-body-size` only...

Hi @HaniBikdeli, please help me reproduce the issue. I followed the steps you listed, but can see the logs. Could you create a repo where this is reproducible and share...

Looks like if you add ``` .metrics(true) { uriTagValue: String -> uriTagValue } ``` to the [logbookNettyServerCustomizer](https://github.com/grassehh/spring-boot-3-tracing-coroutine/blob/main/app/src/main/kotlin/com/grassehh/app/configuration/ServerConfiguration.kt#L24), as was suggested in the initial issue you created for reactor-netty (https://github.com/reactor/reactor-netty/issues/2850), you'll...

@grassehh did I get it right, that the issue with the baggage item is resolved with Spring Framework 6.1.2-SNAPSHOT? Did it also resolve the problem with the traceId being different...