Repository: django-json-api/django-rest-framework-json-api

Issue:
Ensure that all external links are https
## Description of the Bug Report

There are several links in our website which refer to `http://` instead of `https://` even though most linked sites actually provide `https`. Those links should be updated to all use https.

Quick search 
```
$ git grep "http://" | grep -v testserver | grep -v localhost | grep -v "127.0.0.1" | grep -v example.com | grep -v example.org

CHANGELOG.md:Note that in line with [Django REST framework policy](http://www.django-rest-framework.org/topics/release-notes/),
CHANGELOG.md:* Add optional [jsonapi-style](http://jsonapi.org/format/) filter backends. See [usage docs](docs/usage.md#filter-backends)
CHANGELOG.md:  values from being formatted as attributes can contain any [json value](http://jsonapi.org/format/#document-resource-object-attributes).
README.rst:* Format specification: http://jsonapi.org/format/
README.rst:.. _JSON:API: http://jsonapi.org
README.rst:Read more at http://django-rest-framework-json-api.readthedocs.org/
docs/Makefile:$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
docs/make.bat:  echo.http://sphinx-doc.org/
docs/usage.md:Many features of the [JSON:API](http://jsonapi.org/format) format standard have been implemented using
docs/usage.md:# compiled regex that matches the allowed http://jsonapi.org/format/#query-parameters
docs/usage.md:`OrderingFilter` implements the [JSON:API `sort`](http://jsonapi.org/format/#fetching-sorting) and uses
docs/usage.md:`DjangoFilterBackend` implements a Django ORM-style [JSON:API `filter`](http://jsonapi.org/format/#fetching-filtering)
docs/usage.md:[JSON:API _recommendations_](http://jsonapi.org/recommendations/#filtering), including relationship
docs/usage.md:all exceptions will respond with the JSON:API [error format](http://jsonapi.org/format/#error-objects).
docs/usage.md:This package includes the ability (off by default) to automatically convert [JSON:API field names](http://jsonapi.org/format/#document-resource-object-fields) of requests and responses from the python/rest_framework's preferred underscore to
docs/usage.md:In the [JSON:API spec](http://jsonapi.org/format/#document-resource-objects),
docs/usage.md:[JSON:API spec](http://jsonapi.org/format/#fetching-relationships)).
docs/usage.md:[Resource Identifier Objects](http://jsonapi.org/format/#document-resource-identifier-objects)
docs/usage.md:[Compound Documents](http://jsonapi.org/format/#document-compound-documents).
rest_framework_json_api/django_filters/backends.py:    http://jsonapi.org/recommendations/#filtering, including relationship
rest_framework_json_api/django_filters/backends.py:    # See http://jsonapi.org/format/#document-member-names for allowed characters
rest_framework_json_api/django_filters/backends.py:    # and http://jsonapi.org/format/#document-member-names-reserved-characters for reserved
rest_framework_json_api/filters.py:    A backend filter that implements http://jsonapi.org/format/#fetching-sorting and
rest_framework_json_api/filters.py:    the rules at http://jsonapi.org/format/#query-parameters.
rest_framework_json_api/filters.py:    #: compiled regex that matches the allowed http://jsonapi.org/format/#query-parameters:
```


## Checklist

- [x] Certain that this is a bug (if unsure or you have a question use [discussions](https://github.com/django-json-api/django-rest-framework-json-api/discussions) instead)
- [x] Code snippet or unit test added to reproduce bug



Discussion:
Hi , i would like to work on this issue

@himanshu007-creator Sure. Any help is very appreciated.
Is this issue closed @sliverc ? I would love to contribute in this.
@SwarajBaral It seems @himanshu007-creator hasn't had time yet to work on this. As this is a fairly short task as long as no PR hasn't been opened to address this issue feel free to work on it.
Sure, @sliverc, I will get started right away. So just to be sure, I need to edit all the links in the `./docs` directory and change them from `http://` to `https://` right ?
@SwarajBaral yes + some occurrences in readme, changelog and a few doc strings.

Best run the following command to see what needs to change:

```
$ git grep "http://" | grep -v testserver | grep -v localhost | grep -v "127.0.0.1" | grep -v example.com | grep -v example.org
```
Thank you for such a quick response @sliverc. I will get started on it.

Resolving patch:
diff --git a/rest_framework_json_api/django_filters/backends.py b/rest_framework_json_api/django_filters/backends.py
--- a/rest_framework_json_api/django_filters/backends.py
+++ b/rest_framework_json_api/django_filters/backends.py
@@ -15,7 +15,7 @@ class DjangoFilterBackend(DjangoFilterBackend):
     to use the `filter` keyword: This is an optional implementation of style of
     filtering in which each filter is an ORM expression as implemented by
     DjangoFilterBackend and seems to be in alignment with an interpretation of
-    http://jsonapi.org/recommendations/#filtering, including relationship
+    https://jsonapi.org/recommendations/#filtering, including relationship
     chaining. It also returns a 400 error for invalid filters.
 
     Filters can be:
@@ -58,8 +58,8 @@ class DjangoFilterBackend(DjangoFilterBackend):
     search_param = api_settings.SEARCH_PARAM
 
     # Make this regex check for 'filter' as well as 'filter[...]'
-    # See http://jsonapi.org/format/#document-member-names for allowed characters
-    # and http://jsonapi.org/format/#document-member-names-reserved-characters for reserved
+    # See https://jsonapi.org/format/#document-member-names for allowed characters
+    # and https://jsonapi.org/format/#document-member-names-reserved-characters for reserved
     # characters (for use in paths, lists or as delimiters).
     # regex `\w` matches [a-zA-Z0-9_].
     # TODO: U+0080 and above allowed but not recommended. Leave them out for now.e
diff --git a/rest_framework_json_api/filters.py b/rest_framework_json_api/filters.py
--- a/rest_framework_json_api/filters.py
+++ b/rest_framework_json_api/filters.py
@@ -8,7 +8,7 @@
 
 class OrderingFilter(OrderingFilter):
     """
-    A backend filter that implements http://jsonapi.org/format/#fetching-sorting and
+    A backend filter that implements https://jsonapi.org/format/#fetching-sorting and
     raises a 400 error if any sort field is invalid.
 
     If you prefer *not* to report 400 errors for invalid sort fields, just use
@@ -74,10 +74,10 @@ class QueryParameterValidationFilter(BaseFilterBackend):
 
     If you want to add some additional non-standard query parameters,
     override :py:attr:`query_regex` adding the new parameters. Make sure to comply with
-    the rules at http://jsonapi.org/format/#query-parameters.
+    the rules at https://jsonapi.org/format/#query-parameters.
     """
 
-    #: compiled regex that matches the allowed http://jsonapi.org/format/#query-parameters:
+    #: compiled regex that matches the allowed https://jsonapi.org/format/#query-parameters:
     #: `sort` and `include` stand alone; `filter`, `fields`, and `page` have []'s
     query_regex = re.compile(
         r"^(sort|include)$|^(?P<type>filter|fields|page)(\[[\w\.\-]+\])?$"


Test patch: