HTTP -> HTTPS everywhere

closes: #1500

Author: defnull

AUTHORS

@@ -46,7 +46,7 @@ Thanks to all the people who found bugs, sent patches, spread the word, helped e
 * masklinn
 * Michael Labbe
 * Michael Soulier
-* `reddit <http://reddit.com/r/python>`_
+* `reddit <https://reddit.com/r/python>`_
 * Nicolas Vanhoren
 * Oz N Tiram
 * Robert Rollins

README.rst

@@ -1,5 +1,5 @@
-.. image:: http://bottlepy.org/docs/dev/_static/logo_nav.png
-  :target: http://bottlepy.org/
+.. image:: https://bottlepy.org/docs/dev/_static/logo_nav.png
+  :target: https://bottlepy.org/
   :alt: Bottle Logo
   :align: right
 
@@ -29,15 +29,15 @@
 Bottle: Python Web Framework
 ============================
 
-Bottle is a fast, simple and lightweight WSGI_ micro web-framework for Python_. It is distributed as a single file module and has no dependencies other than the `Python Standard Library <http://docs.python.org/library/>`_.
+Bottle is a fast, simple and lightweight WSGI_ micro web-framework for Python_. It is distributed as a single file module and has no dependencies other than the `Python Standard Library <https://docs.python.org/library/>`_.
 
 * **Routing:** Requests to function-call mapping with support for clean and dynamic URLs.
-* **Templates:** Fast `built-in template engine <http://bottlepy.org/docs/dev/tutorial.html#tutorial-templates>`_ and support for mako_, jinja2_ and cheetah_ templates.
+* **Templates:** Fast `built-in template engine <https://bottlepy.org/docs/dev/tutorial.html#tutorial-templates>`_ and support for mako_, jinja2_ and cheetah_ templates.
 * **Utilities:** Convenient access to form data, file uploads, cookies, headers and other HTTP features.
 * **Server:** Built-in development server and ready-to-use adapters for a wide range of WSGI_ capable HTTP server (e.g. gunicorn_, paste_ or cheroot_).
 
 
-Homepage and documentation: http://bottlepy.org
+Homepage and documentation: https://bottlepy.org
 
 
 Example: "Hello World" in a bottle

bottle.py

@@ -7,7 +7,7 @@
 template engines - all in a single file and with no dependencies other than the
 Python Standard Library.
 
-Homepage and documentation: http://bottlepy.org/
+Homepage and documentation: https://bottlepy.org/
 
 Copyright (c) 2009-2025, Marcel Hellkamp.
 License: MIT (see LICENSE for details)
@@ -3618,7 +3618,7 @@ def run(self, handler):
 
 
 class GunicornServer(ServerAdapter):
-    """ Untested. See http://gunicorn.org/configure.html for options. """
+    """ Untested. See https://gunicorn.org/configure.html for options. """
 
     def run(self, handler):
         from gunicorn.app.base import BaseApplication

docs/api.rst

@@ -187,8 +187,8 @@ You can write your own adapter for your favourite template engine or use one of
 Class                      URL                                  Decorator              Render function
 ========================   ==================================   ====================   ========================
 :class:`SimpleTemplate`    :doc:`stpl`                          :func:`view`           :func:`template`
-:class:`MakoTemplate`      http://www.makotemplates.org         :func:`mako_view`      :func:`mako_template`
-:class:`CheetahTemplate`   http://www.cheetahtemplate.org/      :func:`cheetah_view`   :func:`cheetah_template`
+:class:`MakoTemplate`      https://www.makotemplates.org         :func:`mako_view`      :func:`mako_template`
+:class:`CheetahTemplate`   https://www.cheetahtemplate.org/      :func:`cheetah_view`   :func:`cheetah_template`
 :class:`Jinja2Template`    https://jinja.palletsprojects.com/   :func:`jinja2_view`    :func:`jinja2_template`
 ========================   ==================================   ====================   ========================
 

docs/async.rst

@@ -1,12 +1,12 @@
 Asynchronous Applications
 =========================
 
-Asynchronous design patterns don't mix well with the synchronous nature of `WSGI <http://www.python.org/dev/peps/pep-3333/>`_. This is why most asynchronous frameworks (tornado, twisted, ...) implement a specialized API to expose their asynchronous features. Bottle is a WSGI framework and shares the synchronous nature of WSGI, but thanks to the awesome `gevent project <http://www.gevent.org/>`_, it is still possible to write asynchronous applications with bottle. This article documents the usage of Bottle with Asynchronous WSGI.
+Asynchronous design patterns don't mix well with the synchronous nature of `WSGI <https://www.python.org/dev/peps/pep-3333/>`_. This is why most asynchronous frameworks (tornado, twisted, ...) implement a specialized API to expose their asynchronous features. Bottle is a WSGI framework and shares the synchronous nature of WSGI, but thanks to the awesome `gevent project <https://www.gevent.org/>`_, it is still possible to write asynchronous applications with bottle. This article documents the usage of Bottle with Asynchronous WSGI.
 
 The Limits of Synchronous WSGI
 -------------------------------
 
-Briefly worded, the `WSGI specification (pep 3333) <http://www.python.org/dev/peps/pep-3333/>`_ defines a request/response circle as follows: The application callable is invoked once for each request and must return a body iterator. The server then iterates over the body and writes each chunk to the socket. As soon as the body iterator is exhausted, the client connection is closed.
+Briefly worded, the `WSGI specification (pep 3333) <https://www.python.org/dev/peps/pep-3333/>`_ defines a request/response circle as follows: The application callable is invoked once for each request and must return a body iterator. The server then iterates over the body and writes each chunk to the socket. As soon as the body iterator is exhausted, the client connection is closed.
 
 Simple enough, but there is a snag: All this happens synchronously. If your application needs to wait for data (IO, sockets, databases, ...), it must either yield empty strings (busy wait) or block the current thread. Both solutions occupy the handling thread and prevent it from answering new requests. There is consequently only one ongoing request per thread.
 
@@ -17,7 +17,7 @@ Greenlets to the rescue
 
 Most servers limit the size of their worker pools to a relatively low number of concurrent threads, due to the high overhead involved in switching between and creating new threads. While threads are cheap compared to processes (forks), they are still expensive to create for each new connection.
 
-The `gevent <http://www.gevent.org/>`_ module adds *greenlets* to the mix. Greenlets behave similar to traditional threads, but are very cheap to create. A gevent-based server can spawn thousands of greenlets (one for each connection) with almost no overhead. Blocking individual greenlets has no impact on the servers ability to accept new requests. The number of concurrent connections is virtually unlimited.
+The `gevent <https://www.gevent.org/>`_ module adds *greenlets* to the mix. Greenlets behave similar to traditional threads, but are very cheap to create. A gevent-based server can spawn thousands of greenlets (one for each connection) with almost no overhead. Blocking individual greenlets has no impact on the servers ability to accept new requests. The number of concurrent connections is virtually unlimited.
 
 This makes creating asynchronous applications incredibly easy, because they look and feel like synchronous applications. A gevent-based server is actually not asynchronous, but massively multi-threaded. Here is an example::
 
@@ -51,7 +51,7 @@ If you run this script and point your browser to ``http://localhost:8080/stream`
 Event Callbacks
 ---------------
 
-A very common design pattern in asynchronous frameworks (including tornado, twisted, node.js and friends) is to use non-blocking APIs and bind callbacks to asynchronous events. The socket object is kept open until it is closed explicitly to allow callbacks to write to the socket at a later point. Here is an example based on the `tornado library <http://www.tornadoweb.org/documentation#non-blocking-asynchronous-requests>`_::
+A very common design pattern in asynchronous frameworks (including tornado, twisted, node.js and friends) is to use non-blocking APIs and bind callbacks to asynchronous events. The socket object is kept open until it is closed explicitly to allow callbacks to write to the socket at a later point. Here is an example based on the `tornado library <https://www.tornadoweb.org/documentation#non-blocking-asynchronous-requests>`_::
 
     class MainHandler(tornado.web.RequestHandler):
         @tornado.web.asynchronous
@@ -64,7 +64,7 @@ The main benefit is that the request handler terminates early. The handling thre
 
 With Gevent+WSGI, things are different: First, terminating early has no benefit because we have an unlimited pool of (pseudo)threads to accept new connections. Second, we cannot terminate early because that would close the socket (as required by WSGI). Third, we must return an iterable to conform to WSGI.
 
-In order to conform to the WSGI standard, all we have to do is to return a body iterable that we can write to asynchronously. With the help of `gevent.queue <http://www.gevent.org/gevent.queue.html>`_, we can *simulate* a detached socket and rewrite the previous example as follows::
+In order to conform to the WSGI standard, all we have to do is to return a body iterable that we can write to asynchronously. With the help of `gevent.queue <https://www.gevent.org/gevent.queue.html>`_, we can *simulate* a detached socket and rewrite the previous example as follows::
 
     @route('/fetch')
     def fetch():
@@ -83,7 +83,7 @@ Finally: WebSockets
 
 Lets forget about the low-level details for a while and speak about WebSockets. Since you are reading this article, you probably know what WebSockets are: A bidirectional communication channel between a browser (client) and a web application (server).
 
-Thankfully the `gevent-websocket <http://pypi.python.org/pypi/gevent-websocket/>`_ package does all the hard work for us. Here is a simple WebSocket endpoint that receives messages and just sends them back to the client::
+Thankfully the `gevent-websocket <https://pypi.python.org/pypi/gevent-websocket/>`_ package does all the hard work for us. Here is a simple WebSocket endpoint that receives messages and just sends them back to the client::
 
     from bottle import request, Bottle, abort
     app = Bottle()

docs/changelog.rst

@@ -123,7 +123,7 @@ These changes might require special care when updating.
 
 * :class:`Bottle` instances are now context managers. If used in a with-statement, the default application changes to the specific instance and the shortcuts for many instance methods can be used.
 * Added support for ``PATCH`` requests and the :meth:`Bottle.patch` decorator.
-* Added `aiohttp <http://aiohttp.readthedocs.io/en/stable/>`_ and `uvloop <https://github.com/MagicStack/uvloop>`_ server adapters.
+* Added `aiohttp <https://aiohttp.readthedocs.io/en/stable/>`_ and `uvloop <https://github.com/MagicStack/uvloop>`_ server adapters.
 * Added command-line arguments for config from json or ini files.
 * :meth:`Bottle.mount` now recognizes instances of :class:`Bottle` and mounts them with significantly less overhead than other WSGI applications.
 * The :attr:`Request.json <BaseRequest.json>` property now accepts ``application/json-rpc`` requests.
@@ -145,7 +145,7 @@ Release 0.12
 * Removed the ``Request.MAX_PARAMS`` limit. The hash collision bug in CPythons dict() implementation was fixed over a year ago. If you are still using Python 2.5 in production, consider upgrading or at least make sure that you get security fixed from your distributor.
 * New :class:`ConfigDict` API (see :doc:`configuration`)
 
-More information can be found in this `development blog post <http://blog.bottlepy.org/2013/07/19/preview-bottle-012.html>`_.
+More information can be found in this `development blog post <https://blog.bottlepy.org/2013/07/19/preview-bottle-012.html>`_.
 
 
 Release 0.11
@@ -154,7 +154,7 @@ Release 0.11
 * Native support for Python 2.x and 3.x syntax. No need to run 2to3 anymore.
 * Support for partial downloads (``Range`` header) in :func:`static_file`.
 * The new :class:`ResourceManager` interface helps locating files bundled with an application.
-* Added a server adapter for `waitress <http://docs.pylonsproject.org/projects/waitress/en/latest/>`_.
+* Added a server adapter for `waitress <https://docs.pylonsproject.org/projects/waitress/en/latest/>`_.
 * New :meth:`Bottle.merge` method to install all routes from one application into another.
 * New :attr:`Request.app <BaseRequest.app>` property to get the application object that handles a request.
 * Added :meth:`FormsDict.decode()` to get an all-unicode version (needed by WTForms).
@@ -212,7 +212,7 @@ Release 0.9
 
 * A brand new plugin-API. See :doc:`plugins/index` and :doc:`plugins/dev` for details.
 * The :func:`route` decorator got a lot of new features. See :meth:`Bottle.route` for details.
-* New server adapters for `gevent <http://www.gevent.org/>`_, `meinheld <http://meinheld.org/>`_ and `bjoern <https://github.com/jonashaag/bjoern>`_.
+* New server adapters for `gevent <https://www.gevent.org/>`_, `meinheld <https://meinheld.org/>`_ and `bjoern <https://github.com/jonashaag/bjoern>`_.
 * Support for SimpleTAL templates.
 * Better runtime exception handling for mako templates in debug mode.
 * Lots of documentation, fixes and small improvements.

docs/deployment.rst

@@ -2,25 +2,25 @@
 .. currentmodule:: bottle
 
 .. _flup: https://pypi.org/project/flup/
-.. _gae: http://code.google.com/appengine/docs/python/overview.html
-.. _wsgiref: http://docs.python.org/library/wsgiref.html
+.. _gae: https://code.google.com/appengine/docs/python/overview.html
+.. _wsgiref: https://docs.python.org/library/wsgiref.html
 .. _cherrypy: https://cherrypy.dev/
 .. _paste: https://pythonpaste.readthedocs.io/
-.. _gunicorn: http://pypi.python.org/pypi/gunicorn
-.. _tornado: http://www.tornadoweb.org/
-.. _twisted: http://twistedmatrix.com/
-.. _diesel: http://dieselweb.org/
-.. _meinheld: http://pypi.python.org/pypi/meinheld
-.. _bjoern: http://pypi.python.org/pypi/bjoern
-.. _gevent: http://www.gevent.org/
-.. _eventlet: http://eventlet.net/
-.. _waitress: http://readthedocs.org/docs/waitress/en/latest/
-.. _apache: http://httpd.apache.org/
-.. _mod_wsgi: http://code.google.com/p/modwsgi/
-.. _pound: http://www.apsis.ch/pound
-.. _nginx: http://nginx.org/
-.. _lighttpd: http://www.lighttpd.net/
-.. _cherokee: http://cherokee-project.com/
+.. _gunicorn: https://pypi.python.org/pypi/gunicorn
+.. _tornado: https://www.tornadoweb.org/
+.. _twisted: https://twistedmatrix.com/
+.. _diesel: https://dieselweb.org/
+.. _meinheld: https://pypi.python.org/pypi/meinheld
+.. _bjoern: https://pypi.python.org/pypi/bjoern
+.. _gevent: https://www.gevent.org/
+.. _eventlet: https://eventlet.net/
+.. _waitress: https://readthedocs.org/docs/waitress/en/latest/
+.. _apache: https://httpd.apache.org/
+.. _mod_wsgi: https://code.google.com/p/modwsgi/
+.. _pound: https://www.apsis.ch/pound
+.. _nginx: https://nginx.org/
+.. _lighttpd: https://www.lighttpd.net/
+.. _cherokee: https://cherokee-project.com/
 .. _uWSGI: https://uwsgi-docs.readthedocs.io/en/latest/
 .. _cheroot: https://cheroot.cherrypy.dev/
 
@@ -41,7 +41,7 @@ To get your application available to the outside world, specify the IP the serve
 Scaling for Production
 ================================================================================
 
-The built-in development server is base on `wsgiref WSGIServer <http://docs.python.org/library/wsgiref.html#module-wsgiref.simple_server>`_, which is a very simple non-threading HTTP server implementation. This is perfectly fine for development, but may become a performance bottleneck when server load increases.
+The built-in development server is base on `wsgiref WSGIServer <https://docs.python.org/library/wsgiref.html#module-wsgiref.simple_server>`_, which is a very simple non-threading HTTP server implementation. This is perfectly fine for development, but may become a performance bottleneck when server load increases.
 
 The easiest way to increase performance is to install a multi-threaded server library like cheroot_ or gunicorn_ and tell Bottle to use that instead of the single-threaded wsgiref server::
 

docs/development.rst

@@ -20,13 +20,13 @@ The bottle `development repository <https://github.com/bottlepy/bottle>`_ and th
 
 * **git:** ``git clone git://github.com/bottlepy/bottle.git``
 * **git/https:** ``git clone https://github.com/bottlepy/bottle.git``
-* **Download:** Development branch as `tar archive <http://github.com/bottlepy/bottle/tarball/master>`_ or `zip file <http://github.com/bottlepy/bottle/zipball/master>`_.
+* **Download:** Development branch as `tar archive <https://github.com/bottlepy/bottle/tarball/master>`_ or `zip file <https://github.com/bottlepy/bottle/zipball/master>`_.
 
 
 Releases and Updates
 --------------------
 
-Bottle is released at irregular intervals and distributed through `PyPI <http://pypi.python.org/pypi/bottle>`_. Release candidates are only available from the git repository mentioned above. Debian and many other Linux distributions offer packages.
+Bottle is released at irregular intervals and distributed through `PyPI <https://pypi.python.org/pypi/bottle>`_. Release candidates are only available from the git repository mentioned above. Debian and many other Linux distributions offer packages.
 
 The Bottle version number splits into three parts (**major.minor.patch**) but does not follow the rules of `SemVer <https://semver.org/>`_. Instead, you can usually rely on the following rules:
 

docs/faq.rst

@@ -1,12 +1,12 @@
 .. currentmodule:: bottle
 
 .. _beaker: https://beaker.readthedocs.io/en/latest/
-.. _mod_python: http://www.modpython.org/
-.. _mod_wsgi: http://code.google.com/p/modwsgi/
+.. _mod_python: https://www.modpython.org/
+.. _mod_wsgi: https://code.google.com/p/modwsgi/
 .. _paste: https://pythonpaste.readthedocs.io/
 .. _pylons: https://pylonsproject.org/
-.. _gevent: http://www.gevent.org/
-.. _heroku: http://heroku.com
+.. _gevent: https://www.gevent.org/
+.. _heroku: https://heroku.com
 .. _django: https://www.djangoproject.com/
 .. _werkzeug: https://werkzeug.palletsprojects.com/en/3.0.x/
 
@@ -213,7 +213,7 @@ or add a ``before_request`` hook to strip the trailing slashes::
 
 .. rubric:: Footnotes
 
-.. [1] Because they are. See <http://www.ietf.org/rfc/rfc3986.txt>
+.. [1] Because they are. See <https://www.ietf.org/rfc/rfc3986.txt>
 
 
 Keep-alive requests
@@ -300,11 +300,11 @@ Heroku_, a popular cloud application platform now provides support
 for running Python applications on their infrastructure. 
 
 This recipe is based upon the `Heroku Quickstart 
-<http://devcenter.heroku.com/articles/quickstart>`_, 
+<https://devcenter.heroku.com/articles/quickstart>`_, 
 with Bottle specific code replacing the 
-`Write Your App <http://devcenter.heroku.com/articles/python#write_your_app>`_ 
+`Write Your App <https://devcenter.heroku.com/articles/python#write_your_app>`_ 
 section of the `Getting Started with Python on Heroku/Cedar 
-<http://devcenter.heroku.com/articles/python>`_ guide::
+<https://devcenter.heroku.com/articles/python>`_ guide::
 
     import os
     from bottle import route, run