WP Super Cache - add support for the Accept HTTP header #29456
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch allows WP Super Cache to ignore requests from clients that don't accept text/html. That allows WordPress to serve whatever content they require, which may well be JSON data.
This was prompted by the ActivityPub plugin which uses /author/X/ to deliver metadata about the author on a WordPress website to the Fediverse. If you search for a URL through the search box in Mastodon, it expects a JSON payload.
JSON requests are not cached by this plugin (yet?) but the vast majority of requests are text/html ones.
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
Apply patch.
Enable debugging in the plugin.
Go to your Mastodon account and search for a blog post on your blog.
Go to the debug output and filter it to search for your blog post.
Note that it says:
The content of your post should appear in the search box in your Mastodon client.