You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently this plugin responds with a 200 status code for ban messages. This can cause caching systems to cache the page for users who are not banned, resulting in them seeing the ban message even though they are not banned. I would recommend responding with a 401 or 403 status code (or making this configurable.
For example, Pantheon's CDN will cache the banned message if a banned visitor accesses a page before other visitors causing the ban message to be shown to all users until that page falls out of the cache.
The text was updated successfully, but these errors were encountered:
Currently this plugin responds with a 200 status code for ban messages. This can cause caching systems to cache the page for users who are not banned, resulting in them seeing the ban message even though they are not banned. I would recommend responding with a 401 or 403 status code (or making this configurable.
For example, Pantheon's CDN will cache the banned message if a banned visitor accesses a page before other visitors causing the ban message to be shown to all users until that page falls out of the cache.
The text was updated successfully, but these errors were encountered: