Hello Mark,
Mainly to allow caching through a caching proxy to the web server.
I have been able to get the caching server(s) configured to ignore this cookie, however the cookie does still get generated, and would rather it wasn’t generated if possible.
I suppose one alternative option may be to allow changing of the cookie domain path?
e.g. cookies.mydomain.com or static.mydomain.com so Wordfence can handle the cookies through a secondary alias domain, through would be able to ignore caching and allowing the rest of the site(s) to be cached more without forcibly ignoring the cookie?
I hope the above makes sense?
Thanks,
Bison Grid.