5 ms·
I thought the same, but apparently the article is correct https://www.ietf.org/rfc/rfc2616.txt https://www.ietf.org/rfc/rfc2616.txt
by nighthawk454 3y ago
I thought the same, but apparently the article is correct
https://www.ietf.org/rfc/rfc2616.txt https://www.ietf.org/rfc/rfc2616.txt
- sibit 3y agoInteresting. I guess I've been going off of RFC 7231 > The PUT method requests that the state of the target resource be created or replaced with the state defined by the representation enclosed in the request message payload. https://www.ietf.org/rfc/rfc7231.txt https://www.ietf.org/rfc/rfc7231.txt
- blowski 3y agoMy rule of thumb: if you know the ID of the resource you’re creating, it’s a PUT. If the system generates the ID, then it’s a POST.
- treve 3y agoMore generally the URI instead of the ID.
- SgtBastard 3y agoThe I in URI, stands for Identifier...