Hi. I had a ui-502 error when I changed netflix zone. US -> Canada -> USI did this to test some stuff when netflix stopped working near the start of this thread

I cheekily got on the netflix message help, and the lady told me that it was because I was accessing Canadian content from a US netflix account.I fixed this by logging out of all devices (you do this from the netflix account management screen), and then clearing the cache on all browsers accessing netflix from PC's, then logging in to netflix again.

My browser had cached "Canada" in the netflix header and it needed to be cleared before I could access content from the new netflix zone. Trying to access canada from my browser, and US from my roku sent netflix into a spin.

I am also from Central Otago, on Vodafone adsl and haven't been able to get Netflix US since the problems started. I get get Netflix Canada and UK using Unotelly. I signed up with Ihug about 8 years ago.

I am in Auckland, VF adsl, use Getflix and have no problem with Netflix or Hulu.I do have a paid up annual subscription for Unotelly that my son in Brisbane is using with Bigpond and he says that he does has loading and buffering 'issues' with Netflix.if I get time, I should set it up and see if it works properly with my VF Adsl here.

Does anyone know if Trustpower will do the adjustments needed on their side ..to get Netflix back working

Thanks for all your help now with this issue, we no longer need any further testing to be carried out and have concluded our investigations. 1. Netflix recently changed the format of URLs for US and Canadian CDN used for video streaming 2. The affected NZ providers are using transparent caching proxies for the Netflix CDN range of IP addresses. They are NOT using these for other IP ranges we tested. 3. The affected NZ providers are using transparent caching proxies that are set up incorrectly: - They cache content with "no cache" directive in HTTP header (Pragma: no-cache & Cache-Control: no-store) - They ignore query string part of the URL for caching The combination of 1, 2 and 3 has resulted in the Netflix streaming issue. Netflix has started using query string part of the URL to request the movie pieces. Since the content is cached incorrectly, the Netflix player tries to get a fragment of the movie but gets a completely different movie piece from the proxy and shows the error message. Affected ISPs have to reconfigure their proxies to: Take query string into account OR Respect "no cache" directive OR Turn them off for Netflix CDN IP range as caching Netflix streaming does not provide any benefit to the ISP. We encourage you to send the above to your ISP - as this is how they can fix the issue. If enough of you speak - then your ISP might do something about it.

Seems like the other major providers have fixed the problem. Not sure who in Trustpower is looking at this...appreciate if anyone is dealing with if they can give contact details and email address so I can forward the response above, which came from Unblock -US

Well blow me down - tried Netflix on the Bravia again yesterday and it's all working perfectly! Very happy :-) Now wondering if it's because I've only recently had (VF) VDSL installed and the profile has just changed to something the TV's a little happier with...

Does anyone know if Trustpower will do the adjustments needed on their side ..to get Netflix back working

Thanks for all your help now with this issue, we no longer need any further testing to be carried out and have concluded our investigations. 1. Netflix recently changed the format of URLs for US and Canadian CDN used for video streaming 2. The affected NZ providers are using transparent caching proxies for the Netflix CDN range of IP addresses. They are NOT using these for other IP ranges we tested. 3. The affected NZ providers are using transparent caching proxies that are set up incorrectly: - They cache content with "no cache" directive in HTTP header (Pragma: no-cache & Cache-Control: no-store) - They ignore query string part of the URL for caching The combination of 1, 2 and 3 has resulted in the Netflix streaming issue. Netflix has started using query string part of the URL to request the movie pieces. Since the content is cached incorrectly, the Netflix player tries to get a fragment of the movie but gets a completely different movie piece from the proxy and shows the error message. Affected ISPs have to reconfigure their proxies to: Take query string into account OR Respect "no cache" directive OR Turn them off for Netflix CDN IP range as caching Netflix streaming does not provide any benefit to the ISP. We encourage you to send the above to your ISP - as this is how they can fix the issue. If enough of you speak - then your ISP might do something about it.

Seems like the other major providers have fixed the problem. Not sure who in Trustpower is looking at this...appreciate if anyone is dealing with if they can give contact details and email address so I can forward the response above, which came from Unblock -US

CheersPeter

I'll see about passing this on to them. As a Trustpower Home and Business customer