Ember-cli: Safari 10: "The network connection was lost."

1. No other configuration change other than the upgrade?
2. No new npm install? Nothing?
3. Do the issues appear in non-Safari browsers?

Goals:

• Identify the set of changes.
• Deduce the set of possible culprits.

If this is a Safari + Sierra-specific bug I'm not going to be able to reproduce for a while, but maybe somebody else will be able to.

@workmanw Can you upgrade to the most-recent version of Safari on your box and see if that triggers the failure?

1. No other configuration change other than the upgrade?

No

1. No new npm install? Nothing?

No

1. Do the issues appear in non-Safari browsers?

Nope, just Safari 10 (12602.1.50.0.8). He also used Chrome 53 (53.0.2785.113) and Firefox 48 (48.0.2) w/ Sierra and had no issues.

What's weirder is that I upgraded my Safari to 10 (12602.1.50.0.5), staying on El Capitan and I had no issues.

I will upgrade to Sierra GM and report back.

I can very easily reproduce this issue after upgrading to Sierra GM and Safari 10 (12602.1.50.0.8). 😢

It seems like maybe this could just be a regression with that specific version of Safari 10. Seeing as how it's only the GM, maybe we should just hold for the time being and check after Sierra releases.

Okay, so Safari + Sierra = network issues. I have no clue what's going on. I'm going to leave this open for a week for awareness, but generally we don't keep tracking issues open on Ember CLI for things which we may not have control over. At that point I'm going to close it or hope somebody figured out what the underlying problem is that combination triggered.

So, people, thoughts?

Just as a quick note: I have exactly the same problem.
It happens on Safari Version 10.0 (12602.1.50.0.10) since upgrade to mac OS Sierra. I've never seen this error before. The error happens quite often, but only to localhost.

We're connecting via nginx as reverse proxy to our node stack (HTTPS, self-signed cert). We're not using anything ember-related at all though, I've found this discussion via a google search.

Tried to pinpoint it to anything, but no success so far. It might be related to Safari/mac OS Sierra.

Okay, y'all, I'm closing this as it's unlikely we are going to be able to do anything about it. @markschmid reports that this happens as well without Ember in the stack, which implies to me that it's an upstream issue in either https://github.com/nodejitsu/node-http-proxy or Safari + Sierra.

If people who encounter this can please continue to comment with your setups that would be fantastic. (Please also upgrade to the newest version of Sierra/Safari.)

Sounds good to me! I tried to build a reproduction, and while I was successful it was very convoluted. Despite getting all of the HTTP headers to match exactly, the reproduction still only worked when the end destination for proxy was Google App Engine. So ¯_(ツ)_/¯. I agree this is not ember-cli's bug. Thank you.