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
The mockserver is configured to authenticate the requests and for invalid requests it'll send the response body like below with 403 status code and Content-Type set as application/json
{
"result" : "Forbidden"
}
When we call the API through emissary, it overrides the Content-Type as text/plain from application/json
text/plain is the default. You can set the content_type for custom error responses on either a Module or a Mapping. I'm not sure if that spec is available on the AuthService but it might be something to try.
Content-Type from Auth service is overwritten in error response
To Reproduce
Setup AuthService
The mockserver is configured to authenticate the requests and for invalid requests it'll send the response body like below with 403 status code and Content-Type set as application/json
When we call the API through emissary, it overrides the Content-Type as text/plain from application/json
Expected behavior
The auth failure response should retain original Content-Type
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: