Change http to https for security links

For security, we should change http into https links. This PR also update deprecated links Signed-off-by: huynq0911 <[email protected]>
morgo · Feb 16, 2019 · 1898eba · 1898eba
1 parent e832f3f
commit 1898eba
Show file tree

Hide file tree

Showing 32 changed files with 57 additions and 57 deletions.
diff --git a/ADOPTERS.md b/ADOPTERS.md
@@ -1,14 +1,14 @@
 This is an alphabetical list of known adopters of Vitess. Some have already gone into production, and others are at various stages of testing.
 
-* [YouTube](http://youtube.com)
-* [Axon](http://axon.com)
-* [BetterCloud](http://bettercloud.com)
-* [FlipKart](http://flipkart.com)
-* [HubSpot](http://product.hubspot.com/)
-* [JD](http://jd.com/)
-* [Nozzle](http://nozzle.io)
-* [Pixel Federation](http://pixelfederation.com)
-* [Quiz of Kings](http://quizofkings.com)
-* [Slack](http://slack.com)
-* [Square](http://square.com)
-* [Stitch Labs](http://stitchlabs.com)
+* [YouTube](https://youtube.com)
+* [Axon](https://axon.com)
+* [BetterCloud](https://bettercloud.com)
+* [FlipKart](https://flipkart.com)
+* [HubSpot](https://product.hubspot.com/)
+* [JD](https://jd.com/)
+* [Nozzle](https://nozzle.io)
+* [Pixel Federation](https://pixelfederation.com)
+* [Quiz of Kings](https://quizofkings.com)
+* [Slack](https://slack.com)
+* [Square](https://square.com)
+* [Stitch Labs](https://stitchlabs.com)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -10,7 +10,7 @@ to let everyone know what you're planning to work on, and to track progress and
 
 ## Guidance for Novice Vitess Developers
 
-**Please read [vitess.io/contributing/](http://vitess.io/contributing/)** where we provide more information:
+**Please read [vitess.io/contributing/](https://vitess.io/contributing/)** where we provide more information:
 
 * How to make yourself familiar with Go and Vitess.
 * How to go through the GitHub workflow.

diff --git a/doc/Concepts.md b/doc/Concepts.md
@@ -3,7 +3,7 @@ This document defines common Vitess concepts and terminology.
 ## Keyspace
 
 A *keyspace* is a logical database. In the unsharded case, it maps directly
-to a MySQL database name. If [sharded](http://en.wikipedia.org/wiki/Shard_(database_architecture)),
+to a MySQL database name. If [sharded](https://en.wikipedia.org/wiki/Shard_(database_architecture)),
 a keyspace maps to multiple MySQL databases. However, it appears as a single
 database to the application.
 

diff --git a/doc/GettingStarted.md b/doc/GettingStarted.md
@@ -73,10 +73,10 @@ OS X 10.11 (El Capitan) should work as well, the installation instructions are b
 
 In addition, Vitess requires the software and libraries listed below.
 
-1.  [Install Go 1.11+](http://golang.org/doc/install).
+1.  [Install Go 1.11+](https://golang.org/doc/install).
 
 2.  Install [MariaDB 10.0](https://downloads.mariadb.org/) or
-    [MySQL 5.6](http://dev.mysql.com/downloads/mysql). You can use any
+    [MySQL 5.6](https://dev.mysql.com/downloads/mysql). You can use any
     installation method (src/bin/rpm/deb), but be sure to include the client
     development headers (`libmariadbclient-dev` or `libmysqlclient-dev`).
 
@@ -155,7 +155,7 @@ In addition, Vitess requires the software and libraries listed below.
     
 #### OS X
 
-1.  [Install Homebrew](http://brew.sh/). If your /usr/local directory is not empty and you never used Homebrew before,
+1.  [Install Homebrew](https://brew.sh/). If your /usr/local directory is not empty and you never used Homebrew before,
     it will be 
     [mandatory](https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/El_Capitan_and_Homebrew.md) 
     to run the following command:
@@ -365,7 +365,7 @@ lock service. ZooKeeper is included in the Vitess distribution.
 
     Check the system-wide `file-max` setting as well as user-specific
     `ulimit` values. We recommend setting them above 100K to be safe.
-    The exact [procedure](http://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/)
+    The exact [procedure](https://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/)
      may vary depending on your Linux distribution.
 
 1.  **Configure environment variables**

diff --git a/doc/GettingStartedKubernetes.md b/doc/GettingStartedKubernetes.md
@@ -19,7 +19,7 @@ The following sections explain how to set these up in your environment.
 
 ### Install Go 1.11+
 
-You need to install [Go 1.11+](http://golang.org/doc/install) to build the
+You need to install [Go 1.11+](https://golang.org/doc/install) to build the
 `vtctlclient` tool, which issues commands to Vitess.
 
 After installing Go, make sure your `GOPATH` environment
@@ -30,7 +30,7 @@ directory to which your non-root user has write access.
 In addition, make sure that `$GOPATH/bin` is included in
 your `$PATH`. More information about setting up a Go
 workspace can be found at
-[How to Write Go Code](http://golang.org/doc/code.html#Organization).
+[How to Write Go Code](https://golang.org/doc/code.html#Organization).
 
 ### Build and install vtctlclient
 

diff --git a/doc/Monitoring.md b/doc/Monitoring.md
@@ -14,7 +14,7 @@ Viewing a status page can be useful since it works out of the box, but it only p
 
 ### 2. Pull-based metrics system
 
-Vitess uses Go’s [expvar package](http://golang.org/pkg/expvar/) to expose various metrics, with the expectation that a user can configure a pull-based metrics system to ingest those metrics. Metrics are published to `http://<host>:<port>/debug/vars` as JSON key-value pairs, which should be easy for any metrics system to parse.
+Vitess uses Go’s [expvar package](https://golang.org/pkg/expvar/) to expose various metrics, with the expectation that a user can configure a pull-based metrics system to ingest those metrics. Metrics are published to `http://<host>:<port>/debug/vars` as JSON key-value pairs, which should be easy for any metrics system to parse.
 
 Scraping Vitess variables is a good way to integrate Vitess into an existing monitoring system, and is useful for building up detailed monitoring dashboards. It is also the officially supported way for monitoring Vitess.
 
@@ -32,7 +32,7 @@ Once you’ve written the backend plug-in, you also need to register the plug-in
 
 You can then specify that Vitess should publish stats to the backend that you’re targeting by using the `--stats_backend` flag.  
 
-Connecting Vitess to a push-based metrics system can be useful if you’re already running a push-based system that you would like to integrate into. More discussion on using a push vs pull based monitoring system can be seen here: [http://www.boxever.com/push-vs-pull-for-monitoring](http://www.boxever.com/push-vs-pull-for-monitoring)
+Connecting Vitess to a push-based metrics system can be useful if you’re already running a push-based system that you would like to integrate into. More discussion on using a push vs pull based monitoring system can be seen here: [http://www.boxever.com/push-vs-pull-for-monitoring](https://www.boxever.com/push-vs-pull-for-monitoring)
 
 ## Monitoring with Kubernetes
 

diff --git a/doc/ScalabilityPhilosophy.md b/doc/ScalabilityPhilosophy.md
@@ -16,7 +16,7 @@ the assignment of servers and ports is abstracted away from the administrator.
 On baremetal, the operator still has these responsibilities.
 
 We provide sample configs to help you [get started on Kubernetes](/getting-started/)
-since it's the most similar to Borg (the [predecessor to Kubernetes](http://blog.kubernetes.io/2015/04/borg-predecessor-to-kubernetes.html)
+since it's the most similar to Borg (the [predecessor to Kubernetes](https://blog.kubernetes.io/2015/04/borg-predecessor-to-kubernetes.html)
 on which Vitess now runs in YouTube).
 If you're more familiar with alternatives like Mesos, Swarm, Nomad, or DC/OS,
 we'd welcome your contribution of sample configs for Vitess.

diff --git a/doc/ScalingMySQL.md b/doc/ScalingMySQL.md
@@ -70,7 +70,7 @@ Setting up these components directly -- for example, writing your own topology s
 
 Obviously, your application needs to be able to call your database. So, we'll jump straight to explaining how you'd modify your application to connect to your database through vtgate.
 
-As of Release 2.1, VTGate supports the MySQL protocol. So, the application only needs to change where it connects to. For those using Java or Go, we additionally provide libraries that can communicate to VTGate using [gRPC](http://www.grpc.io/). Using the provided libraries allow you to send queries with bind variables, which is not inherently possible through the MySQL protocol.
+As of Release 2.1, VTGate supports the MySQL protocol. So, the application only needs to change where it connects to. For those using Java or Go, we additionally provide libraries that can communicate to VTGate using [gRPC](https://www.grpc.io/). Using the provided libraries allow you to send queries with bind variables, which is not inherently possible through the MySQL protocol.
 
 #### Unit testing database interactions
 

diff --git a/doc/SchemaSwap.md b/doc/SchemaSwap.md
@@ -13,7 +13,7 @@ ApplySchema]({% link user-guide/schema-management.md %}) instead.
 
 One solution to realize such long-running schema changes is to use a temporary
 table and keep it in sync with triggers as [originally proposed by
-Shlomi](http://code.openark.org/blog/mysql/online-alter-table-now-available-in-openark-kit)
+Shlomi](https://code.openark.org/blog/mysql/online-alter-table-now-available-in-openark-kit)
 and further refined by others ([Percona's
 pt-online-schema-change](https://www.percona.com/doc/percona-toolkit/2.2/pt-online-schema-change.html),
 [Square's Shift](https://github.com/square/shift)).

diff --git a/doc/TestingOnARamDisk.md b/doc/TestingOnARamDisk.md
@@ -1,6 +1,6 @@
 # Testing On A Ramdisk
 
-The `integration_test` testsuite contains tests that may time-out if run against a slow disk. If your workspace lives on hard disk (as opposed to [SSD](http://en.wikipedia.org/wiki/Solid-state_drive)), it is recommended that you run tests using a [ramdisk](http://en.wikipedia.org/wiki/RAM_drive).
+The `integration_test` testsuite contains tests that may time-out if run against a slow disk. If your workspace lives on hard disk (as opposed to [SSD](https://en.wikipedia.org/wiki/Solid-state_drive)), it is recommended that you run tests using a [ramdisk](https://en.wikipedia.org/wiki/RAM_drive).
 
 # Setup
 

diff --git a/doc/TopologyService.md b/doc/TopologyService.md
@@ -6,7 +6,7 @@ store small pieces of configuration data about the Vitess cluster, and provide
 cluster-wide locks. It also supports watches, and master election.
 
 Concretely, the Topology Service features are implemented by
-a [Lock Server](http://en.wikipedia.org/wiki/Distributed_lock_manager), referred
+a [Lock Server](https://en.wikipedia.org/wiki/Distributed_lock_manager), referred
 to as Topology Server in the rest of this document. We use a plug-in
 implementation and we support multiple Lock Servers (Zookeeper, etcd, Consul, …)
 as backends for the service.

diff --git a/doc/Upgrading.md b/doc/Upgrading.md
@@ -6,7 +6,7 @@ Generally speaking, upgrading Vitess is a safe and easy process because it is ex
 
 ## Compatibility
 
-Our versioning strategy is based on [Semantic Versioning](http://semver.org/).
+Our versioning strategy is based on [Semantic Versioning](https://semver.org/).
 
 Vitess version numbers follow the format `MAJOR.MINOR.PATCH`.
 We guarantee compatibility when upgrading to a newer **patch** or **minor** version.
@@ -30,7 +30,7 @@ Please use this upgrade order (unless otherwise noted in the release notes):
 
 ## Canary Testing
 
-Within the vtgate and vttablet components, we recommend to [canary](http://martinfowler.com/bliki/CanaryRelease.html) single instances, keyspaces and cells. Upgraded canary instances can "bake" for several hours or days to verify that the upgrade did not introduce a regression. Eventually, you can upgrade the remaining instances.
+Within the vtgate and vttablet components, we recommend to [canary](https://martinfowler.com/bliki/CanaryRelease.html) single instances, keyspaces and cells. Upgraded canary instances can "bake" for several hours or days to verify that the upgrade did not introduce a regression. Eventually, you can upgrade the remaining instances.
 
 ## Rolling Upgrades
 

diff --git a/doc/UserGuideIntroduction.md b/doc/UserGuideIntroduction.md
@@ -5,7 +5,7 @@ Other Linux distributions should work as well.
 
 ## Database support
 
-Vitess supports [MySQL 5.6](http://dev.mysql.com/doc/refman/5.6/en/),
+Vitess supports [MySQL 5.6](https://dev.mysql.com/doc/refman/5.6/en/),
 [MariaDB 10.0](https://downloads.mariadb.org/mariadb/10.0.21/), and any
 newer versions like MySQL 5.7, etc. Vitess also supports Percona's
 variations of these versions.
@@ -56,7 +56,7 @@ VTGate understands the MySQL binary protocol. So, any client that
 can directly talk to MySQL can also use Vitess.
 
 Additionally, VTGate exposes its functionality through a
-[gRPC](http://www.grpc.io/) API which has support for multiple languages.
+[gRPC](https://www.grpc.io/) API which has support for multiple languages.
 
 Accessing Vitess through gRPC has some minor advantages over the MySQL
 protocol:

diff --git a/doc/V3HighLevelDesign.md b/doc/V3HighLevelDesign.md
@@ -301,7 +301,7 @@ You’ll see how these operands are used in the description of the operators.
 
 ## The operators
 
-If one were to ask what are the minimal set of primitives needed to serve SQL queries, we can use [relational algebra](http://www.tutorialspoint.com/dbms/relational_algebra.htm) as starting point. But databases have extended beyond those basic operations. They allow duplicate tuples and ordering. So, here’s a more practical set:
+If one were to ask what are the minimal set of primitives needed to serve SQL queries, we can use [relational algebra](https://www.tutorialspoint.com/dbms/relational_algebra.htm) as starting point. But databases have extended beyond those basic operations. They allow duplicate tuples and ordering. So, here’s a more practical set:
 
 1. Scan (FROM).
 2. Join: Join two results as cross-product (JOIN).

diff --git a/doc/VitessOverview.md b/doc/VitessOverview.md
@@ -127,7 +127,7 @@ The diagram below illustrates Vitess' components:
 
 The [Topology Service]({% link user-guide/topology-service.md %}) is a metadata store that contains information about running servers, the sharding scheme, and the replication graph.  The topology is backed by a consistent data store.  You can explore the topology using **vtctl** (command-line) and **vtctld** (web).
 
-In Kubernetes, the data store is [etcd](https://github.com/coreos/etcd).  Vitess source code also ships with [Apache ZooKeeper](http://zookeeper.apache.org/) support.
+In Kubernetes, the data store is [etcd](https://github.com/coreos/etcd).  Vitess source code also ships with [Apache ZooKeeper](https://zookeeper.apache.org/) support.
 
 ### vtgate
 

diff --git a/doc/VitessReplication.md b/doc/VitessReplication.md
@@ -139,7 +139,7 @@ Thus, you can survive sudden master failure without losing any transactions that
 were reported to clients as completed. In MySQL 5.7+, this guarantee is
 strengthened slightly to preventing loss of any transactions that were ever
 **committed** on the original master, eliminating so-called
-[phantom reads](http://bugs.mysql.com/bug.php?id=62174).
+[phantom reads](https://bugs.mysql.com/bug.php?id=62174).
 
 On the other hand these behaviors also give a requirement that each shard must
 have at least 2 tablets with type *replica* (with addition of the master that

diff --git a/doc/VtExplain.md b/doc/VtExplain.md
@@ -5,7 +5,7 @@ The vtexplain tool provides information about how Vitess will execute a statemen
 ## Prerequisites
 
 You'll need to build the `vtexplain` binary in your environment.
-To find instructions on how to build this binary please refer to this [guide](http://vitess.io/getting-started/local-instance.html#manual-build). 
+To find instructions on how to build this binary please refer to this [guide](https://vitess.io/getting-started/local-instance.html#manual-build). 
 
 ## Explaining a Query
 

diff --git a/doc/internal/Overview.md b/doc/internal/Overview.md
@@ -1,5 +1,5 @@
 # Internal Documentation
 
-The documents in this category document internal processes which are taken care of by the Vitess Team e.g. re-publishing the website [vitess.io](http://vitess.io) or creating a new release.
+The documents in this category document internal processes which are taken care of by the Vitess Team e.g. re-publishing the website [vitess.io](https://vitess.io) or creating a new release.
 
 We have put them here to increase transparency and make it easy for others to follow and improve processes.
diff --git a/doc/internal/PublishWebsite.md b/doc/internal/PublishWebsite.md
@@ -2,7 +2,7 @@
 
 ## Overview
 
-Our website [vitess.io](http://vitess.io) are static HTML pages which are
+Our website [vitess.io](https://vitess.io) are static HTML pages which are
 generated by [Jekyll](https://github.com/jekyll/jekyll) from Markdown files
 located in the [`doc/`](https://github.com/vitessio/vitess/tree/master/doc)
 directory.

diff --git a/doc/internal/ReleaseInstructions.md b/doc/internal/ReleaseInstructions.md
@@ -5,7 +5,7 @@ This page describes the steps for cutting a new [open source release]
 
 ## Versioning
 
-Our versioning strategy is based on [Semantic Versioning](http://semver.org/).
+Our versioning strategy is based on [Semantic Versioning](https://semver.org/).
 
 ### Major Release (vX)
 
@@ -193,13 +193,13 @@ Therefore, file a JIRA ticket with Sonatype to get added ([example for a differe
 
 **Set up GPG**
 
-Follow [Sonatype's GPG instructions](http://central.sonatype.org/pages/working-with-pgp-signatures.html).
+Follow [Sonatype's GPG instructions](https://central.sonatype.org/pages/working-with-pgp-signatures.html).
 
 Install `gpg-agent` (needed below) e.g. on Ubuntu via: `sudo apt-get install gnupg-agent`
 
 **Login configuration**
 
-Create the `settings.xml` in the `$HOME/.m2/` directory as described in their [instructions](http://central.sonatype.org/pages/apache-maven.html).
+Create the `settings.xml` in the `$HOME/.m2/` directory as described in their [instructions](https://central.sonatype.org/pages/apache-maven.html).
 
 ### Deploy & Release
 

diff --git a/doc/meetups_notes/06-14-2018.md b/doc/meetups_notes/06-14-2018.md
@@ -56,7 +56,7 @@ Meeting started at 8am PDT on Zoom.
 
 ### New Vitess Logo / Logo Changes
 
-We kicked off the meeting talking about the first agenda item, *Vitess's new logo*. The new logo was mooted in the first place because of its current similarites to [Vivid IT Corp](http://www.vividitcorp.com/).
+We kicked off the meeting talking about the first agenda item, *Vitess's new logo*. The new logo was mooted in the first place because of its current similarites to [Vivid IT Corp](https://www.vividitcorp.com/).
 
 Based on [logos](https://docs.google.com/forms/d/e/1FAIpQLScp5hGY98vpRMxs3oRT8c-XJ_b04ei6uCFiYiQe3nDunFbyuw/viewform) created with CNCF's help, logos 1 and 4 got the highest no of votes.
 

diff --git a/doc/vtctlReference.md b/doc/vtctlReference.md
@@ -2343,7 +2343,7 @@ Blocks the action queue on the specified tablet for the specified amount of time
 #### Arguments
 
 * <code>&lt;tablet alias&gt;</code> &ndash; Required. A Tablet Alias uniquely identifies a vttablet. The argument value is in the format <code>&lt;cell name&gt;-&lt;uid&gt;</code>.
-* <code>&lt;duration&gt;</code> &ndash; Required. The amount of time that the action queue should be blocked. The value is a string that contains a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms" or "1h45m". See the definition of the Go language's <a href="http://golang.org/pkg/time/#ParseDuration">ParseDuration</a> function for more details. Note that, in practice, the value should be a positively signed value.
+* <code>&lt;duration&gt;</code> &ndash; Required. The amount of time that the action queue should be blocked. The value is a string that contains a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms" or "1h45m". See the definition of the Go language's <a href="https://golang.org/pkg/time/#ParseDuration">ParseDuration</a> function for more details. Note that, in practice, the value should be a positively signed value.
 
 #### Errors