[HTTPS-Everywhere] NYTimes error

[Colonel Graff]

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
<exclusion pattern = "^http://:.*\.blogs\.nytimes\.com/.*" />
If I remember my JavaScript RegExp properly.
They could include this in the development branch and I'd be happy to test
to make sure it's working properly.

P.S.
Jacy, sorry that I responded with my other email. Everything I get is
forwarded there, I just forget to respond from this one.

On Tue, Aug 10, 2010 at 3:56 PM, Jacy Odin Grannis <
eyrieowl-activism at yahoo.com> wrote:

> The plugin causes the Room For Debate oped section of the NY Times website
> to fail.  It appears that the url www.nytimes.com/roomfordebate is not
> hosted on the same server, but is hosted on
> roomfordebate.blogs.nytimes.com.  However, trying to access the server
> address redirects to www.nytimes.com/roomfordebate.  Unfortunately,
> though, the server doesn't seem to support https, unlike the primary server,
> so when the plugin tries to rewrite, say,
> http://www.nytimes.com/roomfordebate/2010/8/9/who-gets-priority-on-the-webto
> https://www.nytimes.com/roomfordebate/2010/8/9/who-gets-priority-on-the-web,
> it ends up redirecting back to http://www.nytimes.com/roomfordebate.  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
>
> 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*/*nytimes.com/roomfordebate/*).
> 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).
>
> Jacy
>
> _______________________________________________
> HTTPS-everywhere mailing list
> HTTPS-everywhere at mail1.eff.org
> https://mail1.eff.org/mailman/listinfo/https-everywhere
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.eff.org/pipermail/https-everywhere/attachments/20100812/f65339ac/attachment.html>