New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple client response codes, currently the "best" success code is used #151

Closed
blast-hardcheese opened this Issue Jan 6, 2019 · 0 comments

Comments

1 participant
@blast-hardcheese
Copy link
Collaborator

blast-hardcheese commented Jan 6, 2019

This has been a significant difference between http4s and akka-http clients for a while.

An initial simplifying assumption was that most routes would only have one "successful" status code, and failure responses could be handled by the consumer.

This is undesirable due to the following points:

  • Error handling is potentially dangerous, if consumers forget to discardEntityBytes()
  • Mixing well typed responses with untyped responses does not give a good user experience

@blast-hardcheese blast-hardcheese created this issue from a note in scala (TODO) Jan 6, 2019

@blast-hardcheese blast-hardcheese moved this from TODO to In progress in scala Jan 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment