Netflix problems w/noscript 16

[8789]

Hi,

I have to disable noscript to get into netflix. Sometimes I can get to the sign in page, but often not, and even if I can sign in I get a problem loading page that says Page isn't redirecting properly, and can sometimes be caused by disabling or refusing to accept cookies. I have cookies on.

It's a buggy problem, it's not consistent. I have gotten in twice out of the 20 some times I've tried. There is a pop up from noscript when I go to sign in (but not always), and it says:

Temporarily allow https://secure.netflix.com/ffe/siteui/a ... ngleLoop-2
webm
(video/webm <VIDEO> /https://www.netflix.com)

So I allow that, and then can sign in, and then get the problem loading page.

Just going into netflix from google I get the problem loading page. Same thing if I type in netflix.com

There has never been a pop up from noscript before for netflix, so the above is new since I installed 2.6.9.16

I have nothing in advanced, abe nor https for netflix.

I think this has something to do with https. Yesterday I had no problems with netflix (my first time there in a long time) but I had 2.6.9.15 yesterday.

So in order to use netflix I have to disable noscript, and it looks like it's version 16 that is causing the problem.

I appreciate any help. If you ask me questions please explain how to do things if I need to look in the console or something. I'm not too skilled with those things.

Thank you!

[barbaz]

Please tell us the exact NoScript development build (rc version) that broke it
https://addons.mozilla.org/addon/noscript/versions
*or*
https://noscript.net/feed?t=a

[7844]

Hi,

I'm using 2.6.9.16

[barbaz]

Not what I meant. Please install and test rc versions that are older than 2.6.9.16, continuing install the prior rc until it works. Thanks.

[Guest]

HI, None of the versions works. They all return page not redirecting.

Yesterday, with noscript 15 it worked. Today, I updated to firefox 36.01 and to noscript 16. Sounds like its firefox, but netflix works as long as noscript is disabled.

[Guest]

Hi!

As the above post, I tried all the rc versions and none work with netflix. Since I have to remove noscript to view netflix, wouldn't that be a noscript problem?

What I don't understand is I've been searching to see if there are any other hits on netflix and noscript, and firefox 36.0.1 and netflix, and firefox 36.0.1 and page not loading and I get no hits, so it is not a problem others are having so far and I think by now I would get some hits on this.

I have windows vista sp1.

I use sandboxie so am okay as long as I don't surf while viewing netflix, which I doubt I'll remember, but I am at least a bit safer using sandboxie with noscript removed.

Any help would be appreciated.

[arcasinky]

HI, None of the versions works. They all return page not redirecting.

Yesterday, with noscript 15 it worked. Today, I updated to firefox 36.01 and to noscript 16. Sounds like its firefox, but netflix works as long as noscript is disabled.

For what it's worth, I see the same redirect loop behavior on Firefox 38.0 (Redhat Enterprise Linux). I've narrowed it down to NoScript's automatic secure cookies management stuff. When automatic secure cookies management is enabled, I get a redirect loop after Netflix sign-in. Disable that checkbox and everything seems to work.

Is there any way to make NoScript spit out diagnostics about what automatic secure cookies management is doing behind the scenes? What cookie is being blocked? What domain is requesting it? Is there a way to whitelist that particular cookie/domain or are do we simply have to disable ACSM whenever we need to log into our Netflix accounts?

Relevant info:
OS: Redhat Enterprise Linux (v6.6)
Browser: Firefox 38.0
NoScript version: 2.6.9.30

[barbaz]

so NoScript doesn't already spit out the information to the Browser Console (Ctrl-Shift-J)? or is it just getting lost in a massive amount of CSS warnings etc?

You can make an exception but without the information from the Browser Console (Ctrl-Shift-J) it's going to be hard to tell what the needed exception is.
(You might want to enable net/XHR logging in the Browser Console (Ctrl-Shift-J) *before* loading the page and looking for NoScript related messages. Also, clear all cookies before testing, just to make sure.)