Currently, many permission systems are controlled based on URL routing (module actions), such as thinkphp. The access path is localhostthinkphpindex. phpindexindex can also be accessed Based on the file path, such as localhostthinkphpTplIndexindex. h... many permission systems are controlled based on URL routing (module/Action) such as thinkphp. The access path is http: // localhost/thinkphp/index. php/index can also access the file path such as http: // localhost/thinkphp/Tpl/Index/index.html, which directly displays the source code of index.html! How can I disable access without parsing it? Or other protection measures
Reply content:
Many permission systems are controlled based on URL routing (module/Action) such as thinkphp. The access path is http: // localhost/thinkphp/index. php/index can also access the file path such as http: // localhost/thinkphp/Tpl/Index/index.html, which directly displays the source code of index.html! How can I disable access without parsing it? Or other protection measures
Put outside the Web directory
Http://doc.thinkphp1.cn/manual/deploy_directory.html
Create a public folder and put the entry file in the public folder.
If you have an upload or images folder, put it under puclib.
Modify the directory definition in the entry file.
// Define the Application directory define ('app _ path', '../Application/'); // introduce the ThinkPHP entry file require '../ThinkPHP. php ';