The responseHandler should respect Content-Type headers

[taylorkline]

Howdy!

I believe the default responseHandler should be a little more intelligent to handle the response based on the content type header.

For example, in the default Go http package, you can see it is typical to return a response body of "404 page not found", "Unauthorized," etc. with non-200 responses.

It seems very counterintuitive that one must define a custom responseHandler for each and every endpoint to avoid RTK Query failing with PARSING_ERROR in some rather common use-cases.

[markerikson]

Oh hey this has been long merged and will be in 1.9.

[taylorkline]

@markerikson I changed the title, as there is now an option to respect Content-Type headers, but it is not the default.

[henkkasoft]

Thanks for solving this problem.
If you want to respect Content-Type for every endpoint, you can give responseHandler as parameter for fetchBaseQuery.

  baseQuery: fetchBaseQuery({
    baseUrl: '/my-api',
    responseHandler: 'content-type',
    ...
  }),

#2440 (comment)

[Ebugo]

Is handling the content type using the "responseHandler" still supported for each request?

I have a use case where I need to do this but it seems all response hadling happens at the base query now.