I'm crashing due to a header that comes back in a response

java.lang.IllegalArgumentException: Unexpected char 0x41c at 74 in Content-Disposition value:  inline; filename="7326f70a-1b88-4ff8-afc8-5f52190c7052b7179b07fcb968827a_Мала.jpg"

I wrote this interceptor and I set it as a network interceptor, but I still get the same crash (as if the interceptor doesn't even get applied). Can anyone point me in the right direction?

private val REMOVE_HEADER_INTERCEPTOR = Interceptor { chain ->
  val originalResponse = chain.proceed(chain.request())
  originalResponse.newBuilder()
    .removeHeader("Content-Disposition")
    .build()
}

oof. i figured they weren't supported, but itd still allow me to remove those headers. hopefully i can find some docs to show my server team that non ascii chars shouldn't be used in headers.

okhttp is throwing before your intercepter gets run

Thanks for the resources. This is definitely a TIL. Thank you @ephemient!

This isn’t a request or a response header, but a multipart header?

I'm trying to just load an image with coil and @Colin White helped me debug to figure out that this was the issue. So I'm not really sure if this is a multipart header (not sure what that is). It would be really nice if it was lenient so I can intercept and rewrite a broken server like I do with my servers broken caching impl.

is that part of a multipart header? I expected it's just a normal response header from the question