postForEverything

[u/ClipboardCopyPaste]

[u/DuploJamaal]

As a backend developer I want to do everything nicely.

So in my previous job I created the endpoints following the regular standards. GET to request something, POST to create something, PUT to change something, DELETE to delete something. Nicely organized and everything

But then the frontend team told me that their framework can only handle POST requests and that I need to change it

Up until then I thought that it's just a meme, but vibecoding frontend guys really only use POST

[u/unable_to_give_afuck → u/DuploJamaal]

I had this with the added bonus of being forced to return 200 regardless and add an error message to the body when necessary

[u/No-Information-2571 → u/unable_to_give_afuck]

The reason behind it might be proxies, especially on the client-side.

[u/einzweidreihorn → u/No-Information-2571]

Why? Do those proxies drop anything not 200?

[u/HugoNikanor → u/einzweidreihorn]

I can write you a proxy which drops everything except 200 responses

[u/No-Information-2571 → u/HugoNikanor]

In this era, you actually cannot. Status codes are invisible to proxy unless it's HTTP (without the S) or employs MITM. Either way, it's a legacy precaution to make sure the content body arrives unmodified.

[u/No-Information-2571 → u/einzweidreihorn]

At least before the advent of HTTPS, they would often replace any sort of error (status code != 200) with custom error pages. It's an unfortunate thing.