Skip to content
Hallway
0:00 / 0:00

#problemdetails#rfc7807#rfc9457

Stop returning custom error responses from your API. Do this instead.

Amichai Mantinband

60K subscribers • 7 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Amichai Mantinband
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

92K views2 years ago1 recommendation

Web developmentSoftware designHTTP, REST and GraphQLAPI design

Amichai Mantinband explains the Problem Details specification (RFC 9457) and demonstrates how to implement it for consistent API error handling in ASP.NET.

In today's video we'll cover the problem details specification (RFC 9457, previously RFC 7807). All HTTP APIs should use the problem details specification, as it defines a consistent, machine readable schema for error responses. So in this video we'll cover what the problem details specifications is, how to use it, and how easy it is to integrate it in your ASP.NET applications. Connect with me on 'em socials:  Twitter: twitter.com/amantinband LinkedIn: linkedin.com/in/amantinband/ GitHub: github.com/amantinband Check out all my courses on DomeTrain:  dometrain.com/author/amichai-mantinband Support the channel and get the source code: patreon.com/amantinband Thanks for watching, don't forget to like & comment & subscribe! ❤️ 💻

Why it's here

1 person recommends this

What people say. Recommended as an excellent guide on implementing modern, standardized error handling in ASP.NET Core APIs.

u/Quito246in r/dotnet • Recommends

On “Is there a modern best practice for return types?”

No the best practice is to have some global error handling and I would advise to use problem details construct. Here is a nice video about how to use problem details in modern web api. link to this video
46View on Reddit