Romain

Hello @flopana, It seems that you are describing an issue that is not related to this one. Can you please open a new issue?

Hello all! I want to suggest an alternative proposal to solve that use case. It is more or less in line with the proposal of @ddtmachado, but narrowed. I propose...

@maxlerebourg Have you tried to add the 'Content-Type` middleware as it is recommended in the v3 migration guide? (see https://doc.traefik.io/traefik/v3.0/migration/v2-to-v3/#content-type-auto-detection).

Hello @maxlerebourg, Unfortunately, I tried to reproduce the problem without success. I used this minimal docker-compose: ```yml version: '3.8' services: traefik: image: traefik:v3.0.0-beta2 command: - --api.insecure - --entrypoints.web.address=:80 - --providers.docker...

Hello @peter-englmaier, Thanks for sharing this proposal! Nonetheless, it looks like this use case is covered with the current configuration, as it is possible to separate concerns thanks to routing....

Hello @peter-englmaier, Sorry for the late answer. I'm unsure of your use case. You have shared a manifest for a TCP middleware and I assumed it was for TCP routing,...

If you are already using the IngressRoute provider to configure a few middleware on Ingresses, you are already using the IngressRoute spec/provider, you could use it as well to define...

Hello @peter-englmaier, Thanks for the clarification. What do you think of exposing the routes on a dedicated entry point with limited access only to your IP, while on the regular...

Hello @JHK, Thanks for reporting this. How did you extract the trace context from the request context? Could you please share with us that part of the plugin implementation?

@JHK Could you try with OTel library as in the ForwardAuth middleware:https://github.com/traefik/traefik/blob/fc897f6756a3a6ae9e3acd604a71ae4f4a675245/pkg/middlewares/auth/forward.go#L137-L148