[HTTPS-Everywhere] plugin blocks "Room for Debate" articles

[Peter Eckersley]

The underlying problem here is that a URL like this works:

http://www.nytimes.com/roomfordebate/2010/8/15/aging-professors-who-wont-retire

while its https equivalent:

https://www.nytimes.com/roomfordebate/2010/8/15/aging-professors-who-wont-retire

redirects back to the Room For Debate homepage.

We could add an exclusion for /roomfordebate, or we can keep trying to get the
NYTimes' web developers to fix these problems.

On Sun, Aug 22, 2010 at 09:42:57AM -0400, Josh Rubin wrote:
>  The https-everywhere plugin for Firefox prevents access to some
> nytimes.com pages.
> On the "Room for Debate" page www.nytimes.com/roomfordebate
> the links to topics do not work. They work as soon as I disable the plugin.
> 
> I sent this report to the their recommended feedback page at
> roomfordebate at gmail.com:
> 
> > I am writing this on a Macbook running Firefox version 3.6.8.
> >
> >The Room for Debate page doesn't work for me at all. Links to
> >topics take me right back
> >to the main page, so I am unable to read any of it.
> >
> >http://www.nytimes.com/roomfordebate
> >
> >In case it matters, I use the following Firefox addons:
> >
> >Adblock Plus
> >Ghostery
> >HTTPS-everywhere
> >
> 

> _______________________________________________
> HTTPS-everywhere mailing list
> HTTPS-everywhere at mail1.eff.org
> https://mail1.eff.org/mailman/listinfo/https-everywhere


-- 
Peter Eckersley                            pde at eff.org
Senior Staff Technologist         Tel  +1 415 436 9333 x131
Electronic Frontier Foundation    Fax  +1 415 436 9993