Not tremendously! I tried to throw in as much technical detail as I could conjure regarding HTTP protocol, networking, http servers, wsgi servers, and the application itself, but the huge scope and general nature of the question made me uncertain of my answer, shook my confidence, and I forgot many details. After a bit, I was asked to focus only on the part after the request is received by Django. I immediately wished I spent less time in the docs, and more time in the framework's code. When I got home, that is the first thing I did. I think the key to answering this question is to be confident. You probably won't remember most of what you have encountered in the past and are actually familiar with, but you probably know way more than enough. Give yourself some credit. Try answering the question like a story and include sound effects.
Another seemingly innocuous interview question, this is actually a perfect opportunity to stand out and show your passion for and connection to the company. For example, if you found out about the gig through a friend or professional contact, name drop that person, then share why you were so excited about it. If you discovered the company through an event or article, share that. Even if you found the listing through a random job board, share what, specifically, caught your eye about the role.