> I am getting the error a few times a day which must be frustrating for the > respective users, so I’m inclined to handle it. I could: > 1. Trap the error in a custom error page, look for a 400 status and clear > cookies there? > 2. Inspect the cookies before handing the request off to A4D? > Or is there a better way?
The better way would be for me to be more lenient with invalid cookies. I'd like to see what their cookies are so I can know what to allow. Regards, Aparajita _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
