4 ms·
I don't see that anywhere in the post. All I saw was "GET"s shouldn't modify state and should be cacheable. That seems perfectly in line with the spec.
by drivebyacct2 14y ago
I don't see that anywhere in the post. All I saw was "GET"s shouldn't modify state and should be cacheable. That seems perfectly in line with the spec.
- jebblue 14y agoThe only problem I have with your comment is that REST is not specified, it's a style: http://en.wikipedia.org/wiki/Representational_state_transfer http://en.wikipedia.org/wiki/Representational_state_transfer
- Ramone 14y agoGET being cacheable/idempotent is part of the HTTP spec, and has nothing to do with REST: http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.9 http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13...
- drivebyacct2 14y agoI meant the HTTP spec which is where GETs specified.