Post by @gabboman@gabboman.xyz

gabboman the wafrn dev

@gabboman@gabboman.xyz 17 hr. ago

I apologise for this early wafrn design decision

The meme of shapes into the bucket

Each shape is a http verb (put, patch, head, delete). User is puting data (a circle wich would fit better on PUT) in square POST — The meme of shapes into the bucket Each shape is a http verb (put, patch, head, delete). User is puting data (a circle wich would fit better on PUT) in square POST

0 Boosts

0 Likes

0x4d6165 (Julie)

@0x4d6165@transfem.social 16 hr. ago

@gabboman@gabboman.xyz wait aren't you supposed to POST new entities?

gabboman the wafrn dev

@gabboman@gabboman.xyz 16 hr. ago

@0x4d6165@transfem.social

Those wouod be put i think but idk

0x4d6165 (Julie)

@0x4d6165@transfem.social 16 hr. ago

@gabboman@gabboman.xyz seems like POST is only for creation whereas PUT is for creation or updating. https://www.rfc-editor.org/info/rfc2616/#section-9.5

Kevin Marks

@kevinmarks.com@bsky.brid.gy 35 min. ago

It's more that with POST the server decides what URL the resource is at, with PUT the client does. PUT is tricky for round tripping as GET, modify, PUT means the client has to fully parse the object it's replacing, and is easier to accidentally write a race condition that way.

1 more reply