In league with the future's latest activity
- 2mo 路
-
Public路
-
ruby.social
Great work...bud ! 馃檪
You must have shown great stamena.
I鈥檒l just let myself out and leaf 馃崄 you alone.
鈥ee more
Great work...bud ! 馃檪
You must have shown great stamena.
I鈥檒l just let myself out and leaf 馃崄 you alone.
See less
Great work...bud ! 馃檪
You must have shown great stamena.
I鈥檒l just let myself out and leaf 馃崄 you alone.
Great work...bud ! 馃檪
You must have shown great stamena.
I鈥檒l just let myself out and leaf 馃崄 you alone.
鈥ee more
See less
- 1y 路
-
Public路
-
ruby.social
422 is saying that the content from the client was bad.
I鈥檓 thinking where the server didn鈥檛 raise an exception but something in its internal state didn鈥檛 add up. There are times when a distinction is made between those circumstances. It should be a 500.
This can happen when an error occurs in code that knows nothing about the web and the web layer fails to recognise the situation and doesn鈥檛 transform it to an appropriate http status code.
鈥ee more
422 is saying that the content from the client was bad.
I鈥檓 thinking where the server didn鈥檛 raise an exception but something in its internal state didn鈥檛 add up. There are times when a distinction is made between those circumstances. It should be a 500.
This can happen when an error occurs in code that knows nothing about the web and the web layer fails to recognise the situation and doesn鈥檛 transform it to an appropriate http status code.
See less
422 is saying that the content from the client was bad.
I鈥檓 thinking where the server didn鈥檛 raise an exception but something in its internal state didn鈥檛 add up. There are times when a distinction is made between those circumstances. It should be a 500.
This can happen when an error occurs in code that knows nothing about the web and the web layer fails to recognise the situation and doesn鈥檛 transform it to an appropriate http status code.
422 is saying that the content from the client was bad.
I鈥檓 thinking where the server didn鈥檛 raise an exception but something in its internal state didn鈥檛 add up. There are times when a distinction is made between those circumstances. It should be a 500.
This can happen when an error occurs in code that knows nothing about the web and the web layer fails to recognise the situation and doesn鈥檛 transform it to an appropriate http status code.
鈥ee more
See less
- 1y 路
-
Public路
-
ruby.social
@nateberkopec because 4xx implies a client error?
But it might not be a client error so should it be a 5xx?
Or, wait! The system worked perfectly and the client request was fine but something in the internal operations is defined add an error. Is that a 5xx or should I stuff it into a 200 payload?
People are all of lazy, uninformed and have differing priorities.
I think it would be nice to use the status codes consistently. Yet here we are!
鈥ee more
@nateberkopec because 4xx implies a client error?
But it might not be a client error so should it be a 5xx?
Or, wait! The system worked perfectly and the client request was fine but something in the internal operations is defined add an error. Is that a 5xx or should I stuff it into a 200 payload?
People are all of lazy, uninformed and have differing priorities.
I think it would be nice to use the status codes consistently. Yet here we are!
See less
@nateberkopec because 4xx implies a client error?
But it might not be a client error so should it be a 5xx?
Or, wait! The system worked perfectly and the client request was fine but something in the internal operations is defined add an error. Is that a 5xx or should I stuff it into a 200 payload?
People are all of lazy, uninformed and have differing priorities.
I think it would be nice to use the status codes consistently. Yet here we are!
@nateberkopec because 4xx implies a client error?
But it might not be a client error so should it be a 5xx?
Or, wait! The system worked perfectly and the client request was fine but something in the internal operations is defined add an error. Is that a 5xx or should I stuff it into a 200 payload?
People are all of lazy, uninformed and have differing priorities.
I think it would be nice to use the status codes consistently. Yet here we are!