Change docs URLs to point to HTTPS versions of the sites

README.md

@@ -3,23 +3,23 @@ Composer - Dependency Management for PHP
 
 Composer is a dependency manager tracking local dependencies of your projects and libraries.
 
-See [http://getcomposer.org/](http://getcomposer.org/) for more information and documentation.
+See [https://getcomposer.org/](https://getcomposer.org/) for more information and documentation.
 
 [![Build Status](https://secure.travis-ci.org/composer/composer.png?branch=master)](http://travis-ci.org/composer/composer)
 
 Installation / Usage
 --------------------
 
-1. Download the [`composer.phar`](http://getcomposer.org/composer.phar) executable or use the installer.
+1. Download the [`composer.phar`](https://getcomposer.org/composer.phar) executable or use the installer.
 
     ``` sh
-    $ curl -s http://getcomposer.org/installer | php
+    $ curl -s https://getcomposer.org/installer | php
     ```
 
 
 2. Create a composer.json defining your dependencies. Note that this example is
 a short version for applications that are not meant to be published as packages
-themselves. To create libraries/packages please read the [guidelines](http://packagist.org/about).
+themselves. To create libraries/packages please read the [guidelines](https://packagist.org/about).
 
     ``` json
     {
@@ -30,7 +30,7 @@ themselves. To create libraries/packages please read the [guidelines](http://pac
     ```
 
 3. Run Composer: `php composer.phar install`
-4. Browse for more packages on [Packagist](http://packagist.org).
+4. Browse for more packages on [Packagist](https://packagist.org).
 
 Installation from Source
 ------------------------
@@ -39,7 +39,7 @@ To run tests, or develop Composer itself, you must use the sources and not the p
 file as described above.
 
 1. Run `git clone https://github.com/composer/composer.git`
-2. Download the [`composer.phar`](http://getcomposer.org/composer.phar) executable
+2. Download the [`composer.phar`](https://getcomposer.org/composer.phar) executable
 3. Run Composer to get the dependencies: `cd composer && php ../composer.phar install`
 
 You can now run Composer by executing the `bin/composer` script: `php /path/to/composer/bin/composer`
@@ -51,7 +51,7 @@ Since Composer works with the current working directory it is possible to instal
 in a system wide way.
 
 1. Change into a directory in your path like `cd /usr/local/bin`
-2. Get Composer `curl -s http://getcomposer.org/installer | php`
+2. Get Composer `curl -s https://getcomposer.org/installer | php`
 3. Make the phar executable `chmod a+x composer.phar`
 4. Change into a project directory `cd /path/to/my/project`
 5. Use Composer as you normally would `composer.phar install`

doc/00-intro.md

@@ -82,7 +82,7 @@ Then, just run `composer` in order to run Composer instead of `php composer.phar
 
 This is the easiest way to get Composer set up on your machine.
 
-Download and run [Composer-Setup.exe](http://getcomposer.org/Composer-Setup.exe),
+Download and run [Composer-Setup.exe](https://getcomposer.org/Composer-Setup.exe),
 it will install the latest Composer version and set up your PATH so that you can
 just call `composer` from any directory in your command line.
 

doc/01-basic-usage.md

@@ -4,7 +4,7 @@
 
 To install Composer, you just need to download the `composer.phar` executable.
 
-    $ curl -s http://getcomposer.org/installer | php
+    $ curl -s https://getcomposer.org/installer | php
 
 For the details, see the [Introduction](00-intro.md) chapter.
 
@@ -17,7 +17,7 @@ This should give you a list of available commands.
 > **Note:** You can also perform the checks only without downloading Composer
 > by using the `--check` option. For more information, just use `--help`.
 >
->     $ curl -s http://getcomposer.org/installer | php -- --help
+>     $ curl -s https://getcomposer.org/installer | php -- --help
 
 ## `composer.json`: Project Setup
 
@@ -128,13 +128,13 @@ the lock file with the new version.
 
 ## Packagist
 
-[Packagist](http://packagist.org/) is the main Composer repository. A Composer
+[Packagist](https://packagist.org/) is the main Composer repository. A Composer
 repository is basically a package source: a place where you can get packages
 from. Packagist aims to be the central repository that everybody uses. This
 means that you can automatically `require` any package that is available
 there.
 
-If you go to the [packagist website](http://packagist.org/) (packagist.org),
+If you go to the [packagist website](https://packagist.org/) (packagist.org),
 you can browse and search for packages.
 
 Any open source project using Composer should publish their packages on

doc/02-libraries.md

@@ -201,10 +201,10 @@ every time is cumbersome. You don't want to force all your users to do that.
 The other thing that you may have noticed is that we did not specify a package
 repository for `monolog/monolog`. How did that work? The answer is packagist.
 
-[Packagist](http://packagist.org/) is the main package repository for
+[Packagist](https://packagist.org/) is the main package repository for
 composer, and it is enabled by default. Anything that is published on
 packagist is available automatically through composer. Since monolog
-[is on packagist](http://packagist.org/packages/monolog/monolog), we can depend
+[is on packagist](https://packagist.org/packages/monolog/monolog), we can depend
 on it without having to specify any additional repositories.
 
 If we wanted to share `hello-world` with the world, we would publish it on

doc/articles/troubleshooting.md

@@ -27,7 +27,7 @@ This is a list of common pitfalls on using Composer, and how to avoid them.
    [minimum-stability](../04-schema.md#minimum-stability)**. To get started or be
    sure this is no issue, set `minimum-stability` to "dev".
 
-3. Packages **not coming from [Packagist](http://packagist.org/)** should
+3. Packages **not coming from [Packagist](https://packagist.org/)** should
    always be **defined in the root package** (the package depending on all
    vendors).