7 ms·

It looks like it's working too well. The site is unreachable for me.

by ticklemyelmo 10y ago

netsec_burn 10y ago
It's up.
dest 10y ago
down : Secure Connection Failed The connection to techblog.netflix.com was interrupted while the page was loading.
- fred256 10y ago
  It's only available on http, not https.
  - gonzoflip 10y ago
    I am receiving a DNS error when trying to reach the URL C:\Windows\System32>nslookup http://techblog.netflix.com/ http://techblog.netflix.com/ 8.8.8.8 Server: google-public-dns-a.google.com Address: 8.8.8.8 * google-public-dns-a.google.com can't find http://techblog.netflix.com/ http://techblog.netflix.com/: Non-existent domain
    - rglullis 10y ago
      remove the http:// http:// part and try again?
    - kgrin 10y ago
      I'm not on Windows, but I'm pretty sure your problem here is the "http://" http://" - try just: nslookup techblog.netflix.com 8.8.8.8
- ticklemyelmo 10y ago
  Looks like some sequence of events convinces Firefox that HSTS is set, and it always rewrites the request as https (which is not supported by the server) after that.
Thaxll 10y ago
Every time that URL comes up people try to access it from https but the site is only available from http... Fix your Firefox, it's clearly at fault here.
- scrollaway 10y ago
  "Every time"? If one random guy's complaining about a URL being unreachable and you're already seeing a pattern... is it at all possible the users aren't at fault?
  - yalooze 10y ago
    In Thaxll's defense, I've seen this a lot with Netflix blog posts on HN.
  - corobo 10y ago
    To be fair it does happen frequently enough. I wouldn't say every time but often on Netflix posts. A bit of a sampling for you: https://news.ycombinator.com/item?id=12269411 https://news.ycombinator.com/item?id=12269411 https://news.ycombinator.com/item?id=12217900 https://news.ycombinator.com/item?id=12217900 https://news.ycombinator.com/item?id=12038367 https://news.ycombinator.com/item?id=12038367 https://news.ycombinator.com/item?id=11771714 https://news.ycombinator.com/item?id=11771714
- niftich 10y ago
  It's NoScript's new-ish defaults at fault. See https://news.ycombinator.com/item?id=12256720 https://news.ycombinator.com/item?id=12256720

It looks like it's working too well. The site is unreachable for me.

netsec_burn 10y ago

It's up.

dest 10y ago

down : Secure Connection Failed The connection to techblog.netflix.com was interrupted while the page was loading.

fred256 10y ago
It's only available on http, not https.
- gonzoflip 10y ago
  I am receiving a DNS error when trying to reach the URL C:\Windows\System32>nslookup http://techblog.netflix.com/ http://techblog.netflix.com/ 8.8.8.8 Server: google-public-dns-a.google.com Address: 8.8.8.8 * google-public-dns-a.google.com can't find http://techblog.netflix.com/ http://techblog.netflix.com/: Non-existent domain
  - rglullis 10y ago
    remove the http:// http:// part and try again?
  - kgrin 10y ago
    I'm not on Windows, but I'm pretty sure your problem here is the "http://" http://" - try just: nslookup techblog.netflix.com 8.8.8.8
ticklemyelmo 10y ago
Looks like some sequence of events convinces Firefox that HSTS is set, and it always rewrites the request as https (which is not supported by the server) after that.

Thaxll 10y ago

Every time that URL comes up people try to access it from https but the site is only available from http... Fix your Firefox, it's clearly at fault here.

scrollaway 10y ago
"Every time"? If one random guy's complaining about a URL being unreachable and you're already seeing a pattern... is it at all possible the users aren't at fault?
- yalooze 10y ago
  In Thaxll's defense, I've seen this a lot with Netflix blog posts on HN.
- corobo 10y ago
  To be fair it does happen frequently enough. I wouldn't say every time but often on Netflix posts. A bit of a sampling for you: https://news.ycombinator.com/item?id=12269411 https://news.ycombinator.com/item?id=12269411 https://news.ycombinator.com/item?id=12217900 https://news.ycombinator.com/item?id=12217900 https://news.ycombinator.com/item?id=12038367 https://news.ycombinator.com/item?id=12038367 https://news.ycombinator.com/item?id=11771714 https://news.ycombinator.com/item?id=11771714
niftich 10y ago
It's NoScript's new-ish defaults at fault. See https://news.ycombinator.com/item?id=12256720 https://news.ycombinator.com/item?id=12256720