I changed some full page loads into ajax requests and some features broke as a result. When researching I found that any cookies set in an ajax response are ignored. For example one of my action handlers adds this http response header: Set-Cookie: manage-p=U333; Expires=Thu, 01-Jan-1970 00:00:10 GMT As a result that cookie should be deleted on the client. It works fine for non-ajax request, but fails with a4j.
Bug? Known limitation?
It should be possible to parse the response header and set cookies on the client correctly when a response is received, right?