-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
list wp-ban as known issue due to 200-level responses #6272
Conversation
The copy is all factually correct but potentially missing the most important part. Because the request is 200, the global CDN could save that "you are blocked" page and serves it up to anyone else visiting that page. |
well that's not good at all |
@@ -1050,7 +1050,7 @@ ___ | |||
|
|||
<ReviewDate date="2021-02-23" /> | |||
|
|||
**Issue:** This plugin works on the platform but might not perform the function that users expect. WP-Ban returns a [200-level](/metrics#available-metrics) response code to banned IPs. These responses are cached and count towards Site Visits. | |||
**Issue:** WP-Ban returns a [200-level](/metrics#available-metrics) response code to banned IPs. These responses are cached and count towards Site Visits. In addition, the Pantheon [Global CDN](/global-cdn) may cache the result as successful, leading future visitors to think they've also been banned. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davidneedham - I added the cache note and removed the "well, it does still work" to dissuade users. Does that seem like it's better described?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Closes: #6247
Summary
WordPress Plugins and Themes with Known Issues - WP-Ban bans traffic to uncached pages, but it uses a 200 status code when returning those pages which causes the platform to cache the banned message for future users and count the traffic as a Site Visit.
Remaining Work
The following changes still need to be completed:
Post Launch
Do not remove - To be completed by the docs team upon merge: