The tests show that support for invalidation on Location and Content-Location is really poor. In my experience, developers don't count on this, and in some case it's counter-productive (because a POST response might want the client to use a cached resource, rather than invalidate).
Should we drop the requirement to invalidate these URLs?
The tests show that support for invalidation on
LocationandContent-Locationis really poor. In my experience, developers don't count on this, and in some case it's counter-productive (because aPOSTresponse might want the client to use a cached resource, rather than invalidate).Should we drop the requirement to invalidate these URLs?