Skip to content
This repository has been archived by the owner on May 1, 2020. It is now read-only.

use wss: protocol for secure websocket when page is using https: #1358

Merged
merged 1 commit into from
Aug 24, 2018

Conversation

rall
Copy link
Contributor

@rall rall commented Jan 2, 2018

Short description of what this resolves:

When using an https (and wss) reverse proxy for the browser platform, the hardcoded ws protocol WebSocket connection gives a Mixed Content error.

Changes proposed in this pull request:

  • attempt to connect to the WebSocket with wss when the page is on https

I know there is some work being done towards better support for https in development environments (see https://github.com/ionic-team/ionic/issues/1686) but I'm wondering if this small change would be acceptable as a stop-gap?

@rall
Copy link
Contributor Author

rall commented Jan 3, 2018

Hi @mhartington - sorry to ping you directly but I see there are a lot of open PRs on this project. Are user contributions valuable here?

@yong-asial
Copy link

+1

@davidalvarezcastro
Copy link

+1

@imhoffd
Copy link
Contributor

imhoffd commented Aug 24, 2018

@rall Thanks--merging this for power users but Ionic likely will not support HTTPS for Ionic v3 apps using @ionic/app-scripts out of the box.

See ionic-team/ionic-cli#3305 for HTTPS support in Ionic 4.

Thank you!

@imhoffd imhoffd merged commit 29c3e23 into ionic-team:master Aug 24, 2018
trsrm added a commit to powwowinc/ionic-app-scripts-tiny that referenced this pull request Jan 2, 2019
3.1.9:
* fix(2889): fix build error with --prod
* fix(serve): start listening when watch is ready
* fix(live-server): update android platform path (ionic-team#1407)
* docs(changelog): 3.1.9

3.1.10:
* Update node-sass dependency (ionic-team#1435)
Updating node-sass dependency from 4.7.2 to 4.9.0 to make it works with node 10 on windows (build fail with ionic start)
* chore(package): bump deps (ionic-team#1421)
* chore(deps): no package lock
* chore(changelog): 3.1.10

3.1.11:
* fix(serve): fix EADDRINUSE issue with dev logger server
fixes ionic-team/ionic-cli#3368
fixes ionic-team/ionic-cli#1678
fixes ionic-team/ionic-cli#1830
fixes ionic-team/ionic-cli#1721
fixes ionic-team/ionic-cli#1866
fixes ionic-team/ionic-cli#1808
fixes ionic-team/ionic-cli#3022
* docs(changelog): 3.1.11 changes

3.2.0:
* feat(environments): configuration via process.env.VAR replacement (ionic-team#1471)
* fix(sass): remove PostCSS warning (ionic-team#1364)
This removes following warning:
Remove warning: Without `from` option PostCSS could generate wrong source map or do not find Browserslist config. Set it to CSS file path or to `undefined` to prevent this warning
`from: the input file name (most runners set it automatically).`
Source: https://github.com/postcss/postcss
Fixes ionic-team#1359 #13763
ionic-team#1359
ionic-team/ionic-framework#13763
* fix(serve): use wss protocol for secure websocket when page is using https (ionic-team#1358)
* docs(changelog): 3.2.0

3.2.1:
* docs(readme): add note about existing declaration
addresses ionic-team/ionic-cli#3541
* chore(deps): update webpack to 3.12.0 (ionic-team#1477)
* chore(deps): bump node-sass to 4.9.3 to fix security warnings (ionic-team#1483)
* chore(deps): bump node-sass to 4.10.0 to fix security warnings (ionic-team#1493)
* docs(changelog): 3.2.1
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants