I can't think of a meaningful CTA so my call to action is that you have to finally finish that side project you keep adding features to instead of just finishing.
I started making this video thinking it was a really hot take to return 200 OK for domain errors when using HTTP. But after digging into it, and more specifically reading HTTP status codes, it doesn't feel that controversial at all. I had a lot of fun digging into TCP and implementing a small piece of the HTTP protocol from scratch.
Thank you so much for taking the time to watch.
Timestamps
0:00 Intro
0:15 What is HTTP doing?
2:35 Explaining the domain
4:01 Handling errors in the server
5:33 Handling errors in the client
6:10 Example
7:32 Exit
Used in this video:
HTTP Client - httpie.io
TCP Implementation is Rust
Other code examples are Kotlin
Server Framework - ktor.io
Animations - motioncanvas.io
Негізгі бет Ғылым және технология Why I return HTTP '200 OK' for errors
Пікірлер: 77