Home/ Questions/Q 493013
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T02:10:16+00:00

I’m taking a look at how to properly escape data that comes from the

  • 0

I’m taking a look at how to properly escape data that comes from the outside world before it gets used either for application control, storage, logic.. that kind of thing.

Obviously, with the magic quotes directive being deprecated shortly in php 5.3.0+, and removed in php6, this becomes more pressing, for anyone looking to upgrade and get into the new language features, while maintaining legacy code (don’t we love it..).

However, one thing that I haven’t seen is much discussion about theory/best practice with what to do once you have protected your data – for example, to store with or without slashes? I personally think keeping escaped data in the DB is a bad move, but want to hear discussion and read some case studies preferably..

Some links from the PHP manual just for reference:

PHP Manual – mysql_real_escape_string

PHP Manual – htmlspecialchars

etc etc.

Any tips?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Take a look at prepared statements. I know in mysql this works very well and is a secure form of getting data in to your databse. It has a few performance benefits too.

    http://dev.mysql.com/tech-resources/articles/4.1/prepared-statements.html

    I have some more resources if you are interested.

    Hope this is what you are looking for, tc.

    Edit:

    One thing i can add is using filters in combination with prepared statements. For example to check if the value is a sting you use FILTER_SANITIZE_STRING, or for the email you use FILTER_SANITIZE_EMAIL.

    This saves some amount of code and works very well. You can always check the data using your own methods afterwards, but there are a lot of filters you can use.

    • 0