SQLite's unrestricted authorization protocol and supports most standard SQL 92 statements, I believe that more and more people will use this database.
The combination of PHP and SQLite is just like the combination of ASP and ACCESS back then. ACCESS can be maliciously downloaded, and SQLite is also not spared, because SQLite is also a binary file, and as long as WEB can access it, it can be downloaded.
ACCESS can use some tricks to prevent users from downloading, and SQLite can do it too. Here are some commonly used methods to prevent SQLite from being downloaded
1. Place SQLite in a place that cannot be accessed by WEB.
Some virtual hosts generally provide a separate directory for users to place some files that they do not want to be downloaded or accessed, so it is safe to place them in this directory. Ilia also offers another approach, which is somewhat similar to ACCESS practices.
It is to change the SQLite database file extension to .php, and use the following method to create a table in the database:
create table ' This way, when anyone accesses the file, a PHP parsing error message will appear, which will prevent users from downloading.
2. If PHP is running as a separate process of CGI or APACHE
Then you can modify the permissions of SQLite database files, such as 0600.
3. If the WEB server is APACHE and supports custom .htaccess, then the following content can be added to the .htaccess file:
Deny from all
where .sqlite is the extension of your database file.
4. Setting the complex points of your database name will not be easily guessed by others.
The combination of PHP and SQLite is just like the combination of ASP and ACCESS back then. ACCESS can be maliciously downloaded, and SQLite is also not spared, because SQLite is also a binary file, and as long as WEB can access it, it can be downloaded.
ACCESS can use some tricks to prevent users from downloading, and SQLite can do it too. Here are some commonly used methods to prevent SQLite from being downloaded
1. Place SQLite in a place that cannot be accessed by WEB.
Some virtual hosts generally provide a separate directory for users to place some files that they do not want to be downloaded or accessed, so it is safe to place them in this directory. Ilia also offers another approach, which is somewhat similar to ACCESS practices.
It is to change the SQLite database file extension to .php, and use the following method to create a table in the database:
create table ' This way, when anyone accesses the file, a PHP parsing error message will appear, which will prevent users from downloading.
2. If PHP is running as a separate process of CGI or APACHE
Then you can modify the permissions of SQLite database files, such as 0600.
3. If the WEB server is APACHE and supports custom .htaccess, then the following content can be added to the .htaccess file:
Deny from all
where .sqlite is the extension of your database file.
4. Setting the complex points of your database name will not be easily guessed by others.