Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Programming \ Defensive programming in PHP     - Apache Spark1.1.0 deployment and development environment to build (Server)

- extundelete: the Linux-based open source data recovery tools (Linux)

- MySQL separation Amoeba achieve literacy (Database)

- configuration ssh without password under Linux (Linux)

- Java recognize simple codes (Programming)

- how to quickly find a file on Linux system (Linux)

- Ubuntu 14.04 install the NVIDIA driver + CUDA + MATLAB (Linux)

- What is a logical partition management LVM, how to use in Ubuntu (Linux)

- Macro Analysis Performance: PHP Performance Analysis and Experiment (Programming)

- How to make GRub instead of the default Ubuntu software center (Linux)

- Some security configuration of Linux systems (Linux)

- How to update the Linux kernel to improve system performance (Linux)

- OpenGL ES 3.0 vertex buffer (Programming)

- Basic Operation Linux files and directories (Linux)

- JITwatch installation under Linux (Linux)

- Incremental garbage collection mechanism for Ruby 2.2 (Programming)

- Linux iostat command example explanation (Linux)

- Django Signals from practice to source code analysis (Programming)

- Encrypted with GnuPG signature to verify the authenticity and integrity of downloaded file (Linux)

- Linux NIC configuration (Linux)

 
         
  Defensive programming in PHP
     
  Add Date : 2018-11-21      
         
         
         
  Fei Nage dynamic inverse law:

Go wrong, will go wrong eventually - at the worst possible moment.

 

Defensive programming (Defensive Programming) What does it mean

Defensive programming, simply put, it is when programming purposefully predict possible points of failure. It aimed at those issues that may occur prior to the occurrence of solving them. You see the problem, right? Prediction unexpected things do have inherent difficulty of forecasting when you want something unexpected and even more difficult to solve it on several times.

Let's look at a few practical examples.



 

Conditional statements

This is easily one of the most defensive programming, and is the easiest place to meet. In many cases, programming with PHP you will not need "else".

Suppose you need to write a function and a conditional statement. Here, you only need to use three conditional statements for your specific variables as follows:

if ($ var == a) {}
elseif ($ var == b) {}
elseif ($ var == c) {}
There is no other possibility, you say, and continue code code. But let us pause here. I know you know there are no other possibilities of. And I believe you. But sometimes (unpredictable) happens. We forget some things. We check for errors. We eventually reuse some code, beyond the original predetermined range. Suddenly we have sometimes silent disclose errors or error status, because we do not use catch. Using the else block. When using the switch to use the default. Use them to return or recording errors, so that you know what happened (If this happens then). Although it will use more than two lines of code, but you can not predict some of the things that occurs, it is worth it.

 

I can not believe that user input

Have you ever heard of this statement? Most programmers heard. This is a little vague, popular speak, of course. But it is the truth. You should never believe that user input. This does not mean you assume that all users are crazy hackers who use some carefully designed command to destroy your application. No need for paranoia. However, you should assume that you do not know your code, they do not know what you need to fill in parameters, or parameters should be long. They do not know what size or what file types can be uploaded (even if the application had told them). Occasionally, they would be a machine or a hacker and they want to run the script on their input, sometimes even after landing in the input. How do you know that you can trust or authentication codes can provide a secure fortress before the user input?

Answer: never.

You would never believe user input. If you trust user input, then you will never have a break. do you understand? So you always have to evaluate input, make sure you are dealing with the data to be stored in the database, especially when you want it displayed, or the use of appropriate technology. So - I do not believe the input, even if not from the local user input - input validation will always be your friend. See Survive the Deep End: PHP Security validation library and use it.

 

Suppose your code

Do not assume anything. If the first two relating to teach us anything, it is that we should not make any assumptions. As a programmer, especially after working on a project for too long, we started to do a lot of assumptions. We assume that the user knows some of the things we know. Is not necessarily the technical details, the program can also be functional details. We assume that the user knows how much can file since. . . We already know. Or they know that in order for the message script. . . It does not work, they do not know any of these things. This seems to be more of a front end of the work, it is clear that you still have to deal in the back-end user behavior and user input, it is worthwhile to think.

Many programmers will do another amazing is that we assume for significant functional properties of our functions, classes, or other piece of code at any time. A defensive programmer will carefully consider not only using a general document to describe the function is doing - they will also write down their input parameters, use cases, or any other similar things to make any assumptions . Because we are all human, we had a period of time will forget something. Finally, we are also likely to face other people to maintain, extend or replace our code. If nothing else, recall, programming takes place in a world full of technological change in. If your application can still be used for several years, you may upgrade PHP version and lose some function, or some of your own need to change the code inside have interaction between components. These are very difficult to predict, so good comments and documentation is very important.
     
         
         
         
  More:      
 
- How to Install Apache on Linux servers (Server)
- Oracle Shared Server Configuration (Database)
- PostgreSQL log classification and management (Database)
- The Objects in JavaScript (Programming)
- Android Studio utility plug organize, create sharp artifact (Programming)
- Java enum use (Programming)
- Oracle 12CIN-memory in table spaces (Database)
- Linux file compression and file system packaged with instructions (Linux)
- VMware clone Linux find eth0 (Linux)
- Ubuntu 14.04 LTS to compile the source code Android4.4.2 (Linux)
- Log analysis is done with Grafana Elasticsearch (Server)
- How to configure Proftpd server on Fedora 22 (Server)
- RT-11SJ run at ambient PDP-11 MACRO-11 assembly (Programming)
- Profile Linux users login shell and login to read (Linux)
- Ubuntu install VMware Workstation 11 tutorials at 14.04 / 14.10 (Linux)
- CentOS 6 Install Xen4.2 Virtualization Practice (Linux)
- Linux system boot process ARM platforms (Linux)
- OpenGL ES 3.0 vertex buffer (Programming)
- Cross server / client backup command: rsync use (Server)
- Linux kernel panic (because glibc result) Repair (Linux)
     
           
     
  CopyRight 2002-2022 newfreesoft.com, All Rights Reserved.