Skip to content
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

Merged
merged 3 commits into from
Apr 13, 2021

Conversation

EdwardAngert
Copy link
Contributor

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:

  • copy edit

Post Launch

Do not remove - To be completed by the docs team upon merge:

@EdwardAngert EdwardAngert self-assigned this Feb 23, 2021
@pantheondocs
Copy link

pantheondocs commented Feb 23, 2021

Lighthouse Audit Results:

Description Live pr-6272 Difference
Performance Score 63 64 1
Best Practice Score 86 86 0
SEO Score 96 96 0
Accessibility Score 100 100 0

Lighthouse Audit Reports:

Preview Environment

@EdwardAngert EdwardAngert removed their assignment Feb 23, 2021
@EdwardAngert EdwardAngert requested a review from a team February 23, 2021 18:46
@davidneedham
Copy link
Contributor

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.

@EdwardAngert
Copy link
Contributor Author

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
brb with a followup commit

@EdwardAngert EdwardAngert self-assigned this Feb 23, 2021
@@ -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.
Copy link
Contributor Author

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?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@EdwardAngert EdwardAngert removed their assignment Feb 23, 2021
@carolyn-shannon carolyn-shannon self-assigned this Mar 1, 2021
@carolyn-shannon carolyn-shannon added Type: New Content Request for or PR containing new content to existing page Source: Pantheor Contribution from within Pantheon, unspecified team labels Mar 1, 2021
Copy link
Contributor

@carolyn-shannon carolyn-shannon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@carolyn-shannon carolyn-shannon merged commit 52e3e9b into main Apr 13, 2021
@carolyn-shannon carolyn-shannon deleted the 6247-wp-ban branch April 13, 2021 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Pantheor Contribution from within Pantheon, unspecified team Type: New Content Request for or PR containing new content to existing page
Projects
None yet
Development

Successfully merging this pull request may close these issues.

wp ban plugin known issue
4 participants