Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Screenshots for RPC #665
It is easy to add screenshots to Github issues (I'm very new to Github).
Here is the URL for the screenshot:
This is 'not much use for the website'. I run many Profiles  and I use Classic Theme Restorer to colour (color) the "selected tab" with a specific colour so that I know which Profile I am using. The 'garish purple' tells me that I'm using a profile with an almost empty Whitelist (for both NoScript and RPC).
Below are some screenshots. I have added them to this issue. The URLs are 'automatically generated by Github', just right click and "Open Link in New Tab" to find the URL.
Abbreviations and conventions:
Updating from RP 0.5.xx to RPC
Before you start make a copy of your Profile.
e.g. on Windows the Profile might be in this Folder:
Starting with either RequestPolicy 0.5.28.1-signed, or RP 0.5.28,
NoScript is also installed. Both NoScript and RP have short Whitelists in this example.
The Whitelist, in this example, is very short.
In this example I allowed all the 'wikipedia family' of sites, to send requests to (in order to collect images from) - "wikimedia.org".
Here is the Release page for RequestPolicy 1.0.beta9.3
Click the "requestpolicy-1-0-beta9-3.xpi" link to install.
Next you will see this Welcome screen.
If you have 'an old RP' as in this example you have 'two RP Red flags' (one old one from RP and a new RPC Flag). This is expected as you update (when you have finished and restarted Firefox you will only have the new RPC Flag).
Note: NoScript is blocking
If you are Upgrading, as in this example, click "Configure RequestPolicy".
If you have never used RP I recommend that you use the "Teach me how to use RequestPolicy" button. This will take you to
The defaults (shown) are good.
In this example, I am going to show you how to 'keep the RP Whitelist' we had before the Update.
"Block requests by default" and "No, don't use subscription policies."
Then press the "Return to browsing" link.
Now, look at
As you can see you still have the 'old RP'. Remove, in this example RP 0.5.29, and Restart Firefox.
Note: there is now only one 'RP Flag' - this is normal (you only saw two RP Flags when you had two versions of RP).
Now, click the 'RP Flag' and choose "Manage Policies" you will see this:
Scroll down to see Your Rules.
In this example you might not see any!
You might be alarmed. In this screen there are no Active rules!
Now click "Show re-import options".
Here you can see the examples: wikimedia and the BBC (in the order from "pref.js").
Next, click the "Import Old Rules" button (at the bottom of the page).
These rules are saved in "user.json".
In "prefs.js" you will find:
Start Firefox and go to
Now, click the "Remove unused rules left over from the old version of RequestPolicy." link.
Using RequestPolicy with Default Deny and a short Whitelist
I very rarely add Rules - I nearly always use Temporary Rules.
Here is a very short Whitelist, NoScript also has a very short Whitelist, in this example.
Here is the URL: #445
All 234 requests from github are still blocked.
The first request I am going to Temporary Allow will be from
I clicked on the Tab "the project's website . Issue ..." to close the RPC Menu.
Look at the Rules in the "Your Policy"
The RequestPolicy User Interface (UI) is 'sticky': it allows you to make several selections in one visit. Providing you do not 'click outside the RP menu' all your choices will be selected. When you are finished click the Tab "the project's website . Issue ..."
I also, using NoScript, Temporary Allowed the "Blocked Object" from
Next, look at the Rules in the "Your Policy" Tab on the right
Here you can see the 7 TA Rules.
If you click the 'RP Flag' you can quickly delete 'all 7 TA Rules' by clicking
If you close Firefox all the Temporary Rules will be forgotten.