The plugin causes the Room For Debate oped section of the NY Times website to fail.  It appears that the url <a href="http://www.nytimes.com/roomfordebate">www.nytimes.com/roomfordebate</a> is not hosted on the same server, but is hosted on <a href="http://roomfordebate.blogs.nytimes.com">roomfordebate.blogs.nytimes.com</a>.  However, trying to access the server address redirects to <a href="http://www.nytimes.com/roomfordebate">www.nytimes.com/roomfordebate</a>.  Unfortunately, though, the server doesn't seem to support https, unlike the primary server, so when the plugin tries to rewrite, say, <a href="http://www.nytimes.com/roomfordebate/2010/8/9/who-gets-priority-on-the-web">http://www.nytimes.com/roomfordebate/2010/8/9/who-gets-priority-on-the-web</a> to <a href="https://www.nytimes.com/roomfordebate/2010/8/9/who-gets-priority-on-the-web">https://www.nytimes.com/roomfordebate/2010/8/9/who-gets-priority-on-the-web</a>, it ends up redirecting back to <a href="http://www.nytimes.com/roomfordebate">http://www.nytimes.com/roomfordebate</a>.  So one can view the landing page for the feature, but can not actually read any of the sections without opening in another browser or turning off https for NYTimes.com<br>
<br>Thanks, by in large very pleased with the plugin.  It'd be nice, though, if there were a "blacklist" feature where I could add a pattern that I *don't* want the plugin to rewrite (i.e., http*/*<a href="http://nytimes.com/roomfordebate/*">nytimes.com/roomfordebate/*</a>).  That way I could fix this for myself and move on without either disabling entirely for the domain or waiting for a new release.  I know it talks about doing custom rulesets, but a nice interface would go a long way towards making that accessible (see NoRedirect, IE Tab Plus, Foxyproxy, and others for examples of what I'd love to see).<br>
<br>Jacy<br>