I think we are dramatic agreement?
HTTPS = breaking caching.
User Authentication = returning different results for per-resource queries, which is RESTful.
HTTPS = breaking caching.
User Authentication = returning different results for per-resource queries, which is RESTful.
The exception is there for practical reasons and it doesn't satisfy REST's constraints nor benefits from REST's properties.
Either way, my point's been exhausted, so, I'll shut up now ;)