Bird
0
0

You added WhiteNoiseMiddleware but static files still return 404 errors. What is a likely cause?

medium📝 Debug Q6 of 15
Django - Deployment and Production
You added WhiteNoiseMiddleware but static files still return 404 errors. What is a likely cause?
ASTATIC_ROOT is not set or collectstatic was not run
BDEBUG is set to False
CWhiteNoiseMiddleware is placed before SecurityMiddleware
DALLOWED_HOSTS is empty
Step-by-Step Solution
Solution:

  1. Step 1: Check static files collection

    If STATIC_ROOT is missing or collectstatic was not run, static files won't be available to serve.

  2. Step 2: Understand other options

    DEBUG=False is normal in production; middleware order matters but placing WhiteNoise before SecurityMiddleware is not recommended but not always fatal; ALLOWED_HOSTS affects host access, not static files.

  3. Final Answer:

    STATIC_ROOT is not set or collectstatic was not run -> Option A

  4. Quick Check:

    Missing STATIC_ROOT or collectstatic = 404 static files [OK]
Quick Trick: Always set STATIC_ROOT and run collectstatic [OK]
Common Mistakes:
MISTAKES
  • Ignoring collectstatic step
  • Misplacing middleware order without checking static files

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Django Quizzes
Async Django - When async helps and when it does not - Quiz 7medium Async Django - Why async matters in Django - Quiz 3easy Caching - Cache backends (memory, Redis, Memcached) - Quiz 14medium DRF Advanced Features - Custom serializer fields - Quiz 6medium DRF Advanced Features - Serializer validation - Quiz 9hard Deployment and Production - Database migration in production - Quiz 4medium Django REST Framework Basics - Serializers for data conversion - Quiz 13medium Security Best Practices - Security checklist (manage.py check --deploy) - Quiz 2easy Security Best Practices - Content Security Policy - Quiz 6medium Testing Django Applications - TestCase and SimpleTestCase - Quiz 12easy