mirror of
https://github.com/django/django.git
synced 2025-10-30 17:16:10 +00:00
[2.0.x] Updated various links in docs to use HTTPS.
Backport of 7c81b28ebc from master
This commit is contained in:
@@ -68,7 +68,7 @@ to handle high loads at LiveJournal.com and subsequently open-sourced by
|
||||
Danga Interactive. It is used by sites such as Facebook and Wikipedia to
|
||||
reduce database access and dramatically increase site performance.
|
||||
|
||||
__ http://memcached.org/
|
||||
__ https://memcached.org/
|
||||
|
||||
Memcached runs as a daemon and is allotted a specified amount of RAM. All it
|
||||
does is provide a fast interface for adding, retrieving and deleting data in
|
||||
@@ -1265,7 +1265,7 @@ Here are some more examples:
|
||||
The full list of known directives can be found in the `IANA registry`_
|
||||
(note that not all of them apply to responses).
|
||||
|
||||
.. _IANA registry: http://www.iana.org/assignments/http-cache-directives/http-cache-directives.xhtml
|
||||
.. _IANA registry: https://www.iana.org/assignments/http-cache-directives/http-cache-directives.xhtml
|
||||
|
||||
If you want to use headers to disable caching altogether,
|
||||
:func:`~django.views.decorators.cache.never_cache` is a view decorator that
|
||||
|
||||
@@ -98,7 +98,7 @@ can then look it up in the database. There are a variety of third-party
|
||||
libraries which are designed to help with this process.
|
||||
|
||||
.. _Elastic: https://www.elastic.co/
|
||||
.. _Solr: http://lucene.apache.org/solr/
|
||||
.. _Solr: https://lucene.apache.org/solr/
|
||||
|
||||
PostgreSQL support
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@@ -12,7 +12,7 @@ There's no ``.php`` or ``.cgi`` required, and certainly none of that
|
||||
See `Cool URIs don't change`_, by World Wide Web creator Tim Berners-Lee, for
|
||||
excellent arguments on why URLs should be clean and usable.
|
||||
|
||||
.. _Cool URIs don't change: http://www.w3.org/Provider/Style/URI
|
||||
.. _Cool URIs don't change: https://www.w3.org/Provider/Style/URI
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
@@ -48,7 +48,7 @@ here's a simplified definition:
|
||||
|
||||
More details can be found in the `W3C Web Internationalization FAQ`_, the `Wikipedia article`_ or the `GNU gettext documentation`_.
|
||||
|
||||
.. _W3C Web Internationalization FAQ: http://www.w3.org/International/questions/qa-i18n
|
||||
.. _W3C Web Internationalization FAQ: https://www.w3.org/International/questions/qa-i18n
|
||||
.. _GNU gettext documentation: https://www.gnu.org/software/gettext/manual/gettext.html#Concepts
|
||||
.. _Wikipedia article: https://en.wikipedia.org/wiki/Internationalization_and_localization
|
||||
|
||||
|
||||
@@ -1686,7 +1686,7 @@ This is only needed for people who either want to extract message IDs or compile
|
||||
message files (``.po``). Translation work itself just involves editing existing
|
||||
files of this type, but if you want to create your own message files, or want to
|
||||
test or compile a changed message file, download `a precompiled binary
|
||||
installer <http://mlocati.github.io/gettext-iconv-windows/>`_.
|
||||
installer <https://mlocati.github.io/articles/gettext-iconv-windows.html>`_.
|
||||
|
||||
You may also use ``gettext`` binaries you have obtained elsewhere, so long as
|
||||
the ``xgettext --version`` command works properly. Do not attempt to use Django
|
||||
|
||||
@@ -59,7 +59,7 @@ very well with `nginx`_. Additionally, Django follows the WSGI spec
|
||||
(:pep:`3333`), which allows it to run on a variety of server platforms.
|
||||
|
||||
.. _Apache: https://httpd.apache.org/
|
||||
.. _nginx: http://nginx.org/
|
||||
.. _nginx: https://nginx.org/
|
||||
.. _mod_wsgi: http://www.modwsgi.org/
|
||||
|
||||
.. _database-installation:
|
||||
|
||||
@@ -410,15 +410,15 @@ performance gains for your application to outweigh the potential risks.
|
||||
|
||||
With these caveats in mind, you should be aware of:
|
||||
|
||||
`PyPy <http://pypy.org/>`_
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
`PyPy <https://pypy.org/>`_
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
`PyPy <http://pypy.org/>`_ is an implementation of Python in Python itself (the
|
||||
'standard' Python implementation is in C). PyPy can offer substantial
|
||||
`PyPy <https://pypy.org/>`_ is an implementation of Python in Python itself
|
||||
(the 'standard' Python implementation is in C). PyPy can offer substantial
|
||||
performance gains, typically for heavyweight applications.
|
||||
|
||||
A key aim of the PyPy project is `compatibility
|
||||
<http://pypy.org/compat.html>`_ with existing Python APIs and libraries.
|
||||
<https://pypy.org/compat.html>`_ with existing Python APIs and libraries.
|
||||
Django is compatible, but you will need to check the compatibility of other
|
||||
libraries you rely on.
|
||||
|
||||
|
||||
@@ -164,8 +164,8 @@ Identifier Information
|
||||
serializer is only available if PyYAML_ is installed.
|
||||
========== ==============================================================
|
||||
|
||||
.. _json: http://json.org/
|
||||
.. _PyYAML: http://www.pyyaml.org/
|
||||
.. _json: https://json.org/
|
||||
.. _PyYAML: https://www.pyyaml.org/
|
||||
|
||||
XML
|
||||
---
|
||||
@@ -220,7 +220,7 @@ This example links the given user with the permission models with PKs 46 and 47.
|
||||
accepted in the XML 1.0 standard, the serialization will fail with a
|
||||
:exc:`ValueError` exception. Read also the W3C's explanation of `HTML,
|
||||
XHTML, XML and Control Codes
|
||||
<http://www.w3.org/International/questions/qa-controls>`_.
|
||||
<https://www.w3.org/International/questions/qa-controls>`_.
|
||||
|
||||
.. _serialization-formats-json:
|
||||
|
||||
@@ -308,7 +308,7 @@ The JSON serializer uses ``DjangoJSONEncoder`` for encoding. A subclass of
|
||||
|
||||
Support for :class:`~datetime.timedelta` was added.
|
||||
|
||||
.. _ecma-262: http://www.ecma-international.org/ecma-262/5.1/#sec-15.9.1.15
|
||||
.. _ecma-262: https://www.ecma-international.org/ecma-262/5.1/#sec-15.9.1.15
|
||||
|
||||
YAML
|
||||
----
|
||||
|
||||
@@ -740,5 +740,5 @@ listed here because of the ``source`` flag passed to the previous command.
|
||||
For more options like annotated HTML listings detailing missed lines, see the
|
||||
`coverage.py`_ docs.
|
||||
|
||||
.. _coverage.py: http://coverage.readthedocs.io/
|
||||
.. _coverage.py: https://coverage.readthedocs.io/
|
||||
.. _install coverage.py: https://pypi.python.org/pypi/coverage
|
||||
|
||||
@@ -161,7 +161,7 @@ Use the ``django.test.Client`` class to make requests.
|
||||
HTTP request from the browser to the server should be passed
|
||||
as ``HTTP_HOST``.
|
||||
|
||||
.. _CGI: http://www.w3.org/CGI/
|
||||
.. _CGI: https://www.w3.org/CGI/
|
||||
|
||||
If you already have the GET arguments in URL-encoded form, you can
|
||||
use that encoding instead of using the data argument. For example,
|
||||
|
||||
Reference in New Issue
Block a user