I know NYTimes is included in the pattern itself, but you could disable 
the default one, and write your own new ruleset with the exclusion 
pattern for that URL... which would be<br><div style="margin-left: 40px;"><exclusion pattern = "^http://:.*\.blogs\.nytimes\.com/.*"
 /><br>
</div>If I remember my JavaScript RegExp properly.<br>They could include
 this in the development branch and I'd be happy to test to make sure 
it's working properly.<br><br>P.S.<br>Jacy, sorry that I responded with my other email. Everything I get is forwarded there, I just forget to respond from this one.<br><br><div class="gmail_quote">On Tue, Aug 10, 2010 at 3:56 PM, Jacy Odin Grannis <span dir="ltr"><<a href="mailto:eyrieowl-activism@yahoo.com">eyrieowl-activism@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">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" target="_blank">www.nytimes.com/roomfordebate</a> is not hosted on the same server, but is hosted on <a href="http://roomfordebate.blogs.nytimes.com" target="_blank">roomfordebate.blogs.nytimes.com</a>.  However, trying to access the server address redirects to <a href="http://www.nytimes.com/roomfordebate" target="_blank">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" target="_blank">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" target="_blank">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" target="_blank">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/*" target="_blank">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>
<font color="#888888">
<br>Jacy<br>
</font><br>_______________________________________________<br>
HTTPS-everywhere mailing list<br>
<a href="mailto:HTTPS-everywhere@mail1.eff.org">HTTPS-everywhere@mail1.eff.org</a><br>
<a style="" href="https://mail1.eff.org/mailman/listinfo/https-everywhere" target="_blank">https://mail1.eff.org/mailman/listinfo/https-everywhere</a><br>
<br></blockquote></div><br>