Description of problem: The cache-control directive, when specified on the UI, gets too much encoding when being set as a header. This means that it's not useful at the current state when more than one parameter for the cache-control is set: For instance, the string "no-cache, max-age=0, must-revalidate, no-store" becomes this header: Cache-Control:no-cache%2C+max-age%3D0%2C+must-revalidate%2C+no-store
https://github.com/gatein/gatein-portal/pull/917 was merged in upstream.
This issue had an improper target milestone CR3 due to release plan changes after CR2. Actually, it was fixed in Portal 6.2.0.ER6
The Cache-Control of the Response Headers now looks like "no-cache, max-age=0, must-revalidate, no-store". Verified in er09.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.