Quarkus or the spring compatibility layer I'm using with it is injecting content-type headers into responses that already have content-type headers set and its really annoying.
Looks like its the spring compatability layer and that does not suprise me at all.
Definitely the spring ExceptionHandler ended up writing some quarkus handlers instead which lead to more issues with one of the extensions installed but that has been resolved.
Spring continues to be awful at letting you decide your own fate but I guess that's what comes with the level of 'magic' that it comes with.