RESTEASY-578 introduces a TCK regression. The spec assumes CacheControl to be a dumb property holder with no logic. Therefore, every property set programatically should appear in the Cache header although it may not make sense (e.g. "public, no-cache, no-store, max-age=60"). It is up to the application developer to set the properties correctly. The TCK assumes every property set on CacheControl to appear in the header.

CacheControl does not support "public" property for some reason. Note that "public" and "private" directives are not complementary, thus it is not correct to use the "public" directive every time the private property is set to false (This is what RESTEasy currently does).

I suggest to rollback RESTEASY-578 and fix the issue by:

• changing CacheControlDelegate so that it never sets the "public" directive
• optionally introduce a RESTEasy-specific CacheControl subclass (e.g. ExtendedCacheControl) with support for the public directive.