---
title: "Test a fix against the reporter's page with DevTools overrides | Proofline"
description: "Before a fix ships, the maintainer can test it against the real page the reporter used, from their own browser."
url: https://proofline.sh/learn/local-overrides-test-fix/
---

[Learning center](/learn/)

# Test a fix against the reporter's page with DevTools overrides

Before a fix ships, the maintainer can test it against the real page the reporter used, from their own browser. Chrome DevTools' local overrides replace a response's content or headers with a local file, and keep doing it across reloads. That turns "this should fix it" into "with this change, the failing steps pass", without a deploy.

Deployment failures The Proofline team November 22, 2026 3 min read

## Override a file or a header

1.  In the Network panel, right-click the response you want to change and choose **Override content** or **Override headers**.
2.  The first time, DevTools asks for a local folder to keep overrides in and for permission to use it.
3.  Edit the file in the **Sources** panel's editor, or edit the header in the **Headers** tab. Overridden requests are marked in the Network panel.
4.  Reload. The browser now receives your version of that response.

[Chrome DevTools: Override web content and HTTP response headers locally](https://developer.chrome.com/docs/devtools/overrides)

Overrides stay active while DevTools is open, across reloads. Turn them off in **Sources > Overrides** when you are done, so a later session does not test a page that is not the real one.

## What to override for common fixes

| The fix changes | Override |
| --- | --- |
| A line in a JavaScript bundle | The bundle file. With source maps, edit the original source and rebuild the bundle locally, or edit the minified file near the mapped line. |
| A CSS rule | The stylesheet, or add the rule to the HTML document |
| A server header, such as `Cache-Control`, `Content-Security-Policy` or a CORS header | **Override headers** on that response |
| An API response the page mishandles | The API response, to confirm the page's handling, not the server's fix |

## Prove the fix with the reporter's steps

An override test is only as good as the steps it runs. Replay the reporter's reproduction against the overridden page:

1.  Reproduce the bug without overrides, and confirm it fails.
2.  Turn on the override, reload and run the same steps.
3.  Confirm the expected result, and check that nearby behavior still works.

For an automated version of the same test, a Playwright route that fulfills the response with your file does what an override does, in a script:

```
await page.route('**/assets/checkout-*.js', route => route.fulfill({ path: 'fixed-checkout.js' }));
```

## Limits

-   The override changes what the browser receives, not what the server does. A fix that changes server logic cannot be tested this way; only its effect on the response can be imitated.
-   DevTools disables the browser cache while overrides are active, as **Disable cache** does. An override cannot show whether a caching header fixes a caching bug; deploy the header to a test environment and check it with normal caching on.
-   Hashed file names change on each deploy. An override for `checkout-3f2a1c.js` stops matching after the next deploy.
-   A service worker may answer the request before the network override applies. Bypass it for the test; [the service worker guide](/learn/service-worker-controlled-page/) shows how.
-   The test runs in your browser, with your state. If the bug depended on the reporter's state, [seed it first](/learn/seed-local-storage-indexeddb/).

## Worked example: a total that rounded twice

This example is fictional. A customer reports that an invoice total shows €10.01 where the line items add up to €10.00. The developer finds that the page rounds each line before summing and writes a fix that sums first.

Before opening a pull request, they override the production bundle with a locally built copy containing the fix, follow the customer's steps on a test account with the same three line items, and see €10.00. Without the override the €10.01 returns. The fix shipped with evidence that it addressed the reporter's steps on the real page.

## Questions

### Do overrides work in Firefox or Safari?

Their developer tools have different features for this. For a cross-browser test, use a local proxy or a Playwright route.

### Can I share an override with the reporter?

You can send the file and the steps, but they need DevTools and the same page version. A deployed preview of the fix is usually easier for them.

### Is it safe to override production pages?

It changes only what your browser receives. Be careful with actions on production data during the test, since the page will really submit what you do.

Return to [reproducing what someone else saw](/learn/replay-browser-bug-report/) for the other layers a replay needs.

## One month of free code review.

New organizations get one calendar month of hosted code review for private and public GitHub repositories. No card or cloud connection required. [Eligibility and fair-use terms](/free-code-review/).

[Start free with GitHub](https://proofline.sh/orgs/plan?offer=free_month)

## Related reading

-   ### [Record which service worker controlled the page](/learn/service-worker-controlled-page/)
    
    Deployment failures The Proofline team November 22, 2026 4 min read
    
-   ### [Freeze the backend's answers with a recorded HAR](/learn/har-replay-playwright/)
    
    Network outages The Proofline team November 22, 2026 4 min read
