问题
Is it worth changing my code to be "more portable" and able to deal with the horror of magic quotes, or should I just make sure that it's always off via a .htaccess file?
if (get_magic_quotes_gpc()) {
$var = stripslashes($_POST['var']);
} else {
$var = $_POST['var'];
}
Versus
php_flag magic_quotes_gpc off
回答1:
Don't accommodate both situations. Two code paths = twice the headaches, plus there's a good chance you'll slip up and forget to handle both situations somewhere.
I used to check if magic quotes were on or off, and if they were on, undo their magic (as others in the thread have suggested). The problem with this is, you're changing the configured environment (no matter how stupid) that another programmer may expect.
These days I write code as though magic quotes are off, and in my main include/bootstrap/always-runs file I check if magic quotes are on or off. If they're on I throw an Exception that explains why this is a bad thing, and provide instructions on how they can be turned off.
This approach allows you to code to a single behavior, encourages other folks using your code to configure their servers correctly (magic quotes is going away in PHP 6), and if someone really needs magic quotes on they can handle your exception and take their lives into their own hands.
回答2:
I would check the setting using get_magic_quotes_gpc() and do a big noisy exit with error. In the error inform the administrator of the proper setting.
回答3:
I would make sure it's off if that's possible (requires access to .htaccess or apache configuration). It's better to avoid it altogether than stripping it's behavior which requires more resources and is prone to bugs.
If disabling it is not an option, your example code could be useful for the input superglobals ($_GET,$_POST,...) but make sure not to apply it on data arriving from sources other than those supergloabls. Such misuse is pretty common.
Just make sure that when turning magic_quotes_gpc() off to have a proper escaping mechanism in place to protect you from SQL inkection (such as mysql_real_escape_string() or PDO prepared statements). You can read more on SQL injection prevention - here.
回答4:
On more of a side note php 6 won't be supporting them anymore. So writting the code for them off may be beneficial in the future.
来源：https://stackoverflow.com/questions/370292/work-around-magic-quotes-or-just-make-sure-theyre-off