What is a common mistake when working with HTTP methods and status codes?

A common mistake with HTTP methods and status codes is returning 200 for every outcome or using methods inconsistently hides failure semantics and leads to fragile client code. The safer approach is to design and test the behavior explicitly rather than assuming the platform or dependency will handle it automatically.