Unfortunately, there’s not much that can be done on our side, as the mwai_session cookie is necessary to gather data about user sessions. If your caching process is too aggressive, it might immediately stop working as soon as this cookie is set.

If you’re unable to configure anything on the caching side, you can go into AI Engine and disable the Insights module. This will effectively prevent the cookie from being set, but you won’t be able to use the Insights feature.

This command fetches only the HTTP headers of a GET request to your website and filters out lines showing:

• Any cookie being set by the server.
• Any proxy cache information.

If the server sets a session cookie it will indicate that the response was not served from a cache.

curl -sIXGET https://meowapps.com/ | grep -i 'proxy-cache\|cookie'

No cache due to Cookie output:

set-cookie: mwai_session_id=684a58b5b1c12; path=/; secure; HttpOnly
set-cookie: __cf_bm=9MOQ46X3Q0MZGymHFTsD90VBq.D5kDKzZpYFlIol5t4-1749704501-1.0.1.1-Z7osBm_caHusXbJsIKuefF.QitmB3HRrOUpmaQFvSkgvzGRihR_b16dIctzaJHbMwRSlekcKbs3Ty7F4sn85iYxDMS.dLadexgKxqI0I61I; path=/; expires=Thu, 12-Jun-25 05:31:41 GMT; domain=.meowapps.com; HttpOnly; Secure; SameSite=None

If you have a HIT header, it means the request was served from the cache instead of going all the way to the backend server.