Timeline for How to make "Everything you ever wanted to know about mod_rewrite" more visible
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2014 at 7:37 | comment | added | user9517 | @ShaneMadden: I have no real opinion on the matter I almost never go near a mod_rewrite question, they all look the same to me :) My answer is just based on what I (think) I know of the way things work and what we've done in the past for other similar issues. | |
| Feb 14, 2014 at 2:00 | comment | added | Shane Madden | Most of the questions which are asking how to write a rule are bad. But some of the ones needing debugging or dealing with unexpected configuration results, interactions with other modules that aren't well documented, etc. are good questions that would say we should keep. I'd propose a standard of "if you're asking for help writing mod_rewrite rules, instead of asking for help with unexpected behavior in the configuration you have (which should have taken at least some research), always close", and see where it gets us to have a slightly higher bar for these - thoughts? | |
| Feb 13, 2014 at 14:41 | vote | accept | ETL | ||
| Feb 13, 2014 at 7:51 | history | answered | user9517 | CC BY-SA 3.0 |