You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with several APIs where the server does not send a Content-Type header, especially for error responses. This forces me to use a custom http.Client implementation that injects this header before the response is parsed. I'm wondering if it would make sense to do this by default when only one Content-Type is defined for a response?
The text was updated successfully, but these errors were encountered:
I'm working with several APIs where the server does not send a Content-Type header, especially for error responses. This forces me to use a custom
http.Client
implementation that injects this header before the response is parsed. I'm wondering if it would make sense to do this by default when only one Content-Type is defined for a response?The text was updated successfully, but these errors were encountered: