Merge pull request #314 from effigies/opportunistic_ssl

MRG: Use HTTPS for outside scripts/forms

https instead of http for web links where possible.

Author: matthew-brett

doc/source/_templates/indexsidebar.html

@@ -1,12 +1,12 @@
 <h3>Quick links</h3>
 
 <ul>
-    <li><a href="http://pypi.python.org/pypi/nibabel">Nibabel pypi</a></li>
-    <li><a href="http://github.com/nipy/nibabel">Git repository</a></li>
+    <li><a href="https://pypi.python.org/pypi/nibabel">Nibabel pypi</a></li>
+    <li><a href="https://github.com/nipy/nibabel">Git repository</a></li>
     <li><a href="http://mail.scipy.org/pipermail/nipy-devel">Mailing list archive</a></li>
 </ul>
 
-<script type="text/javascript" src="http://www.ohloh.net/projects/480908/widgets/project_partner_badge"></script>
+<script type="text/javascript" src="https://www.ohloh.net/projects/480908/widgets/project_partner_badge"></script>
 
 <h3>Search mailing list archive</h3>
 <script type="text/javascript">
@@ -15,7 +15,7 @@ <h3>Search mailing list archive</h3>
     curobj.q.value="site:mail.scipy.org/pipermail/nipy-devel/ "+curobj.userquery.value
 }
 </script>
-<form action="http://www.google.com/search" method="get" onSubmit="mlsearch(this)">
+<form action="https://www.google.com/search" method="get" onSubmit="mlsearch(this)">
 <input name="userquery" size="18" type="text" /> <input type="submit" value="Go" />
 <input name="q" type="hidden" />
 </form>

doc/source/_templates/layout.html

@@ -4,7 +4,7 @@
 {% block rootrellink %}
   <li><a href="http://nipy.org/">Community</a> |&nbsp;</li>
   <li><a href="{{ pathto('index') }}">NiBabel Home</a> |&nbsp;</li>
-  <li><a href="http://projects.scipy.org/mailman/listinfo/nipy-devel">Mailing list</a> |&nbsp;</li>
+  <li><a href="http://mail.scipy.org/mailman/listinfo/nipy-devel">Mailing list</a> |&nbsp;</li>
   <li><a href="legal.html">License</a> |&nbsp;</li>
 {% endblock %}
 

doc/source/conf.py

@@ -216,6 +216,7 @@
 # Output file base name for HTML help builder.
 htmlhelp_basename = 'nibabeldoc'
 
+mathjax_path = 'https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML'
 
 # -- Options for LaTeX output --------------------------------------------------
 
@@ -251,7 +252,7 @@
 
 
 # Example configuration for intersphinx: refer to the Python standard library.
-intersphinx_mapping = {'http://docs.python.org/': None}
+intersphinx_mapping = {'https://docs.python.org/': None}
 
 # Config of plot_directive
 plot_include_source = True

doc/source/devel/data_pkg_design.rst

@@ -288,7 +288,7 @@ There is an example nipy data package ``nipy-examplepkg`` in the
 ``examples`` directory of the NIPY repository.
 
 The machinery for creating and maintaining data packages is available at
-http://github.com/nipy/data-packaging.
+https://github.com/nipy/data-packaging.
 
 See the ``README.txt`` file there for more information.
 

doc/source/devel/data_pkg_discuss.rst

@@ -275,7 +275,7 @@ Issues
 ******
 
 From a brief scan of the `debian package management documentation
-<http://www.debian.org/doc/manuals/debian-reference/ch02.en.html>`_.
+<https://www.debian.org/doc/manuals/debian-reference/ch02.en.html>`_.
 
 Dependency management
 =====================
@@ -292,7 +292,7 @@ Authentication and validation
 For dependency and validation, see the `Debian secure apt`_ page. One related
 proposal would be:
 
-.. _Debian secure apt: http://wiki.debian.org/SecureApt
+.. _Debian secure apt: https://wiki.debian.org/SecureApt
 
 * Each package instantiation would carry a table of checksums for the files
   within.  Someone using this instantiation would check the checksums to confirm

doc/source/devel/make_release.rst

@@ -180,14 +180,14 @@ Release checklist
 
 * Force builds of the win32 and amd64 binaries from the buildbot. Go to pages:
 
-  * http://nipy.bic.berkeley.edu/builders/nibabel-bdist32-27
-  * http://nipy.bic.berkeley.edu/builders/nibabel-bdist32-34
-  * http://nipy.bic.berkeley.edu/builders/nibabel-bdist64-27
+  * https://nipy.bic.berkeley.edu/builders/nibabel-bdist32-27
+  * https://nipy.bic.berkeley.edu/builders/nibabel-bdist32-34
+  * https://nipy.bic.berkeley.edu/builders/nibabel-bdist64-27
 
   For each of these, enter the revision number (e.g. "2.0.0") in the field
   "Revision to build". Then get the built binaries in:
 
-  * http://nipy.bic.berkeley.edu/nibabel-dist
+  * https://nipy.bic.berkeley.edu/nibabel-dist
 
   and upload them to pypi with the admin files interface.
 
@@ -256,6 +256,6 @@ Release checklist
 
 * Announce to the mailing lists.
 
-.. _setuptools intro: http://packages.python.org/an_example_pypi_project/setuptools.html
+.. _setuptools intro: https://pythonhosted.org/an_example_pypi_project/setuptools.html
 
 .. include:: ../links_names.txt

doc/source/dicom/dcm2nii_algorithms.rst

@@ -9,7 +9,7 @@ by Chris Rorden, in Delphi (object orientated pascal).  It's part of
 Chris' popular mricron_ collection of programs.  The source appears to
 be best found on the `mricron NITRC site`_.  It's BSD_ licensed. 
 
-.. _mricron NITRC site: http://www.nitrc.org/projects/mricron
+.. _mricron NITRC site: https://www.nitrc.org/projects/mricron
 
 These are working notes looking at Chris' algorithms for working with
 DICOM.

doc/source/dicom/dicom_info.rst

@@ -37,7 +37,7 @@ Here is a selected list of other tools and relevant resources:
   headers, and has been tested with Philips, GE and Siemens data. It's
   not clear whether it yet supports the :ref:`dicom-mosaic`.  BSD_ style
   license.
-* The famous Philips cookbook: http://www.archive.org/details/DicomCookbook
+* The famous Philips cookbook: https://www.archive.org/details/DicomCookbook
 * http://dicom.online.fr/fr/dicomlinks.htm
 
 ===============

doc/source/gitwash/development_workflow.rst

@@ -150,7 +150,7 @@ Ask for your changes to be reviewed or merged
 When you are ready to ask for someone to review your code and consider a merge:
 
 #. Go to the URL of your forked repo, say
-   ``http://github.com/your-user-name/nibabel``.
+   ``https://github.com/your-user-name/nibabel``.
 #. Use the 'Switch Branches' dropdown menu near the top left of the page to
    select the branch with your changes:
 
@@ -183,7 +183,7 @@ Delete a branch on github
    git push origin :my-unwanted-branch
 
 (Note the colon ``:`` before ``test-branch``.  See also:
-http://github.com/guides/remove-a-remote-branch
+https://github.com/guides/remove-a-remote-branch
 
 Several people sharing a single repository
 ------------------------------------------
@@ -195,7 +195,7 @@ share it via github.
 First fork nibabel into your account, as from :ref:`forking`.
 
 Then, go to your forked repository github page, say
-``http://github.com/your-user-name/nibabel``
+``https://github.com/your-user-name/nibabel``
 
 Click on the 'Admin' button, and add anyone else to the repo as a
 collaborator:

doc/source/gitwash/forking_hell.rst

@@ -5,9 +5,9 @@ Making your own copy (fork) of nibabel
 ==========================================
 
 You need to do this only once.  The instructions here are very similar
-to the instructions at http://help.github.com/forking/ |emdash| please see
-that page for more detail.  We're repeating some of it here just to give the
-specifics for the nibabel_ project, and to suggest some default names.
+to the instructions at https://help.github.com/articles/fork-a-repo/ |emdash|
+please see that page for more detail.  We're repeating some of it here just to
+give the specifics for the nibabel_ project, and to suggest some default names.
 
 Set up and configure a github account
 =====================================