Request Policy 1.0 Alpha released

kupo · Apr 14, 2012

RequestPolicy 1.0 is a major rewrite of RequestPolicy that includes many new features including:

A new UI
A new rule system that supports wildcards in rule hostnames
Blacklists in addition to whitelists
A "default allow" mode instead of just a "default deny" mode
Subscription whitelists/blacklists
Lots of other stuff
Click to expand...

RequestPolicy 1.0+ supports two types of rule actions: "allow" and "block".

Every rule can specify origins and/or destinations that match the rule. When a rule matches a request, the rule's action (allow or block) is triggered. When both an allow and a block rule match a request, the user's default rule is used.

The origin and destination components of a rule can have the following properties. All properties are optional. An empty rule property will not be considered when matching against requests.

Scheme
The URL's scheme (protocol). For example, "http" or "https".
Host
The URL's host. For example, "example.com", "1.2.3.4", or "fe80:0000:0000:0000:0202:b3ff:fe1e:8329". For host names (not IP addresses), you can use a wildcard to indicate any or no subdomain. For example, "*.example.com" will match "example.com", "www.example.com", or "a.b.c.example.com". Wildcards are only supported as the leftmost label of a hostname. Wildcards are not supported anywhere else in the name and cannot be mixed with other characters.1
Port
The URL's port. For example, "81" or "8080. This may also be "*" to indicate that any ports should match. By default, rules that do not specify ports only match the default port for the request's scheme.2
Path
The URL's path. Note: this is planned but not yet implemented. When implemented, this will support either regular expressions or path prefixes.

[1] The restrictions on the host value of rules exists for performance reasons. Allowing regular expressions would mean that every rule with regular expressions would have to be checked for every request. In the future we may add support for regular expressions in host patterns. We may also add support for CIDR notation and IPv6 abbreviated notation.

[2] TODO: confirm this is true.
Click to expand...

form here -https://www.requestpolicy.com/1.0.html
Pretty big changes, now I'm learning to use this new version.

Daveski17 · Apr 15, 2012

Looks interesting, I'll have to have a look at this. RP is good but could always do with a bit of improvement I always thought. Thanks for the link.

kupo · Apr 15, 2012

The version one has a sticky UI (similar to Noscript in terms of when choosing what to allow/block, the context menu will not close in the first click.). I'm gonna wait for the beta though as this alpha still has an incomplete subscription.

Wroll · Apr 15, 2012

It's a nice update although I prefer the old UI. Another regression is the alphabetized blocked domains. With the stable version, if the site was looking broken it was usually the first domain which needed to be allowed. Now you have to exclude the known domains and allow by guessing if there are more unknown domains.

kupo · Apr 15, 2012

Wroll said:

It's a nice update although I prefer the old UI. Another regression is the alphabetized blocked domains. With the stable version, if the site was looking broken it was usually the first domain which needed to be allowed. Now you have to exclude the known domains and allow by guessing if there are more unknown domains.
Click to expand...

I didn't notice that while testing, I have it off my Waterfox now . Maybe you could report it to him? I'm to lazy today, some devs that I contacted today for some bugs in the software still hasn't reply, LOL.

Daveski17 · Apr 15, 2012

I've only had time today to have a precursory glance at it, but I more or less agree with what's been said above. I'm running it on a portable version of Firefox & apart from a few freezing problems (I blame the cheap crappy free work USB stick ... ) it looks interesting. I think it's going to need some work but I like what I see so far. I value RP as an important line of defence (after NoScript) so I would like to get as familiar with the new UI & format as I can.

Daveski17 · Apr 17, 2012

Screenshot of GUI of 1.0.0 a7 update. 17/4/12.

blaze x · May 20, 2012

Anyone using the alpha version in their main profile? or is everyone here using the stable version? And is the alpha version safe to use permanently for now? I like the fact you can permanently block certain domains, it makes it easier to use compared to the old version. Though, I do like the old interface better.

kupo · May 20, 2012

blaze x said:

Anyone using the alpha version in their main profile? or is everyone here using the stable version? And is the alpha version safe to use permanently for now? I like the fact you can permanently block certain domains, it makes it easier to use compared to the old version. Though, I do like the old interface better.
Click to expand...

Still using the stable version. What I love with this alpha is that you can allow multiple domains without refreshing the page with every clicks.

guest · May 20, 2012

Almost forgot I had RP here. I checked the Enable 'Temporarily Allow All Requests' when browser starts option some time ago. I will wait for v1 stable.

Log in or Sign up

Request Policy 1.0 Alpha released

kupo Registered Member

Daveski17 Registered Member

kupo Registered Member

Wroll Registered Member

kupo Registered Member

Daveski17 Registered Member

Daveski17 Registered Member

blaze x Registered Member

kupo Registered Member

guest Guest

Log in or Sign up

Request Policy 1.0 Alpha released

kupo Registered Member

Daveski17 Registered Member

kupo Registered Member

Wroll Registered Member

kupo Registered Member

Daveski17 Registered Member

Daveski17 Registered Member

blaze x Registered Member

kupo Registered Member

guest Guest

Useful Searches