Skip to content

Keep the .opml suffix rule out of /.well-known/ - #51

Merged
pfefferle merged 1 commit into
mainfrom
fix/opml-suffix-well-known
Oct 15, 2026
Merged

pfefferle merged 1 commit into
mainfrom
fix/opml-suffix-well-known

Conversation

@pfefferle

Copy link
Copy Markdown
Owner

With SocialSpec active, /.well-known/following.opml was a 404. The .opml suffix rule of the plugin (^(.+?)\.opml$) comes before the rule of SocialSpec, so the request went to a page called .well-known/following, which does not exist.

The suffix rule now leaves everything under /.well-known/ alone: ^(?!\.well-known/)(.+?)\.opml$. Nothing there is a page, and the files belong to whoever serves them. That also means the well-known rules of the plugin no longer have to come before it.

The suffix rule is part of the check for stale rules now, so existing sites flush once after the update. Without that, a site that already has SocialSpec would keep the old rule, since nothing else about its rules changes.

The bug only shows with permalinks like /%year%/%monthnum%/%postname%/. With /%postname%/ WordPress checks that a page exists before it takes a page rule and moves on, so the test uses the date structure. Found by testing the SocialSpec hand-over from #47 on a local site.

@pfefferle
pfefferle merged commit b2da38f into main Oct 15, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant