> why are we making excuses for doing the obviously wrong thing? Sorry if I was unclear -- I wasn't advocating a mis-designed API, I am suggesting that HTTP is

> why are we making excuses for doing the obviously wrong thing? Sorry if I was unclear -- I wasn't advocating a mis-designed API, I am suggesting that HTTP is way more complicated and subtle than it needs to be for the purposes of remote APIs. I concede that providing enough information to know what is cacheable (and what the caching key is, etc) is justified complexity. But I think that the other 95% of semantics that "pure" REST demands you follow are pretty useless and pedantic.