Understanding the Request-Response Cycle is a crucial step in setting up for any WebServer.
An example of the request-response cycle is when you “request” a web page by entering a URL in your browser and a web server sends a web page as ‘response’ to your browser. Of course, there’re usually several HTTP requests that happen when visiting a website; each is a separate Request-Response in itself.
The request-response architecture of a web application is an important idea to grasp whether you’re working on Django, Symphony, Laravel, Flask, WordPress or any of the thousands of other web frameworks.
When you call a Django server the flow typically is
Request: Browser → Web Server → WSGI → WSGI callable function in Django
Response: Django → WSGI → Web Server → Browser
Here’s a diagram that explains the request-response flow very well.