The Meaning of HTTP Status Codes

preview_player
Показать описание
Follow for more Android & Kotlin tips 🙌
Рекомендации по теме
Комментарии
Автор

As a mobile developer you typically don't need to know most of the codes, apart from the fundamental ones like 200, 403 or 500. Most of it is abstracted away from you, and a mobile app usually can't do much about an error anyway, apart from presenting the user with an "oops!", "uh-oh" or "shit". Of course it's still good to have some broader understanding of the protocol up your sleeve, but you don't have to know it inside out. Eg. "further action needed" isn't really expected in a REST API (which is typically used by mobile apps), in which all operations are meant to be atomic and self-contaimed by design.

vibovitold
Автор

I've never seen 1xx status code from the server. Thanks!

alexnovikov
Автор

Basically almost 50% of the time when I edit a comment I get this

Helfirehydra
Автор

When I first learn about web programming I was confused with http and html, but luckily I understand it now. Because when I read the wikipedia page it says,
when you send a request, to the server it will respond to you with a http headers which is a string.

So, I was thinking the "header" here means the "html tag" that we need to parse. For example, if we have a
"user agent" such as an internet browser, it can parse the "http headers" given by the server. Until this day, I do not know whether this is the case or not.

abacaabaca
Автор

Should I learn spring boot or something else...
Please guide....

jatin_