Comment by quanticle

    The "true spirit" of REST, to me, is that there's a certain set of things 
    you can do when creating an API that will let you re-use the huge amount of 
    HTTP middleware that's been written and get correct (and useful!) semantics 
    from it. Caches (browser-, edge-, and server-side-), load balancers, 
    forward- and reverse-proxies, application-layer firewalls, etc. will all 
    "just work" for your software if you do REST correctly, and won't have any 
    weird edge-cases.

Doesn't that assume that the middleware also implements REST correctly? As the article points out, there are all too many HTTP libraries that only support GET and POST, not the more "esoteric" verbs like PUT and DELETE.