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
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
At the end of message handler you call Request.CreateResponse. Is it possible that you actually use Request.CreateErrorResponse, or make it at least configurable.
This is important because I use other message handlers made by myself and they treat your response message as actual data (instead of threating them as errors).
I know this is small change in code but probably breaking one, but making strategy about returning response configurable would be great
The text was updated successfully, but these errors were encountered:
You can override that method and use CreateErrorResponse instead. Both CreateResponse and CreateErrorResponse have a return type of HttpResponseMessage.
@VladoP Are there specific side effects that you are expecting CreateErrorResponse to provide? What are some differences in the HttpResponseMessage that you expect to see?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the end of message handler you call Request.CreateResponse. Is it possible that you actually use Request.CreateErrorResponse, or make it at least configurable.
This is important because I use other message handlers made by myself and they treat your response message as actual data (instead of threating them as errors).
I know this is small change in code but probably breaking one, but making strategy about returning response configurable would be great
The text was updated successfully, but these errors were encountered: