mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 00:48:54 +00:00
Typo fix. (thanks, cynic!).
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@39339 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
cf0805bfe0
commit
ebb77d1e3d
2 changed files with 2 additions and 2 deletions
|
@ -438,7 +438,7 @@ if (!ereg('^[^./][^/]*$', $userfile))
|
|||
developer who is trying to debug a script, indicating such things
|
||||
as the function or file that failed, the PHP file it failed in,
|
||||
and the line number which the failure occured in. This is all
|
||||
information that can be exploited. It not uncommon for a php
|
||||
information that can be exploited. It is not uncommon for a php
|
||||
developer to use show_source(), highlight_string(), or
|
||||
highlight_file() as a debugging measure, but in a live site, this
|
||||
can expose hidden variables, unchecked syntax, and other dangerous
|
||||
|
|
|
@ -438,7 +438,7 @@ if (!ereg('^[^./][^/]*$', $userfile))
|
|||
developer who is trying to debug a script, indicating such things
|
||||
as the function or file that failed, the PHP file it failed in,
|
||||
and the line number which the failure occured in. This is all
|
||||
information that can be exploited. It not uncommon for a php
|
||||
information that can be exploited. It is not uncommon for a php
|
||||
developer to use show_source(), highlight_string(), or
|
||||
highlight_file() as a debugging measure, but in a live site, this
|
||||
can expose hidden variables, unchecked syntax, and other dangerous
|
||||
|
|
Loading…
Reference in a new issue