Web Development

If I were you, I would create an crontab function to change all the files in the directory of interest to read-only for security reasons. That way you have even more security.

yes

But in my setup i dont wana break current functionality,Then you know how programmer reacts.So i will be using what i said before

Then please explain why taking files that are not supposed to be executable and making them read only or read-write only will break current functionality?

What you are doing is good, but it is not enough to be fully secure.

We never know what kind of software programmer make,may be they need some time picture with different extension,or my be they need to upload documents pfd or video file.that's why i am accpecpting all file to be uploaded but not allowing certain file to run on my server.

Yes, we already know that.

You did not answer my question.

Ohh yes you are right,i didnt understand your question,yes what you are saying is also perfect.
Thx Neo.

I am not suggesting that you do one, or the other.

I am saying you should do both, (1) use your .htaccess directives and (2) create a crontab to insure all files are not executable. You might also consider changing ownership (chown) of the uploaded files in combination with chmod.

This is called "defense in depth" - using more than one security defense in case the other one fails.

Relying on only one security control creates a higher risk of compromise.