


The tp framework prevents entering the background by typing the address after logging in
<?php namespace AdminController; use ThinkController; class IndexController extends Controller { public function index(){ $this->display(); } public function login(){ $username = I('username'); $password = I('password'); $user = D('User'); $res = $user->where(array('username'=>$username))->find(); // dump($res);die; if(!$res || md5($password) != $res['password']){ $this->error('用户名或密码错误'); }else{ session('username',$res['username']); session('id',$res['id']); session('create_time',$res['create_time']); //dump(session());die; $this->redirect('/Admin/Main/index'); //跳转到后台管理 } } //清空 public function loginout(){ session(null); //dump(session()); $this->redirect('/Admin/Index/index'); } }
<?php //后台页面的控制器 namespace AdminController; use ThinkController; class MainController extends Controller { public function index(){ $this->display(); } }
How should I judge? I can’t enter the login page or backend system at will by typing the address in the address bar
Reply content:
<?php namespace AdminController; use ThinkController; class IndexController extends Controller { public function index(){ $this->display(); } public function login(){ $username = I('username'); $password = I('password'); $user = D('User'); $res = $user->where(array('username'=>$username))->find(); // dump($res);die; if(!$res || md5($password) != $res['password']){ $this->error('用户名或密码错误'); }else{ session('username',$res['username']); session('id',$res['id']); session('create_time',$res['create_time']); //dump(session());die; $this->redirect('/Admin/Main/index'); //跳转到后台管理 } } //清空 public function loginout(){ session(null); //dump(session()); $this->redirect('/Admin/Index/index'); } } <?php //后台页面的控制器 namespace AdminController; use ThinkController; class MainController extends Controller { public function index(){ $this->display(); } }
How should I judge? I can’t enter the login page or backend system at will by typing the address in the address bar
In Index In the __initialize method of the controller, determine whether your session has been assigned a value. There is no jump to login.
For specific reference
TP framework __initialize method
It seems that you don’t want others to enter the background, that is, the login page is not allowed to enter, right? If you can try configuring accessible modules. If you want to judge whether the person is logged in or not, then you need to judge the session. I will give you some information and you can try it. If you can, deploy it to the server settings and do not set it locally. Access is prohibited. The module
3.2对模块的访问是自动判断的,所以通常情况下无需配置模块列表即可访问,但可以配置禁止访问的模块列表(用于被其他模块调用或者不开放访问),默认配置中是禁止访问Common模块和Runtime模块(Runtime目录是默认的运行时目录),我们可以增加其他的禁止访问模块列表: // 设置禁止访问的模块列表 'MODULE_DENY_LIST' => array('Common','Runtime','Api'), 设置后,Api模块不能通过URL直接访问,事实上,可能我们只是在该模块下面放置一些公共的接口文件,因此都是内部调用即可。 设置访问列表 如果你的应用下面模块比较少,还可以设置允许访问列表和默认模块,这样可以简化默认模块的URL访问。 ***'MODULE_ALLOW_LIST' => array('Home','Admin','User'),*** 'DEFAULT_MODULE' => 'Home', 设置之后,除了Home、Admin和User模块之外的模块都不能被直接访问,并且Home模块是默认访问模块(可以不出现在URL地址)。
is not allowed to enter the login page. How to log in to the backend system?
TP can write a base class (
BaseController), and then all controllers that need verification should Inherit this base class.
isAuth()) { $this->redirectToLogin(); } } private function isAuth() { //验证是否登录 } private function redirectToLogin() { //跳转到登录页面 } }
For example, there is an administrator controller in the background
class AdminController extends BaseController { public function __construct() { parent::__construct(); } }This is TP's approach, but frameworks like symfony come with their own verification classes, which can easily perform http verification, accesstoken verification and Customized verification method.It is impossible not to allow access to the login page, otherwise your business staff will not be able to log in. If your front-end and back-end are the same user system, then verify whether the front-end login user has the permission to enter the back-end. Just display the login page normally without logging in. As long as you don't let the search engine grab your back-end login address
Write a public function to determine whether it is logged in
function isLogin(){ if(I('session.uid')){ return true; }else{ return false; } }Then write it in the __initialize method of the background controller
if(!isLogin()){ $this->redirect('/login') //重定向到登录页 }

ThesecrettokeepingaPHP-poweredwebsiterunningsmoothlyunderheavyloadinvolvesseveralkeystrategies:1)ImplementopcodecachingwithOPcachetoreducescriptexecutiontime,2)UsedatabasequerycachingwithRedistolessendatabaseload,3)LeverageCDNslikeCloudflareforservin

You should care about DependencyInjection(DI) because it makes your code clearer and easier to maintain. 1) DI makes it more modular by decoupling classes, 2) improves the convenience of testing and code flexibility, 3) Use DI containers to manage complex dependencies, but pay attention to performance impact and circular dependencies, 4) The best practice is to rely on abstract interfaces to achieve loose coupling.

Yes,optimizingaPHPapplicationispossibleandessential.1)ImplementcachingusingAPCutoreducedatabaseload.2)Optimizedatabaseswithindexing,efficientqueries,andconnectionpooling.3)Enhancecodewithbuilt-infunctions,avoidingglobalvariables,andusingopcodecaching

ThekeystrategiestosignificantlyboostPHPapplicationperformanceare:1)UseopcodecachinglikeOPcachetoreduceexecutiontime,2)Optimizedatabaseinteractionswithpreparedstatementsandproperindexing,3)ConfigurewebserverslikeNginxwithPHP-FPMforbetterperformance,4)

APHPDependencyInjectionContainerisatoolthatmanagesclassdependencies,enhancingcodemodularity,testability,andmaintainability.Itactsasacentralhubforcreatingandinjectingdependencies,thusreducingtightcouplingandeasingunittesting.

Select DependencyInjection (DI) for large applications, ServiceLocator is suitable for small projects or prototypes. 1) DI improves the testability and modularity of the code through constructor injection. 2) ServiceLocator obtains services through center registration, which is convenient but may lead to an increase in code coupling.

PHPapplicationscanbeoptimizedforspeedandefficiencyby:1)enablingopcacheinphp.ini,2)usingpreparedstatementswithPDOfordatabasequeries,3)replacingloopswitharray_filterandarray_mapfordataprocessing,4)configuringNginxasareverseproxy,5)implementingcachingwi

PHPemailvalidationinvolvesthreesteps:1)Formatvalidationusingregularexpressionstochecktheemailformat;2)DNSvalidationtoensurethedomainhasavalidMXrecord;3)SMTPvalidation,themostthoroughmethod,whichchecksifthemailboxexistsbyconnectingtotheSMTPserver.Impl


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

SublimeText3 Chinese version
Chinese version, very easy to use

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Zend Studio 13.0.1
Powerful PHP integrated development environment

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool
