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: Which image URL does the browser resolve?
Supplied evidence · EXAMPLE
Page: https://example.com/notes/
HTML: <img src="images/turn.svg" alt="A bend in the path">
Deployed asset: /images/turn.svg
There is no base element.

https://example.com/notes/images/turn.svg

Yes. The relative reference is resolved from the document URL’s directory.

Step 2: Which edit clearly targets that existing asset?
Supplied evidence · EXAMPLE
Simulated request: /notes/images/turn.svg → 404
The site is hosted at the domain root. /images/turn.svg exists.

src="/images/turn.svg"

Yes. The leading slash starts from the origin root.

Step 3: What should you reconsider?
Supplied evidence · EXAMPLE
The corrected root-hosted site works. You now plan to publish a copy under /demo/ with its assets at /demo/images/.

Whether root-relative paths still point to the intended deployment base

Exactly. /images/ still starts at the origin root, not /demo/. Adapt paths or the build base to the deployment.

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