Docs: HTTP -> HTTPS (fixes #9768) (#9768)

URLs were updated to use HTTPS protocol tag: Docs
eslint · Dec 27, 2017 · db431cb · db431cb
1 parent cbf0fb9
commit db431cb
Show file tree

Hide file tree

Showing 34 changed files with 61 additions and 61 deletions.
diff --git a/README.md b/README.md
@@ -156,7 +156,7 @@ Before filing an issue, please be sure to read the guidelines for what you're re
 
 ## Semantic Versioning Policy
 
-ESLint follows [semantic versioning](http://semver.org). However, due to the nature of ESLint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy for ESLint:
+ESLint follows [semantic versioning](https://semver.org). However, due to the nature of ESLint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy for ESLint:
 
 * Patch release (intended to not break your lint build)
     * A bug fix in a rule that results in ESLint reporting fewer errors.

diff --git a/docs/about/index.md b/docs/about/index.md
@@ -8,8 +8,8 @@ The primary reason ESLint was created was to allow developers to create their ow
 
 ESLint is written using Node.js to provide a fast runtime environment and easy installation via [npm][].
 
-[linting]: http://en.wikipedia.org/wiki/Lint_(software)
-[npm]: http://npmjs.org/
+[linting]: https://en.wikipedia.org/wiki/Lint_(software)
+[npm]: https://npmjs.org/
 
 ## Philosophy
 

diff --git a/docs/developer-guide/code-conventions.md b/docs/developer-guide/code-conventions.md
@@ -1,6 +1,6 @@
 # Code Conventions
 
-Programming language style guides are important for the long-term maintainability of software. This guide is based on the [Code Conventions for the Java Programming Language](http://java.sun.com/docs/codeconv/) and [Douglas Crockford's Code Conventions for the JavaScript Programming Language](http://javascript.crockford.com/code.html). Modifications have been made due to my personal experience and preferences.
+Programming language style guides are important for the long-term maintainability of software. This guide is based on the [Code Conventions for the Java Programming Language](https://java.sun.com/docs/codeconv/) and [Douglas Crockford's Code Conventions for the JavaScript Programming Language](http://javascript.crockford.com/code.html). Modifications have been made due to my personal experience and preferences.
 
 ## File Format
 

diff --git a/docs/developer-guide/development-environment.md b/docs/developer-guide/development-environment.md
@@ -4,7 +4,7 @@ ESLint has a very lightweight development environment that makes updating code f
 
 ## Step 1: Install Node.js
 
-Go to <http://nodejs.org/> to download and install the latest stable version for your operating system.
+Go to <https://nodejs.org/> to download and install the latest stable version for your operating system.
 
 Most of the installers come with [npm](https://www.npmjs.com/) already installed, but if for some reason it doesn't work on your system, you can install it manually using the instructions on the site.
 

diff --git a/docs/developer-guide/source-code.md b/docs/developer-guide/source-code.md
@@ -1,18 +1,18 @@
 # Source Code
 
-ESLint is hosted at [GitHub](https://github.com/eslint/eslint) and uses [Git](http://git-scm.com/) for source control. In order to obtain the source code, you must first install Git on your system. Instructions for installing and setting up Git can be found at [http://help.github.com/set-up-git-redirect](http://help.github.com/set-up-git-redirect).
+ESLint is hosted at [GitHub](https://github.com/eslint/eslint) and uses [Git](https://git-scm.com/) for source control. In order to obtain the source code, you must first install Git on your system. Instructions for installing and setting up Git can be found at [https://help.github.com/articles/set-up-git/](https://help.github.com/articles/set-up-git/).
 
 If you simply want to create a local copy of the source to play with, you can clone the main repository using this command:
 
     git clone git://github.com/eslint/eslint.git
 
-If you're planning on contributing to ESLint, then it's a good idea to fork the repository. You can find instructions for forking a repository at [http://help.github.com/fork-a-repo/](http://help.github.com/fork-a-repo/). After forking the ESLint repository, you'll want to create a local copy of your fork.
+If you're planning on contributing to ESLint, then it's a good idea to fork the repository. You can find instructions for forking a repository at [https://help.github.com/articles/fork-a-repo/](https://help.github.com/articles/fork-a-repo/). After forking the ESLint repository, you'll want to create a local copy of your fork.
 
 ## Start Developing
 
 Before you can get started developing, you'll need to have a couple of things installed:
 
-* [Node.JS](http://nodejs.org)
+* [Node.JS](https://nodejs.org)
 * [npm](https://www.npmjs.com/)
 
 Once you have a local copy and have Node.JS and npm installed, you'll need to install the ESLint dependencies:

diff --git a/docs/developer-guide/unit-tests.md b/docs/developer-guide/unit-tests.md
@@ -1,6 +1,6 @@
 # Unit Tests
 
-Most parts of ESLint have unit tests associated with them. Unit tests are written using [Mocha](http://mochajs.org/) and are required when making contributions to ESLint. You'll find all of the unit tests in the `tests` directory.
+Most parts of ESLint have unit tests associated with them. Unit tests are written using [Mocha](https://mochajs.org/) and are required when making contributions to ESLint. You'll find all of the unit tests in the `tests` directory.
 
 When you first get the source code, you need to run `npm install` once initially to set ESLint for development. Once you've done that, you can run the tests via:
 

diff --git a/docs/maintainer-guide/governance.md b/docs/maintainer-guide/governance.md
@@ -152,4 +152,4 @@ or else the discussion will continue. Simple majority wins.
 
 This work is a derivative of [YUI Contributor Model](https://github.com/yui/yui3/wiki/Contributor-Model) and the [Node.js Project Governance Model](https://github.com/nodejs/node/blob/master/GOVERNANCE.md).
 
-This work is licensed under a [Creative Commons Attribution-ShareAlike 2.0 UK: England & Wales License](http://creativecommons.org/licenses/by-sa/2.0/uk/).
+This work is licensed under a [Creative Commons Attribution-ShareAlike 2.0 UK: England & Wales License](https://creativecommons.org/licenses/by-sa/2.0/uk/).
diff --git a/docs/maintainer-guide/releases.md b/docs/maintainer-guide/releases.md
@@ -2,7 +2,7 @@
 
 Releases are when a project formally publishes a new version so the community can use it. There are two types of releases:
 
-* Regular releases that follow [semantic versioning](http://semver.org/) and are considered production-ready.
+* Regular releases that follow [semantic versioning](https://semver.org/) and are considered production-ready.
 * Prereleases that are not considered production-ready and are intended to give the community a preview of upcoming changes.
 
 ## Release Team

diff --git a/docs/rules/array-callback-return.md b/docs/rules/array-callback-return.md
@@ -16,16 +16,16 @@ This rule enforces usage of `return` statement in callbacks of array's methods.
 
 This rule finds callback functions of the following methods, then checks usage of `return` statement.
 
-* [`Array.from`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.from)
-* [`Array.prototype.every`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.every)
-* [`Array.prototype.filter`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.filter)
-* [`Array.prototype.find`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.find)
-* [`Array.prototype.findIndex`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.findIndex )
-* [`Array.prototype.map`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.map)
-* [`Array.prototype.reduce`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.reduce)
-* [`Array.prototype.reduceRight`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.reduceRight)
-* [`Array.prototype.some`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.some)
-* [`Array.prototype.sort`](http://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.sort)
+* [`Array.from`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.from)
+* [`Array.prototype.every`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.every)
+* [`Array.prototype.filter`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.filter)
+* [`Array.prototype.find`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.find)
+* [`Array.prototype.findIndex`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.findIndex )
+* [`Array.prototype.map`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.map)
+* [`Array.prototype.reduce`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.reduce)
+* [`Array.prototype.reduceRight`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.reduceRight)
+* [`Array.prototype.some`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.some)
+* [`Array.prototype.sort`](https://www.ecma-international.org/ecma-262/6.0/#sec-array.prototype.sort)
 * And above of typed arrays.
 
 Examples of **incorrect** code for this rule:

diff --git a/docs/rules/eqeqeq.md b/docs/rules/eqeqeq.md
@@ -2,7 +2,7 @@
 
 It is considered good practice to use the type-safe equality operators `===` and `!==` instead of their regular counterparts `==` and `!=`.
 
-The reason for this is that `==` and `!=` do type coercion which follows the rather obscure [Abstract Equality Comparison Algorithm](http://www.ecma-international.org/ecma-262/5.1/#sec-11.9.3).
+The reason for this is that `==` and `!=` do type coercion which follows the rather obscure [Abstract Equality Comparison Algorithm](https://www.ecma-international.org/ecma-262/5.1/#sec-11.9.3).
 For instance, the following statements are all considered `true`:
 
 * `[] == false`

diff --git a/docs/rules/guard-for-in.md b/docs/rules/guard-for-in.md
@@ -45,5 +45,5 @@ for (key in foo) {
 
 ## Further Reading
 
-* [Exploring JavaScript for-in loops](http://javascriptweblog.wordpress.com/2011/01/04/exploring-javascript-for-in-loops/)
+* [Exploring JavaScript for-in loops](https://javascriptweblog.wordpress.com/2011/01/04/exploring-javascript-for-in-loops/)
 * [The pitfalls of using objects as maps in JavaScript](http://2ality.com/2012/01/objects-as-maps.html)
diff --git a/docs/rules/lines-around-directive.md b/docs/rules/lines-around-directive.md
@@ -2,7 +2,7 @@
 
 This rule was **deprecated** in ESLint v4.0.0 and replaced by the [padding-line-between-statements](padding-line-between-statements.md) rule.
 
-Directives are used in JavaScript to indicate to the execution environment that a script would like to opt into a feature such as `"strict mode"`. Directives are grouped together in a [directive prologue](http://www.ecma-international.org/ecma-262/7.0/#directive-prologue) at the top of either a file or function block and are applied to the scope in which they occur.
+Directives are used in JavaScript to indicate to the execution environment that a script would like to opt into a feature such as `"strict mode"`. Directives are grouped together in a [directive prologue](https://www.ecma-international.org/ecma-262/7.0/#directive-prologue) at the top of either a file or function block and are applied to the scope in which they occur.
 
 ```js
 // Strict mode is invoked for the entire script

diff --git a/docs/rules/max-nested-callbacks.md b/docs/rules/max-nested-callbacks.md
@@ -71,8 +71,8 @@ function handleFoo4() {
 ## Further Reading
 
 * [Control flow in Node.js](http://book.mixu.net/node/ch7.html)
-* [Control Flow in Node](http://howtonode.org/control-flow)
-* [Control Flow in Node Part II](http://howtonode.org/control-flow-part-ii)
+* [Control Flow in Node](https://howtonode.org/control-flow)
+* [Control Flow in Node Part II](https://howtonode.org/control-flow-part-ii)
 
 ## Related Rules
 

diff --git a/docs/rules/no-eval.md b/docs/rules/no-eval.md
@@ -139,8 +139,8 @@ global.eval("var a = 0");
 
 ## Further Reading
 
-* [Eval is Evil, Part One](http://blogs.msdn.com/b/ericlippert/archive/2003/11/01/53329.aspx)
-* [How evil is eval](http://javascriptweblog.wordpress.com/2010/04/19/how-evil-is-eval/)
+* [Eval is Evil, Part One](https://blogs.msdn.com/b/ericlippert/archive/2003/11/01/53329.aspx)
+* [How evil is eval](https://javascriptweblog.wordpress.com/2010/04/19/how-evil-is-eval/)
 
 ## Related Rules
 

diff --git a/docs/rules/no-extra-strict.md b/docs/rules/no-extra-strict.md
@@ -47,4 +47,4 @@ Examples of **correct** code for this rule:
 
 ## Further Reading
 
-* [The ECMAScript 5 Annotated Specification - Strict Mode](http://es5.github.io/#C)
+* [The ECMAScript 5 Annotated Specification - Strict Mode](https://es5.github.io/#C)
diff --git a/docs/rules/no-invalid-regexp.md b/docs/rules/no-invalid-regexp.md
@@ -61,4 +61,4 @@ new RegExp('.', 'yu')
 
 ## Further Reading
 
-* [Annotated ES5 §7.8.5 - Regular Expression Literals](http://es5.github.io/#x7.8.5)
+* [Annotated ES5 §7.8.5 - Regular Expression Literals](https://es5.github.io/#x7.8.5)
diff --git a/docs/rules/no-iterator.md b/docs/rules/no-iterator.md
@@ -40,5 +40,5 @@ var __iterator__ = foo; // Not using the `__iterator__` property.
 ## Further Reading
 
 * [MDN - Iterators and Generators](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Iterators_and_Generators)
-* [ECMAScript 6 compatibility table - Iterators](http://kangax.github.io/es5-compat-table/es6/#Iterators)
+* [ECMAScript 6 compatibility table - Iterators](https://kangax.github.io/es5-compat-table/es6/#Iterators)
 * [Deprecated and Obsolete Features](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Deprecated_and_obsolete_features#Object_methods)
diff --git a/docs/rules/no-mixed-requires.md b/docs/rules/no-mixed-requires.md
@@ -118,7 +118,7 @@ var async = require('async'),
 
 If you use a pattern such as [UMD][4] where the `require`d modules are not loaded in variable declarations, this rule will obviously do nothing for you.
 
-[1]: http://nodejs.org/api/modules.html#modules_core_modules
-[2]: http://nodejs.org/api/modules.html#modules_file_modules
-[3]: http://nodejs.org/api/modules.html#modules_loading_from_node_modules_folders
+[1]: https://nodejs.org/api/modules.html#modules_core_modules
+[2]: https://nodejs.org/api/modules.html#modules_file_modules
+[3]: https://nodejs.org/api/modules.html#modules_loading_from_node_modules_folders
 [4]: https://github.com/umdjs/umd
diff --git a/docs/rules/no-new-symbol.md b/docs/rules/no-new-symbol.md
@@ -45,4 +45,4 @@ This rule should not be used in ES3/5 environments.
 
 ## Further Reading
 
-* [Symbol Objects specification](http://www.ecma-international.org/ecma-262/6.0/#sec-symbol-objects)
+* [Symbol Objects specification](https://www.ecma-international.org/ecma-262/6.0/#sec-symbol-objects)
diff --git a/docs/rules/no-obj-calls.md b/docs/rules/no-obj-calls.md
@@ -2,11 +2,11 @@
 
 ECMAScript provides several global objects that are intended to be used as-is. Some of these objects look as if they could be constructors due their capitalization (such as `Math` and `JSON`) but will throw an error if you try to execute them as functions.
 
-The [ECMAScript 5 specification](http://es5.github.io/#x15.8) makes it clear that both `Math` and `JSON` cannot be invoked:
+The [ECMAScript 5 specification](https://es5.github.io/#x15.8) makes it clear that both `Math` and `JSON` cannot be invoked:
 
 > The Math object does not have a `[[Call]]` internal property; it is not possible to invoke the Math object as a function.
 
-And the [ECMAScript 2015 specification](http://www.ecma-international.org/ecma-262/6.0/index.html#sec-reflect-object) makes it clear that `Reflect` cannot be invoked:
+And the [ECMAScript 2015 specification](https://www.ecma-international.org/ecma-262/6.0/index.html#sec-reflect-object) makes it clear that `Reflect` cannot be invoked:
 
 > The Reflect object also does not have a `[[Call]]` internal method; it is not possible to invoke the Reflect object as a function.
 
@@ -38,4 +38,4 @@ var value = Reflect.get({ x: 1, y: 2 }, "x");
 
 ## Further Reading
 
-* [The Math Object](http://es5.github.io/#x15.8)
+* [The Math Object](https://es5.github.io/#x15.8)
diff --git a/docs/rules/no-process-env.md b/docs/rules/no-process-env.md
@@ -35,5 +35,5 @@ If prefer to use `process.env` throughout your project to retrieve values from e
 
 ## Further Reading
 
-* [How to store Node.js deployment settings/configuration files? - Stack Overflow](http://stackoverflow.com/questions/5869216/how-to-store-node-js-deployment-settings-configuration-files)
-* [Storing Node.js application config data - Ben Hall's blog](http://blog.benhall.me.uk/2012/02/storing-application-config-data-in/)
+* [How to store Node.js deployment settings/configuration files? - Stack Overflow](https://stackoverflow.com/questions/5869216/how-to-store-node-js-deployment-settings-configuration-files)
+* [Storing Node.js application config data - Ben Hall's blog](https://blog.benhall.me.uk/2012/02/storing-application-config-data-in/)
diff --git a/docs/rules/no-reserved-keys.md b/docs/rules/no-reserved-keys.md
@@ -50,4 +50,4 @@ If your code is only going to be executed in an ECMAScript 5 or higher environme
 
 ## Further Reading
 
-* [Reserved words as property names](http://kangax.github.io/compat-table/es5/#Reserved_words_as_property_names)
+* [Reserved words as property names](https://kangax.github.io/compat-table/es5/#Reserved_words_as_property_names)
diff --git a/docs/rules/no-script-url.md b/docs/rules/no-script-url.md
@@ -18,4 +18,4 @@ location.href = "javascript:void(0)";
 
 ## Further Reading
 
-* [What is the matter with script-targeted URLs?](http://stackoverflow.com/questions/13497971/what-is-the-matter-with-script-targeted-urls)
+* [What is the matter with script-targeted URLs?](https://stackoverflow.com/questions/13497971/what-is-the-matter-with-script-targeted-urls)
diff --git a/docs/rules/no-shadow-restricted-names.md b/docs/rules/no-shadow-restricted-names.md
@@ -36,8 +36,8 @@ function f(a, b){}
 
 ## Further Reading
 
-* [Annotated ES5 - §15.1.1](http://es5.github.io/#x15.1.1)
-* [Annotated ES5 - Annex C](http://es5.github.io/#C)
+* [Annotated ES5 - §15.1.1](https://es5.github.io/#x15.1.1)
+* [Annotated ES5 - Annex C](https://es5.github.io/#C)
 
 ## Related Rules
 

diff --git a/docs/rules/no-sparse-arrays.md b/docs/rules/no-sparse-arrays.md
@@ -47,4 +47,4 @@ If you want to use sparse arrays, then it is safe to disable this rule.
 
 ## Further Reading
 
-* [Inconsistent array literals](http://www.nczonline.net/blog/2007/09/09/inconsistent-array-literals/)
+* [Inconsistent array literals](https://www.nczonline.net/blog/2007/09/09/inconsistent-array-literals/)
diff --git a/docs/rules/no-undefined.md b/docs/rules/no-undefined.md
@@ -68,7 +68,7 @@ If you want to allow the use of `undefined` in your code, then you can safely tu
 ## Further Reading
 
 * [undefined - JavaScript \| MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/undefined)
-* [Understanding JavaScript’s ‘undefined’ \| JavaScript, JavaScript...](http://javascriptweblog.wordpress.com/2010/08/16/understanding-undefined-and-preventing-referenceerrors/)
+* [Understanding JavaScript’s ‘undefined’ \| JavaScript, JavaScript...](https://javascriptweblog.wordpress.com/2010/08/16/understanding-undefined-and-preventing-referenceerrors/)
 * [ECMA262 edition 5.1 &sect;15.1.1.3: undefined](https://es5.github.io/#x15.1.1.3)
 
 ## Related Rules

diff --git a/docs/rules/no-void.md b/docs/rules/no-void.md
@@ -65,7 +65,7 @@ If you intentionally use the `void` operator then you can disable this rule.
 ## Further Reading
 
 * [Mozilla Developer Network](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/void)
-* [Bad Parts: Appendix B - JavaScript: The Good Parts by Douglas Crockford](http://oreilly.com/javascript/excerpts/javascript-good-parts/bad-parts.html)
+* [Bad Parts: Appendix B - JavaScript: The Good Parts by Douglas Crockford](https://oreilly.com/javascript/excerpts/javascript-good-parts/bad-parts.html)
 
 ## Related Rules