diff options
| author | Rik <gitaarik@gmail.com> | 2015-03-08 16:02:31 +0100 |
|---|---|---|
| committer | Erik Romijn <eromijn@solidlinks.nl> | 2015-03-08 16:32:54 +0100 |
| commit | 794c3f74c32062d0f2ad021cb2af0e530b40730d (patch) | |
| tree | b4eb63360b70cab781a3b2cde6d1ee119aef1158 /docs/ref/request-response.txt | |
| parent | 336512fae77ec214ad6db24166b9a8676007cc09 (diff) | |
Fixed #24460 -- Extended HttpRequest.build_absolute_uri documentation
Added explanation on why build_absolute_uri always enforces the
request's scheme.
Diffstat (limited to 'docs/ref/request-response.txt')
| -rw-r--r-- | docs/ref/request-response.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/ref/request-response.txt b/docs/ref/request-response.txt index 50310b9692..0a7a75cdc7 100644 --- a/docs/ref/request-response.txt +++ b/docs/ref/request-response.txt @@ -249,6 +249,14 @@ Methods Example: ``"http://example.com/music/bands/the_beatles/?print=true"`` + .. note:: + + Mixing HTTP and HTTPS on the same site is discouraged, therefore + :meth:`~HttpRequest.build_absolute_uri()` will always generate an + absolute URI with the same scheme the current request has. If you need + to redirect users to HTTPS, it's best to let your webserver redirect + all HTTP traffic to HTTPS. + .. method:: HttpRequest.get_signed_cookie(key, default=RAISE_ERROR, salt='', max_age=None) Returns a cookie value for a signed cookie, or raises a |