2 ms·
isnt there a caching and idempotency implication ? from what I had learned long back - GET, PUT, DELETE are supposed to be idempotent [1] POST is not - so poss
by sandGorgon 13y ago
isnt there a caching and idempotency implication ? from what I had learned long back - GET, PUT, DELETE are supposed to be idempotent [1]
POST is not - so possibly it's considered safer to use among muggles.
I also think PUT and DELETE are not cacheable, while POST is (given the right set of headers).
caveat: I might be completely wrong about my interpretation.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html