Tag Info

New answers tagged

0

Based on this question you will need something like this: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^([^\.]+)$ $1.php [NC,QSA,L,E=LOOP:1] RewriteCond %{ENV:REDIRECT_LOOP} !1 RewriteRule ^(.*)\.php$ /$1 [NC,QSA,R=301,L] !-f and !-d ensure that it doesn't get executed for files and directories that exist The ...


0

Use that in root .htaccess: RewriteEngine On RewriteCond %{THE_REQUEST} \s/+(.+)\.php[\s?] [NC] RewriteRule ^ /%1 [R=302,L,NE] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^([^\.]+)$ $1.php [NC,QSA,L]


0

From Will Setting open_basedir in an .htaccess file completely limit a PHP scripts directory access? here is how you set the open_basedir for PHP in your .htaccess file: php_flag open_basedir "/var/www/vhosts/mydomain.com/php_can_only_access_files_in_this_directory/"


2

B in this password means that this encryption uses random salt, than md5(saltWithDash . md5(password)). If you want to check user input with password from database, you need to extract salt from password and combine user password with that salt. Next, compare this two hashes, and if matches, user password is valid. <?php $password = 'password'; ...


2

Hope this helps someone: This is how mediawiki saves the user password in the database. Please see @Aleksander's answer for more details.


1

Actually, there is a way to tell which plugins may be the problem. The P3 plugin (ironically, written by GoDaddy) can be used to generate a report of what each plugin is doing in terms of runtime. Longer run times will usually correlate with more resources consumed and give you some initial guidance on which plugins to examine first.


1

It appears that your APACHE_LOG_DIR variable is not defined. See this thread. It says that you need to define it in /etc/apache2/envvars. I'm not sure exactly where then envvars file would be on a Mac, but it should be with all the other apache2 configuration files. Alternately, you should just use a hardcoded path rather than ${APACHE_LOG_DIR}. For ...


1

Having a server serve unparsed PHP files is a big security hole. It means anyone else would be able to read the code. What happens if you have some files with a password on there? The other issue is speed: loading so many files (dozens, if not hundreds) from a completely different server would be very slow. If you were hosting multiple sites on the same ...


1

After the name servers change and migration, while my website is correctly working from the new server, it doesn't mean the propagation of the change has completed. When my new server tries to send an email to info@example.com via PHP mail(), it has to look up the MX records of example.com for the destination server. However as the propagation hasn't ...



Top 50 recent answers are included