Cache busting strategies in Flask - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a version query parameter for cache busting in a Flask template URL.

Flask

url_for('static', filename='style.css') + '?v=[1]'

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

Aversion

Bcache

Crandom

Dtimestamp

Attempts:

3 left

💡 Hint

Common Mistakes

Using a fixed string that never changes, so cache is not busted.

Forgetting to add the query parameter at all.

Using a timestamp as a query parameter helps browsers load the latest file version by changing the URL when the file updates.

2fill in blank

medium

Complete the Flask route to send a static file with a cache-busting header.

Flask

from flask import send_from_directory, make_response

@app.route('/static/<path:filename>')
def static_files(filename):
    response = make_response(send_from_directory('static', filename))
    response.headers['Cache-Control'] = '[1]'
    return response

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

Ano-cache, no-store, must-revalidate

Bmax-age=3600

Cpublic, max-age=86400

Dprivate, max-age=0

Attempts:

3 left

💡 Hint

Common Mistakes

Using a long max-age which allows caching.

Not setting Cache-Control header at all.

Setting 'no-cache, no-store, must-revalidate' tells browsers not to cache the file, ensuring fresh content.

3fill in blank

hard

Fix the error in the Flask template to append a file hash for cache busting.

Flask

<link rel="stylesheet" href="{{ url_for('static', filename='style.css') }}?v=[1]">

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

Ahash

Bhash_file

Cget_hash()

Dfile_hash

Attempts:

3 left

💡 Hint

Common Mistakes

Using a function call inside the template variable.

Using a variable name not passed from the view.

The variable 'hash' should be passed from the Flask view to the template to append the file's hash for cache busting.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps filenames to their cache-busted URLs using a version number.

Flask

cache_busted_urls = {file: url_for('static', filename=file) + '?v=' + [1] for file in files if file.[2]('.css')}

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

Aversion

Bendswith

Cstartswith

Din

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'startswith' instead of 'endswith' for file extension.

Not appending the version parameter.

The dictionary comprehension appends the version to URLs only for files ending with '.css'.

5fill in blank

hard

Fill all three blanks to create a Flask function that returns a static file URL with a timestamp cache buster and sets a no-cache header.

Flask

from flask import url_for, make_response, send_from_directory
import time

def get_static_file(filename):
    url = url_for('static', filename=filename) + '?v=' + str([1])
    response = make_response(send_from_directory('static', filename))
    response.headers['Cache-Control'] = '[2]'
    return response, url

current_time = [3]

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

Atime.time()

Bno-cache, no-store, must-revalidate

Cint(time.time())

Dmax-age=3600

Attempts:

3 left

💡 Hint

Common Mistakes

Using float timestamp which may cause URL issues.

Setting Cache-Control to allow caching.

The function uses the current integer timestamp for cache busting and sets headers to prevent caching.

Practice

1. What is the main purpose of cache busting in Flask applications?

easy

A. To force browsers to load updated static files by changing their URLs

B. To speed up the server response time by caching database queries

C. To reduce the size of static files by compressing them

D. To prevent users from accessing static files

Solution

1. Step 1: Understand cache behavior in browsers

   Browsers cache static files to avoid re-downloading them on every visit, which improves speed.

2. Step 2: Identify the role of cache busting

   Cache busting changes the URL of static files so browsers fetch the new version instead of using the cached one.

3. Final Answer:

   To force browsers to load updated static files by changing their URLs -> Option A

4. Quick Check:

   Cache busting = force reload updated files [OK]

Hint: Cache busting changes URLs to refresh files in browser cache [OK]

Common Mistakes:

• Confusing cache busting with server-side caching
• Thinking cache busting compresses files
• Believing cache busting blocks file access

2. Which of the following is the correct way to add a version query parameter for cache busting in Flask's url_for function?

easy

A. url_for('static', filename='style.css', _anchor='1.0')

B. url_for('static', filename='style.css?v=1.0')

C. url_for('static', filename='style.css', v='1.0')

D. url_for('static', filename='style.css', _external='1.0')

Solution

1. Step 1: Recall how url_for adds query parameters

   Any extra keyword arguments in url_for become query parameters in the URL.

2. Step 2: Identify the common cache busting parameter name

   v='1.0' is the common short form used for cache busting, adding ?v=1.0.

3. Final Answer:

   url_for('static', filename='style.css', v='1.0') -> Option C

4. Quick Check:

   Extra args in url_for = query params [OK]

Hint: Extra args in url_for become query parameters [OK]

Common Mistakes:

• Putting version query string inside filename argument
• Using special parameters like _anchor (adds fragment, not query)
• Using _external (absolute URL, no query param)

3. Given this Flask template snippet:

<link rel="stylesheet" href="{{ url_for('static', filename='app.css', v='2.1') }}">

What will be the rendered href attribute in the HTML?

medium

A. /static/app.css

B. /static/app.css?version=2.1

C. /static/app.css?v=app.css

D. /static/app.css?v=2.1

Solution

1. Step 1: Understand how url_for builds URLs

   url_for('static', filename='app.css', v='2.1') creates a URL to the static file with a query parameter v=2.1.

2. Step 2: Construct the full URL

   The URL will be /static/app.css?v=2.1 because filename sets the path and v adds the query string.

3. Final Answer:

   /static/app.css?v=2.1 -> Option D

4. Quick Check:

   url_for adds query param v=2.1 [OK]

Hint: url_for adds extra args as query strings [OK]

Common Mistakes:

• Confusing parameter name 'v' with 'version'
• Forgetting the query parameter appears in URL
• Assuming no query string is added

4. You added cache busting by appending v='1.0' in url_for, but after updating your CSS file, the browser still loads the old styles. What is the most likely cause?

medium

A. The static folder is missing from your project

B. You forgot to update the version string to a new value

C. Flask does not support query parameters in url_for

D. The filename parameter in url_for is incorrect

Solution

1. Step 1: Understand cache busting requires version change

   Browsers cache files by URL. If the version string stays the same, the URL doesn't change, so the browser uses cached files.

2. Step 2: Identify why old styles load

   If the version string is not updated after file changes, the browser won't request the new file.

3. Final Answer:

   You forgot to update the version string to a new value -> Option B

4. Quick Check:

   Version string must change to bust cache [OK]

Hint: Change version string when files update to bust cache [OK]

Common Mistakes:

• Assuming Flask ignores query parameters in url_for
• Not verifying static folder presence
• Changing filename without updating version

5. You want to implement cache busting in a Flask app so that static files update only when changed. Which approach is best to automate this?

hard

A. Use the file's last modified timestamp as a query parameter in url_for

B. Disable browser caching completely in Flask configuration

C. Manually update a version string in url_for every time files change

D. Rename static files randomly on every request

Solution

1. Step 1: Consider manual version updates

   Manually updating version strings is error-prone and tedious.

2. Step 2: Use file modification time for automation

   Using the file's last modified timestamp as a query parameter ensures the URL changes only when the file changes, automating cache busting.

3. Step 3: Evaluate other options

   Disabling caching hurts performance; renaming files randomly breaks references and is inefficient.

4. Final Answer:

   Use the file's last modified timestamp as a query parameter in url_for -> Option A

5. Quick Check:

   File timestamp automates cache busting [OK]

Hint: Use file timestamps to automate cache busting [OK]

Common Mistakes:

• Relying on manual version updates only
• Disabling caching instead of busting
• Random renaming causing broken links