Choose from thousands of extra features and styles to make Firefox your own.Close
|User since||March 5, 2007|
|Number of add-ons developed||0 add-ons|
|Average rating of developer's add-ons||Not yet rated|
I have been looking for an extension that displays not only HTTP headers but the body/content as well. This extension does not display UTF-8 Byte Order Marks even though they are sent by the web server and I can see them with an external packet sniffer. I'm not sure if this is a bug in this extension or a Firefox limitation. Firefox doesn't display the BOM in its source code view either, nor does Firebug in its net traffic tab.This review is for a previous version of the add-on (0.8.11).
The NoRedirect extension does what it said it would and does not do what it didn't say.
This extension uses regular expressions. If you want to block all redirects you will have to add a regular expression matching all URLs, e.g. ".*". That's a dot followed by an asterisk. An asterisk alone (*) is not going to work.
Anyway, the last few reviews made me suspicious enough to have a closer look at this extension and its source code.
First, it does not hijack search results. Hijacked search results like the ones described by the previous reviewer may be sign of malware and the problem is a common one (a Web search gives plenty of results and suggestions, e.g. running a malware scan). However, I could not find any sign that this extension engages in such behaviour, nor did I find anything suspicious inside the extension's source code.
Second, it does work on Firefox 16.0.1.
There are four columns. The first one is named "RegExp Pattern" and provides an edit box, the other three are checkboxes named "Source", "Allow" and "DNS error" (on that order, from left to right).
Below is the description of these settings:
a regular expression pattern (PCRE) to match the source or destination URL
whether the pattern should match the source (checked) or destination (unchecked) URL
whether this is a redirect that should be allowed (checked) or blocked (unchecked)
whether the browser should display a DNS error upon interdicting the redirect
My only suggestion at this point would be to add an option to enable/disable this extension. The option's value, preferably a boolean, would have to be accessible through about:config. This would allow a user to toggle NoRedirect through Prefbar's checkbox.
If you are using the PrefBar extension, go to http://prefbar.mozdev.org/buttons.html#togglecss and install the "CSS Checkbox 1.0" button. This will create a new item on your PrefBar which happens to do exactly what Read Easily did... :-) HTHThis review is for a previous version of the add-on (1.0.3).
Uses UNIX linebreaks when running on Windows. Nevertheless a very useful extension with clever options.This review is for a previous version of the add-on (1.14.1).
One of my favourite extensions. Admittedly, it takes about 15 minutes to fully understand all the options but it really pays in the long run.
Yes, subdomain blocking is supported. Simply go to
Options - Menus - Behavior
and uncheck the "Display only the base domain" option.
And if you don't like any particular menu item, simply drag it horizontally to remove it from the menu.
About the icons, well, there are five different icon sets available through
Options - Appeareance - Default Skin
Since I got used to it I prefer the Classic set, but if you're looking for something more obvious try the "Simple" sets ... and by the way, one should never judge a software by its icons! :-)
The keyboard shortcut sound like a good idea. Why don't you post it over at the CookieSafe forum?