HTTPS and secure cookies in Django

Introduction

HTTPS keeps data safe by encrypting it between your website and visitors. Secure cookies help protect user information by only sending cookies over HTTPS.

When you want to protect user passwords and personal data on your website.

When you need to keep login sessions safe from hackers.

When handling sensitive information like payment details.

When you want to improve user trust by showing a secure site.

When complying with privacy laws that require data protection.

Syntax

Django

SECURE_SSL_REDIRECT = True
SESSION_COOKIE_SECURE = True
CSRF_COOKIE_SECURE = True

Set SECURE_SSL_REDIRECT to force all traffic to HTTPS.

Use SESSION_COOKIE_SECURE and CSRF_COOKIE_SECURE to make cookies send only over HTTPS.

Examples

This setting makes Django redirect all HTTP requests to HTTPS automatically.

Django

SECURE_SSL_REDIRECT = True

This ensures the session cookie is only sent over HTTPS, protecting login sessions.

Django

SESSION_COOKIE_SECURE = True

This makes the CSRF cookie secure, preventing it from being sent over insecure connections.

Django

CSRF_COOKIE_SECURE = True

Sample Program

This example shows the key settings in settings.py to enable HTTPS redirection and secure cookies. The simple view returns a welcome message. When deployed with HTTPS, cookies will only be sent securely.

Django

from django.http import HttpResponse
from django.views.decorators.csrf import csrf_exempt

# settings.py snippet
SECURE_SSL_REDIRECT = True
SESSION_COOKIE_SECURE = True
CSRF_COOKIE_SECURE = True

# views.py snippet
@csrf_exempt
def home(request):
    return HttpResponse("Welcome to the secure site!")

Important Notes

Remember to have a valid SSL certificate installed on your server for HTTPS to work.

Secure cookies won't be sent over HTTP, so test your site using HTTPS URLs.

Using HTTPS also improves SEO and user trust.

Summary

HTTPS encrypts data between users and your site.

Secure cookies protect sensitive session and CSRF data.

Enable SECURE_SSL_REDIRECT, SESSION_COOKIE_SECURE, and CSRF_COOKIE_SECURE in Django settings.

Practice

1. What is the main purpose of setting SESSION_COOKIE_SECURE = True in Django settings?

easy

A. To allow cookies on both HTTP and HTTPS

B. To make cookies accessible to JavaScript

C. To disable cookies entirely

D. To ensure cookies are only sent over HTTPS connections

Solution

1. Step 1: Understand what SESSION_COOKIE_SECURE does

   This setting tells Django to only send session cookies over HTTPS connections, preventing them from being sent over insecure HTTP.

2. Step 2: Analyze the options

   To ensure cookies are only sent over HTTPS connections correctly describes this behavior. The other options do not match the purpose of this setting.

3. Final Answer:

   To ensure cookies are only sent over HTTPS connections -> Option D

4. Quick Check:

   SESSION_COOKIE_SECURE = True means HTTPS only [OK]

Hint: Secure cookies only send on HTTPS connections [OK]

Common Mistakes:

• Thinking it makes cookies accessible to JavaScript
• Believing it disables cookies
• Assuming it allows cookies on HTTP

2. Which of the following is the correct way to enable HTTPS redirection in Django settings?

easy

A. SECURE_SSL_REDIRECT = False

B. SECURE_SSL_REDIRECT = True

C. SESSION_COOKIE_SECURE = False

D. CSRF_COOKIE_SECURE = False

Solution

1. Step 1: Identify the setting for HTTPS redirection

   The setting SECURE_SSL_REDIRECT controls whether Django redirects HTTP requests to HTTPS.

2. Step 2: Choose the correct value to enable redirection

   Setting SECURE_SSL_REDIRECT = True enables automatic redirection to HTTPS. The other options either disable security or relate to cookies.

3. Final Answer:

   SECURE_SSL_REDIRECT = True -> Option B

4. Quick Check:

   Enable HTTPS redirect with SECURE_SSL_REDIRECT = True [OK]

Hint: Set SECURE_SSL_REDIRECT to True to force HTTPS [OK]

Common Mistakes:

• Setting SECURE_SSL_REDIRECT to False disables HTTPS redirect
• Confusing cookie settings with HTTPS redirect
• Not enabling HTTPS redirect at all

3. Given the following Django settings snippet, what will happen when a user accesses the site over HTTP?

SECURE_SSL_REDIRECT = True
SESSION_COOKIE_SECURE = True
CSRF_COOKIE_SECURE = True

medium

A. The user will be redirected to the HTTPS version of the site

B. The session cookie will be sent over HTTP

C. CSRF protection will be disabled

D. The site will allow HTTP access without redirection

Solution

1. Step 1: Understand SECURE_SSL_REDIRECT = True

   This setting forces Django to redirect all HTTP requests to HTTPS automatically.

2. Step 2: Analyze cookie settings

   Both SESSION_COOKIE_SECURE and CSRF_COOKIE_SECURE ensure cookies are only sent over HTTPS, but the redirect happens first.

3. Final Answer:

   The user will be redirected to the HTTPS version of the site -> Option A

4. Quick Check:

   SECURE_SSL_REDIRECT = True causes HTTPS redirect [OK]

Hint: HTTPS redirect happens before cookies are sent [OK]

Common Mistakes:

• Thinking cookies are sent over HTTP despite redirect
• Assuming CSRF protection is disabled
• Believing HTTP access is allowed without redirect

4. You set SESSION_COOKIE_SECURE = True but notice session cookies are still sent over HTTP. What is the most likely cause?

medium

A. The site is not using HTTPS, so cookies are sent anyway

B. The browser does not support secure cookies

C. You forgot to set SECURE_SSL_REDIRECT = True

D. You need to set CSRF_COOKIE_SECURE = False

Solution

1. Step 1: Understand the role of SECURE_SSL_REDIRECT

   This setting forces HTTP requests to HTTPS, ensuring secure cookies are sent only over HTTPS.

2. Step 2: Identify why cookies are sent over HTTP

   If SECURE_SSL_REDIRECT is not enabled, users can access the site over HTTP, so cookies may be sent insecurely despite SESSION_COOKIE_SECURE.

3. Final Answer:

   You forgot to set SECURE_SSL_REDIRECT = True -> Option C

4. Quick Check:

   Enable SECURE_SSL_REDIRECT to enforce HTTPS [OK]

Hint: Enable SECURE_SSL_REDIRECT to prevent HTTP cookie sending [OK]

Common Mistakes:

• Assuming browser ignores secure cookie flag
• Thinking CSRF_COOKIE_SECURE affects session cookies
• Believing HTTPS is automatic without redirect

5. You want to secure your Django site so that session and CSRF cookies are only sent over HTTPS, and all HTTP requests redirect to HTTPS. Which combination of settings achieves this securely?

hard

A. SECURE_SSL_REDIRECT = True, SESSION_COOKIE_SECURE = True, CSRF_COOKIE_SECURE = True

B. SECURE_SSL_REDIRECT = False, SESSION_COOKIE_SECURE = True, CSRF_COOKIE_SECURE = True

C. SECURE_SSL_REDIRECT = True, SESSION_COOKIE_SECURE = False, CSRF_COOKIE_SECURE = False

D. SECURE_SSL_REDIRECT = False, SESSION_COOKIE_SECURE = False, CSRF_COOKIE_SECURE = False

Solution

1. Step 1: Ensure HTTP requests redirect to HTTPS

   Setting SECURE_SSL_REDIRECT = True forces all HTTP requests to HTTPS, preventing insecure access.

2. Step 2: Secure cookies for session and CSRF

   Setting both SESSION_COOKIE_SECURE and CSRF_COOKIE_SECURE to True ensures cookies are only sent over HTTPS connections.

3. Step 3: Evaluate other options

   The other options fail to secure either redirection or cookies properly, leaving security gaps.

4. Final Answer:

   SECURE_SSL_REDIRECT = True, SESSION_COOKIE_SECURE = True, CSRF_COOKIE_SECURE = True -> Option A

5. Quick Check:

   All three settings True secures HTTPS and cookies [OK]

Hint: Enable all three: redirect and secure cookies [OK]

Common Mistakes:

• Not enabling HTTPS redirect
• Leaving cookie secure flags False
• Assuming one setting is enough alone