Timeline for .htaccess RedirectMatch 301 issue
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2015 at 15:24 | comment | added | MrWhite | The RedirectMatch directive matches against a root-relative (starting with a slash) URL-path, not the absolute URL, so the above directive would not have done anything - it would not have matched. Even it did match, it wouldn't have redirected to the /wordpress folder - so there must have been something else going on here. Incidentally, 301 redirects are cached by the browser, so it's quite possible you were seeing a cached response. It's often best to first test with 302 (temporary) redirects for this reason. | |
| Dec 10, 2015 at 12:19 | history | edited | MrWhite | CC BY-SA 3.0 | Formatting |
| Mar 15, 2013 at 0:03 | history | edited | Simon Hayter | tag | |
| Feb 22, 2013 at 22:44 | history | edited | Simon Hayter | CC BY-SA 3.0 | replaced example non-working link with a good old <pre> |
| Mar 7, 2011 at 3:20 | vote | accept | Steve | ||
| Mar 7, 2011 at 3:20 | answer | added | Steve | timeline score: 2 | |
| Mar 7, 2011 at 3:06 | answer | added | Steve | timeline score: 0 | |
| Mar 1, 2011 at 9:49 | answer | added | Kissaki | timeline score: 0 | |
| Mar 1, 2011 at 4:17 | history | asked | Steve | CC BY-SA 2.5 |