CRA + proxy + HTTPS=true issues with OAuth flow

Is this a bug report?

yes

Environment

1. node -v: 8.3.0

2. npm -v: 5.4.2

3. yarn --version (if you use Yarn): 1.1.0

4. npm ls react-scripts (if you haven’t ejected):

5. Operating system: OSX

Steps to Reproduce

1. I have express.js app running on http://localhost:5000
2. I have Oauth google setted up.
3. I have CRA app installed.
4. I have added target proxy setted in CRA’s package:

"proxy": {
    "/auth/google": {
      "target": "https://localhost:5000"
    }
  },

1. I have npm start script modified to enable self signed SSL certificate in CRA’s package.json as it recommended by README:

"scripts": {
    "start": "HTTPS=true react-scripts start"
}

1. I have link with relative path, embedded to React app, which should proxy to https://localhost:5000/auth/google:

<a href='/auth/google'>Sign In with Google</a>

Expected Behavior

Redirect tohttps://accounts.google.com/signin/oauth/...... to confirm signup:

Actual Behavior

Receiving error in browser:

Proxy error: Could not proxy request /auth/google from localhost:3000 to https://localhost:5000 (ECONNRESET).

PS: If I set proxy in package.json to HTTP instead of HTTPS:

"proxy": {
    "/auth/google": {
      "target": "http://localhost:5000"
    }
  },

and remove HTTPS=true from npm start script, everything works, but my paranoia tells me that in dev mode it is better to be protected, cos some malicious browser extensions could mess with the code. Sorry, I do not have demo.

[gaearon]

Do you have a proposed fix we could apply on our side?

[gaearon]

I see. I’m going to close this as there’s not enough detail for us to dig into this. But if somebody else encounters this, or you see it again, please file a new issue with a reproducing example. Thanks!