I have to wonder if this happens because GET and POST are not super obvious names, like imagine if they were instead READ and WRITE endpoints?
I don’t think anyone would make the same mistake with the linux filesystem stuff, like you cat /proc/cpuinfo and it erases the information about the processor.
i am still convincing lazy “senior” engs to stop using GET endpoints to do stuff. get to “/db_offline” should not set the fucking db offline.
I have to wonder if this happens because GET and POST are not super obvious names, like imagine if they were instead READ and WRITE endpoints?
I don’t think anyone would make the same mistake with the linux filesystem stuff, like you
cat /proc/cpuinfoand it erases the information about the processor.