Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CHANGED] nats.io resources from HTTP to HTTPS #1596

Merged
merged 1 commit into from Sep 15, 2020
Merged

[CHANGED] nats.io resources from HTTP to HTTPS #1596

merged 1 commit into from Sep 15, 2020

Conversation

DavidSimner
Copy link
Contributor

  • Link to issue, e.g. Resolves #NNN
  • Documentation added (if applicable)
  • Tests added
  • Branch rebased on top of current master (git pull --rebase origin master)
  • Changes squashed to a single commit (described here)
  • Build is green in Travis CI
  • You have certified that the contribution is your original work and that you license the work to the project under the Apache 2 license

Changes proposed in this pull request:

  • This PR fixes a Mixed Content warning in web browsers when viewing the monitoring webpage.

/cc @nats-io/core

kozlovic
kozlovic approved these changes Sep 15, 2020
View reviewed changes
Copy link
Member

@kozlovic kozlovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you for your contribution!

@kozlovic kozlovic changed the title Change nats.io resources from HTTP to HTTPS [CHANGED] nats.io resources from HTTP to HTTPS Sep 15, 2020
@kozlovic kozlovic merged commit b39f0f9 into nats-io:master Sep 15, 2020
@DavidSimner DavidSimner deleted the patch-1 branch September 15, 2020 15:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kozlovic kozlovic kozlovic approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@DavidSimner @kozlovic