Automattic / Automattic/wp-super-cache
Redirections not working for cached target pages
- Dominant language
- PHP
- Stars
- 436
- Forks
- 130
- Avg merge
- 15h 11m
- Merged PRs (30d)
- 10
Description
I use mod_rewrite caching on LiteSpeed. When page is redirected from URL A to B and B is in the cache, visiting URL A shows the page with URL A in the address bar and a HTTP status of 200, which is incorrect.
After clearing B from the cache, redirection takes place, the browser shows the page with URL B and 301 is returned.
This seems to occur whether a WordPress rewrite rule takes care of the redirection or the Redirection plugin.
This causes duplicate content and hurts SEO.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the LiteSpeed caching case with a WordPress rewrite rule or the Redirection plugin, using URL A redirecting to cached URL B. Compare responses before and after clearing B from the cache. Done means A still returns a 301 with B as the browser URL and does not serve B's cached page under A.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100