Original fictional case. All request logs and file listings below are supplied examples. This page does not inspect your files, browser settings or network traffic. Progress stays in this page’s memory.

Read the complete case

The evidence and explanations are also available without JavaScript. Open a step to read its solution.

Step 1: What would give you useful evidence first?
Supplied evidence · EXAMPLE
Page: https://example.com/journal/
HTML: <img src="/images/Morning.svg" alt="Sun above hills">
Symptom: the alternative text is visible, but the image is missing.

Inspect the image request in Network

Yes. Inspect the address and response before changing the design.

Step 2: Which difference explains this request?
Supplied evidence · EXAMPLE
Simulated Network entry:
GET https://example.com/images/Morning.svg → 404
Deployed file listing: /images/morning.svg
This exercise uses a case-sensitive server.

Morning.svg does not match morning.svg

Exactly: the capital M is the mismatch.

Step 3: What completes the repair?
Supplied evidence · EXAMPLE
Edited source: <img src="/images/morning.svg" alt="Sun above hills">
The generated upload folder still contains the previous HTML.

Rebuild, deploy the generated output and verify the exact request

Correct. Check the deployed HTML and the image response. In this scenario the matching URL returns 200 and the image displays.

Apply the method

Write down the symptom, collect the exact address or rule, change one cause and verify the result. A successful request does not by itself prove that the right content was returned.

Read the companion lesson · All debugging trails · Short debugging exercises