php/yii2
1
0
Fork 0
mirror of https://github.com/yiisoft/yii2.git synced 2025-11-13 12:49:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #12309 from Mak-Di/patch-2

Browse Source 
Fix typo
This commit is contained in:
Dmitry Naumenko
2016-08-25 09:20:47 +03:00
committed by GitHub
parent 05bfe18611 383de6f051
commit f038477d08
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/guide/security-best-practices.md
View File

@@ -202,7 +202,7 @@ In debug mode Yii shows quite verbose errors which are certainly helpful for dev
verbose errors are handy for attacker as well since these could reveal database structure, configuration values and verbose errors are handy for attacker as well since these could reveal database structure, configuration values and
parts of your code. Never run production applications with `YII_DEBUG` set to `true` in your `index.php`. parts of your code. Never run production applications with `YII_DEBUG` set to `true` in your `index.php`.
You should never enalble Gii at production. It could be used to get information about database structure, code and to You should never enable Gii at production. It could be used to get information about database structure, code and to
simply rewrite code with what's generated by Gii. simply rewrite code with what's generated by Gii.
Debug toolbar should be avoided at production unless really necessary. It exposes all the application and config Debug toolbar should be avoided at production unless really necessary. It exposes all the application and config