WSGI concept overview in Flask - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a simple WSGI application function.

Flask

def application(environ, [1]):
    start_response('200 OK', [('Content-Type', 'text/plain')])
    return [b'Hello World']

Drag options to blanks, or click blank then click option'

Astart_response

Bsend_response

Crequest

Dresponse

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect argument names like 'response' or 'request' instead of 'start_response'.

Forgetting to include the 'start_response' argument.

The WSGI application function takes two arguments: environ and start_response. The start_response callable is used to begin the HTTP response.

2fill in blank

medium

Complete the code to call the start_response function with status and headers.

Flask

def application(environ, start_response):
    [1]('200 OK', [('Content-Type', 'text/html')])
    return [b'<h1>Welcome</h1>']

Drag options to blanks, or click blank then click option'

Asend_response

Bbegin_response

Cstart_response

Dresponse_start

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect function names like 'send_response' or 'begin_response'.

Not calling the function before returning the body.

The start_response function is called with the HTTP status and headers to begin the response.

3fill in blank

hard

Fix the error in the WSGI application to return the response body correctly as bytes.

Flask

def application(environ, start_response):
    start_response('200 OK', [('Content-Type', 'text/plain')])
    return [[1]]

Drag options to blanks, or click blank then click option'

A'Hello World'

Bb'Hello World'

Cbytearray('Hello World')

Dstr('Hello World')

Attempts:

3 left

💡 Hint

Common Mistakes

Returning a normal string instead of bytes.

Returning a non-iterable instead of a list or iterable.

The WSGI application must return an iterable of byte strings. Using b'Hello World' ensures the response is bytes.

4fill in blank

hard

Fill both blanks to create a Flask app and run it with debug mode on.

Flask

from flask import Flask
app = Flask(__name__)

@app.route('/')
def home():
    return 'Hello Flask!'

if __name__ == '__main__':
    app.[1](debug=[2])

Drag options to blanks, or click blank then click option'

Arun

Bstart

Cexecute

DTrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect method names like 'start' or 'execute'.

Setting debug to a string instead of a boolean.

To run a Flask app with debug mode, call app.run(debug=True).

5fill in blank

hard

Fill all three blanks to create a WSGI middleware that prints a message before calling the app.

Flask

def simple_middleware(app):
    def middleware(environ, start_response):
        print([1])
        return app([2], [3])
    return middleware

Drag options to blanks, or click blank then click option'

A'Middleware active'

Benviron

Cstart_response

D'Starting app'

Attempts:

3 left

💡 Hint

Common Mistakes

Passing wrong arguments to the app call.

Printing a variable instead of a string message.

The middleware prints a message, then calls the wrapped app with environ and start_response.

Practice

1. What is the main role of WSGI in a Flask web application?

easy

A. It acts as a bridge between the web server and the Python application.

B. It stores the application's database connections.

C. It manages user sessions and cookies.

D. It handles the frontend HTML and CSS rendering.

Solution

1. Step 1: Understand WSGI's purpose

   WSGI stands for Web Server Gateway Interface and connects web servers with Python apps.

2. Step 2: Identify WSGI's role in Flask

   Flask apps use WSGI to receive requests from servers and send responses back.

3. Final Answer:

   It acts as a bridge between the web server and the Python application. -> Option A

4. Quick Check:

   WSGI = bridge between server and app [OK]

Hint: WSGI connects server and Python app like a translator [OK]

Common Mistakes:

• Confusing WSGI with frontend rendering
• Thinking WSGI manages databases
• Assuming WSGI handles user sessions

2. Which of the following is the correct signature of a WSGI application callable?

easy

A. def app(request, response):

B. def app():

C. def app(request):

D. def app(environ, start_response):

Solution

1. Step 1: Recall WSGI callable signature

   A WSGI app is a function that takes two arguments: environ and start_response.

2. Step 2: Match the correct function signature

   Only def app(environ, start_response): matches the required parameters for a WSGI callable.

3. Final Answer:

   def app(environ, start_response): -> Option D

4. Quick Check:

   WSGI callable = (environ, start_response) [OK]

Hint: WSGI apps always take environ and start_response [OK]

Common Mistakes:

• Using request and response instead of environ and start_response
• Missing one or both parameters
• Defining a function with no parameters

3. Given this WSGI app snippet, what will be the response body sent to the client?

def app(environ, start_response):
    start_response('200 OK', [('Content-Type', 'text/plain')])
    return [b'Hello, WSGI!']

medium

A. An empty response with status 200

B. A server error due to missing return type

C. The text 'Hello, WSGI!' displayed in the browser

D. A response with HTML content

Solution

1. Step 1: Analyze start_response call

   The status is '200 OK' and content type is 'text/plain', so plain text will be sent.

2. Step 2: Check the return value

   The app returns a list with a byte string containing 'Hello, WSGI!'. This is the response body.

3. Final Answer:

   The text 'Hello, WSGI!' displayed in the browser -> Option C

4. Quick Check:

   Return byte string with 'Hello, WSGI!' = The text 'Hello, WSGI!' displayed in the browser [OK]

Hint: Return a byte string list for response body in WSGI [OK]

Common Mistakes:

• Returning a string instead of bytes
• Not calling start_response before returning
• Expecting HTML content without setting content-type

4. Identify the error in this WSGI application code:

def app(environ, start_response):
    start_response('200 OK')
    return [b'Hello']

medium

A. The function should not take any parameters.

B. Missing the headers argument in start_response call.

C. The return value should be a string, not bytes.

D. start_response should be called after returning the response.

Solution

1. Step 1: Check start_response usage

   start_response requires two arguments: status and headers list. Here headers are missing.

2. Step 2: Validate return type and function signature

   Return type is correct as a list of bytes, and parameters are correct.

3. Final Answer:

   Missing the headers argument in start_response call. -> Option B

4. Quick Check:

   start_response needs headers list [OK]

Hint: start_response needs status and headers list [OK]

Common Mistakes:

• Omitting headers argument in start_response
• Returning string instead of bytes
• Calling start_response after return

5. You want to create a WSGI app that returns 'Welcome!' only if the URL path is '/home', otherwise returns 'Not Found' with status 404. Which code correctly implements this?

hard

A. def app(environ, start_response):
if environ['PATH_INFO'] == '/home':
start_response('200 OK', [('Content-Type', 'text/plain')])
return [b'Welcome!']
else:
start_response('404 Not Found', [('Content-Type', 'text/plain')])
return [b'Not Found']

B. def app(environ, start_response):
if environ['PATH_INFO'] == '/home':
return [b'Welcome!']
else:
start_response('404 Not Found', [('Content-Type', 'text/plain')])
return [b'Not Found']

C. def app(environ, start_response):
start_response('200 OK', [('Content-Type', 'text/plain')])
return [b'Welcome!']

D. def app(environ, start_response):
start_response('404 Not Found')
return [b'Not Found']

Solution

1. Step 1: Check URL path handling

   Use environ['PATH_INFO'] to check the requested path; only '/home' returns 'Welcome!'.

2. Step 2: Verify start_response calls and return values

   Both cases call start_response with correct status and headers, and return byte strings in a list.

3. Final Answer:

   The code that checks environ['PATH_INFO'] == '/home' and calls start_response in both branches. -> Option A

4. Quick Check:

   Check PATH_INFO and call start_response properly [OK]

Hint: Always call start_response before returning response [OK]

Common Mistakes:

• Not calling start_response in all branches
• Returning bytes without start_response
• Ignoring PATH_INFO for routing