All posts by Satheesh Rajan

Hiding PHP extension in IIS using URL rewrite module

We have some situations in which we need to hide the extension of a webpage to the end users. Mostly this is concerned with the server security. Here we discuss about hiding the PHP extension of a wepage deployed in an IIS server .

We can easily implement this in Linux using codes passed via .htaccess file. In the case of Windows we will use URL-rewrite module to achieve the same. By default, this module is not installed alongside IIS, so we need to install it via Microsoft Web Platform Installer (WPI).

After the installation of URL-rewrite module, we need to edit the web.conf file in the root directory.

Say for example, we have a php website ‘’ and its root folder is C:/inetpub/wwwroot/ We need to hide the php extension of the page, That is, we need to rewrite this url into Lets now edit the web.conf file located at the root folder of the site (C:/inetpub/wwwroot/

Attaching a sample web.conf file to make it clear :

<?xml version=”1.0″ encoding=”utf-8″ ?>





         <rule name=”test rule” enabled=”false” stopProcessing=”true”>

              <match url=”^gif” />

               <action type=”Rewrite” url=”{R:0}.aspx” />






In our case look for the <rewrite> option in the web.conf file. After finding <rewrite> tag, copy the below mentioned configuration and paste it under the <rewrite> tag.

<rule name=”PHP Hiding”>

     <match url=”(.*)” />

         <conditions logicalGrouping=”MatchAll”>

             <add input=”{REQUEST_FILENAME}” matchType=”IsFile” negate=”true” />

             <add input=”{REQUEST_FILENAME}” matchType=”IsDirectory” negate=”true” />


     <action type=”Rewrite” url=”{R:1}.php” />


After this, the webpage will always be displayed as instead of

No backupset selected to be restored – error in SQL 2012/14 !

Sometimes we get a message like “No backupset selected to be restored” while trying to restore a Database into SQL server 2012 or SQL Server 2014 using SQL Management Studio. There are various reasons for this to happen, such as :

  • If we are trying to restore the backup from a different version of SQL Server. For example consider we have SQL Server 2008 Express and if we try to restore a backup of any other version such as SQL Server 2012 or 2014, this error should pop up.
  • Another main reason is related to the permission of ‘.bak’ file. If the .bak file is having any special permissions or it is located in a folder with special permissions, then Management studio will not read the file and this may lead to this error. So we make sure that .bak file have the appropriate permission  before proceeding with the restoration.

If you are facing this issue and you want more information about this error, try to restore the DB using the following T-SQL:

RESTORE DATABASE <Your Database > FROM DISK=’<Path to your backup file>\<Your Database>.bak’

This should do it 🙂