|
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
#1 |
Kids are great, Appu. You can teach them to hate the things you hate and they practically raise themselves now-a-days, you know, with the internet and all
|
htaccess--one file or many?
Haven't been able to find an answer to this question during much surfing tonight/day.
RewriteEngine on starts the process, then conditions and rule, then the "L" concludes the redirection instructions--this I think I understand. Without an "L" at the end of the rule, will the server go on to a next set of conditions/rules in the same htaccess file, or would this cause some sort of loop or breakdown (ie. list of urls with access to images followed by redirect for all others, then specific urls that are to be denied all access to files)? Is only one "RewriteEngine on" directive necessary, or should it precede each new set of conditions? Or should all Rewrite condition/rule sets be in separate htaccess files? Thanks for your patience with yet another damn htaccess question! Lee |
![]() |
![]() |
![]() |
#2 |
No offence Apu, but when they were handing out religions you must have been out taking a whizz
|
Oy! I'm kinda stumped on this one, but I don't *think* that the [L] terminates anything but the current set of RewriteCond's.
Generally though, if I have multiple sets of conditions I need to work with I separate them into multiple htaccess files in the corresponding directory. htaccess is hierarchical, meaning that the rules you set up are inherited as you go deeper within the website. So you can "funnel down" your rules as you go deeper into the site.
__________________
Please Re-Read The Rules For Sig Files |
![]() |
![]() |
![]() |
#3 |
Kids are great, Appu. You can teach them to hate the things you hate and they practically raise themselves now-a-days, you know, with the internet and all
|
Thanks for replying--I'd about decided that my question was either too simple or too complex to warrant an answer.
Through trial and error, I think I've figured out that the "L" doesn't stop the whole thing, as you said. But, also as you said, a long list of directives in one file might become quite confusing. To me, anyway. So I think your "one command list per htaccess file" suggestion is the way to go. Thanks again--much appreciated! Lee |
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | Rate This Thread |
|
|