[Replay Bug]: Font file with URL-encoded space (%20) in filename returns 404, path separator inserted during replay

[EstebanPiacentino]

ReplayWeb.page Version

App v0.16.1 & Extension v0.16.1

What did you expect to happen? What happened instead?

A font file with a space in its filename (Raleway%20Regular.woff) is captured
successfully (Status 200, visible in Resources tab), but fails to load during
replay with a 404 error.

The replay engine appears to mangle the URL by inserting a / before the
encoded space, turning:

/assets/font/Raleway%20Regular.woff

into:

/assets/font/Raleway/%20Regular.woff

Console error during replay:

GET ..../https://web-url.com/assets/font/Raleway/%20Regular.woff net::ERR_ABORTED 404 (Not Found)

The font is present in the archive (confirmed via Resources tab search), so
this is a replay URL rewriting issue, not a capture issue.

Step-by-step reproduction instructions

1. Archive any website that loads a font file with a space in its filename
   (e.g., Raleway%20Regular.woff at https://bridge-front.netlify.app/)
2. Confirm the font appears in the Resources tab with Status 200
3. Replay the archived page
4. Open DevTools → Console: observe 404 error for the font URL
5. Compare the requested URL vs. the original — note the inserted /
   before %20

Additional details

No response

[mistydemeo]

It looks like the webpage you’ve linked is a 404 for me; do you have an example live page or a WACZ you could share?

[EstebanPiacentino]

True, here's a sample .wacz showing the problem

example-bridge.wacz.zip

Let me know if this works. Thank you!