Valid htaccess rule causes 404 after upgrade to 3.3.1
|Reported by:||ronnieg||Owned by:|
|Component:||Rewrite Rules||Keywords:||needs-patch needs-testing|
On 2/18/2012, I upgraded WP from 3.2.1 to 3.3.1. on www.denverhomevalue.com. I later noticed that Google webmaster tools started reporting 404 errors on lots of pages that were fine before. WP was still returning the proper pages and content, not my custom 404 page, so the issue was not readily apparent except in WMT reports. Running http header response checkers confirmed 404 responses, despite good contents being returned.
Deleting sections of the htaccess file until the problem went away, the issue was isolated to two rules meant to escape following rewrite rules on certain urls:
RewriteRule ^city(.*) - [L] RewriteRule ^areas(.*) - [L]
These were the same family of urls that started returning 404s after 3.3.1 upgrade. These rules were in place since 12/5/2011, with WP 3.2.1 and never caused a problem.
I was able to revert a backup of the site to 3.2.1, on the same exact server environment, and confirm that these same valid htaccess rewrite rules were not a problem in that release.
Change History (6)
19 months ago
- Keywords needs-patch reporter-feedback added
- Severity changed from critical to normal