Release Notes › Web Agent Release Notes › Defects Fixed › Defects Fixed in 6.x QMR 5 › Change in Behavior Between 5.0.8 and 6.0.5 WA for AllowCacheHeaders Parameter (73604/80256)

Previous Topic: Web Agent Terminated Abnormally When Resolving Agent Names Under Heavy Loads (75072)

Next Topic: Custom page that posts to an FCC with invalid credentials causes the agent to redirect to login.fcc (69552/80254)
Change in Behavior Between 5.0.8 and 6.0.5 WA for AllowCacheHeaders Parameter (73604/80256)

Symptom:

The problem is that after logoff, a request for protected resource redirect8 is met with a 304 and causes an auth reject. User flow is attached as smaccess_UAT_log_cacheissue.txt in UAT.zip. In the customer's WA 5.0.8.02 UAT environment it gives a 200 response, but in the customer's WA 6.0.5.19 SIT environment it gives an undesired 304 response.

Solution:

This is no longer an issue.

STAR Issue: 17365359:1