You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arguably, POST /key is not an entirely correct use of POST -- since the insertion operation (after #1 gets fixed) is idempotent arguably it should be PUT. However, I'm not sure whether this will confuse students (then again, they'll have to deal with PUT when they move on to "real-world" APIs anyway).
The text was updated successfully, but these errors were encountered:
PUT is definitely valid. POST is also valid but way less specific about the nature of the API. I think we could easily have both methods as long as there was a short explanation in the docs.
Arguably,
POST /key
is not an entirely correct use ofPOST
-- since the insertion operation (after #1 gets fixed) is idempotent arguably it should bePUT
. However, I'm not sure whether this will confuse students (then again, they'll have to deal withPUT
when they move on to "real-world" APIs anyway).The text was updated successfully, but these errors were encountered: