Sanitization
Example #1 Sanitizing and validating email addresses
<?php
$a = 'joe@example.org' ;
$b = 'bogus - at - example dot org' ;
$c = '(bogus@example.org)' ;
$sanitized_a = filter_var ( $a , FILTER_SANITIZE_EMAIL );
if ( filter_var ( $sanitized_a , FILTER_VALIDATE_EMAIL )) {
echo "This (a) sanitized email address is considered valid.\n" ;
}
$sanitized_b = filter_var ( $b , FILTER_SANITIZE_EMAIL );
if ( filter_var ( $sanitized_b , FILTER_VALIDATE_EMAIL )) {
echo "This sanitized email address is considered valid." ;
} else {
echo "This (b) sanitized email address is considered invalid.\n" ;
}
$sanitized_c = filter_var ( $c , FILTER_SANITIZE_EMAIL );
if ( filter_var ( $sanitized_c , FILTER_VALIDATE_EMAIL )) {
echo "This (c) sanitized email address is considered valid.\n" ;
echo "Before: $c \n" ;
echo "After: $sanitized_c \n" ;
}
?> 以上例程会输出：
This (a) sanitized email address is considered valid. This (b) sanitized email address is considered invalid. This (c) sanitized email address is considered valid. Before: (bogus@example.org) After: bogus@example.org
Example #2 Configuring a default filter
filter.default = full_special_chars
filter.default_flags = 0 用户评论:
[#1] Chris [2015-04-14 19:42:18]
While it may seem to be good practice to set the defaults in php.ini you should not assume that the end users server has the same settings as your server. Because of this you should not presume that default filtering will work out of the box for the end user.
You should ensure that all filters are declared at the site of use regardless of your own default settings. A move to a new host even for your own personal application may break due to different settings.
[#2] zeeshan dot karamat dot abbas at gmail dot com [2015-02-05 13:59:03]
If we omit using a filter then PHP by default puts a filter which is FILTER_DEFAULT which will use default filter. Now the question is what is a default filter. A default filter is unsafe_raw which will allow the unsafe raw data passed on to the server. This value is available in php.ini file. It is suggested that a developer should update this value inside php.ini file as under:
filter.default = full_special_chars
filter.default_flags = 0
Whereas in php.ini file above values are by default, set as under:
;filter.default = unsafe_raw
;filter.default_flags =
Above semicolons are commented out lines so surely one needs to remove those semicolons to apply the changes made. If we do not do above things then what will happen. In that case PHP will use default filter which would surely be FILTER_UNSAFE_RAW and one can see that unsafe raw data can then be passed onto server which can make the life a hacker easier.