HTTP PUT - Response Codes Explained
In today's software development world, APIs have become the norm of communication between any two systems. Communication between two microservices, communication between frontend and backend of an application, etc.
When APIs are all the buzz, in the ...
tech-hustler.hashnode.dev3 min read
As you wrote, there’s regularly some debate. That’s why it’s also useful to have an authoritative source of truth to confirm what a server should do if we want to make it follow the standards.
And that’s where RFC 7231 (section 4.3.4) comes in to confirm what you wrote:
src: tools.ietf.org/html/rfc7231
Every time such discussion starts in a design doc review or code review, following RFC is very helpful. We need very strong reason and special edge cases to pick non standard behaviors.