Up to now, we have been using notifications.dev as the domain for local development. However, the .dev TLD is now valid, and Google has forced its forwarding to HTTPS as of Chrome 63. This patch instead has us use the .localhost TLD (same as Calypso).
I've chosen to add a new app specific to .localhost rather than updating the existing app, since this is a Chrome-only issue so far.
Testing
Load master at http://notifications.dev:3000 in Chrome 63+, and get a browser error after being redirected to the HTTPS-equivalent URL.
Switch to this branch, and load http://notifications.localhost:3000 . You should not be redirected, and instead see the prompt for OAuth. Continue, and notifications should load properly.
Up to now, we have been using
notifications.devas the domain for local development. However, the.devTLD is now valid, and Google has forced its forwarding to HTTPS as of Chrome 63. This patch instead has us use the.localhostTLD (same as Calypso).I've chosen to add a new app specific to
.localhostrather than updating the existing app, since this is a Chrome-only issue so far.Testing
masterat http://notifications.dev:3000 in Chrome 63+, and get a browser error after being redirected to the HTTPS-equivalent URL.