This post was last edited by Xiongmzh on 2013-11-20 15:24:09
My group: A B C
Default group: A
B.xxx.com, point to Group B,. htaccess as follows;
Options +followsymlinks
rewriteengine onrewritecond%{request_filename}!-drewritecond%{request_ FILENAME}!-frewriterule ^ (. *) $ index.php/b/$1 [qsa,pt,l]
Now, when accessing http://b.xxx.com/, it is the index method in the Indexaction controller under the A packet (but the URL in the address bar has not changed), for help, has not figured out what the principle, Why not perform the indexaction controller under Group B
Reply to discussion (solution)
Well, I know what's going on, and I didn't do it at all. Rewriterule ^ (. *) $ index.php/b/$1 [qsa,pt,l]
But when I visit Http://b.xxx.com/index is also performing a group of indexaction, which I can't think of.
When accessing Http://b.xxx.com/index, the server is exported in the portal file, and no redirect_status is found, indicating that no rewrite succeeded
http://b.xxx.com/
Http://b.xxx.com/Index
Http://b.xxx.com/Index/index
Http://b.xxx.com/Index/index.html
These did not rewrite the success, the first unsuccessful, but also understandable, but the No. 234 one is baffled, what is more incomprehensible is that the following can rewrite success:
Http://b.xxx.com/Other
Http://b.xxx.com/Other/index
Http://b.xxx.com/Other/index.html