What we do today is a simple table page, and I use Bootstrap at the front end. no way. you don't know about art, and you only need to use other tools. BS is really beautiful and has rich plug-ins. it is something twitter engineers have made. all of us like good things ,... what we do today is a simple table page, and I use Bootstrap at the front end. no way. you don't know about art, and you only need to use other tools. BS is really beautiful and has rich plug-ins. it is something twitter engineers have made.
Good stuff is liked by everyone, but its compatibility with IE6-9 is almost 0. as you can understand, Internet Explorer basically does not use these browsers abroad. However, Internet Explorer still occupies a high market share in China. therefore, someone has developed a Bootstrap plug-in called BSIE. it is easy to use and despise IE. it seems that I am using CodeIgniter at the backend, it is an open source framework based on PHP. CI is the question of today, because CI only has xss_clean () for data filtering functions (). (I don't know if I am not familiar with it. In short, I didn't find any other filter functions) today's project involves receiving user data and then submitting database operations. no filtering for SQL statements makes this operation very risky. I think of the xss_clean () function of CI to filter SQL injection statements, two functions are not nested when data is filtered. in the CI/system/core/directory, find secure. in the php file, locate the declaration position of the xss_clean () function, and add such a paragraph at the end.
The PHP instance code is as follows:
$str = str_replace("_","x",$str); $str = str_replace("%","x",$str); $str = str_replace(""","x",$str); $str = str_replace("'","x",$str); $str = str_replace("select","x",$str); $str = str_replace("update","x",$str); $str = str_replace("insert","x",$str); $str = str_replace("set","x",$str); $str = str_replace("where","x",$str); $str = str_replace("from","x",$str); $str = str_replace("alert","x",$str); $str = str_replace("like","x",$str); return $str;
This almost avoids normal SQL injection.
Tutorial link:
Reprint at will ~ However, please keep the tutorial address★