Guides you can use today, opinions you may disagree with, and war stories you will forward to a teammate. Written by the eight humans who build ProxyCeptor.
Everything is fine. Nothing is on fire.
It is "basically done". The docs are "in progress". The staging URL is "being fixed". A field guide, with a survival plan at the end.
Gently ruining a popular belief.
If it cannot be measured, it is a hobby. Here are five beliefs about mocking that do not survive contact with a real workflow.
The unpolished version.
The decisions we made on purpose, the constraints that forced our hand, and why one small JSON shape ended up running everywhere.
No jargon, no gatekeeping.
Local Overrides is Chrome's built-in way to fake a response. It is great for quick edits and awkward for everything else. Here is exactly where the line is.
Grab coffee. This goes deep.
Every project has a hidden API nobody remembers writing, and on a TV you cannot even see it. What actually works when the device will not trust your proxy.
What changed, and who it hurts.
Manifest V3 removed blocking webRequest, leaving developers wondering how to modify response bodies. Here is why declarativeNetRequest cannot touch payloads and how modern interceptors bypass the limitation.
Grab coffee. This goes deep.
Code interceptors belong to your app. Proxy interceptors belong to your debugging session. Mixing them up is how mock data ends up in production.
You will send this to a friend.
I had to learn these the hard way. Here is the version I wish I had: what each code means, one joke each, and what your UI should do about it.
Zero to first request.
I asked what a proxy was. Now I am writing about it. Here are the mistakes that cost me the most time, so they do not cost you yours.
Zero to first request.
Five short exercises that take you from "what is a proxy interceptor?" to mocking, deep-merging, failing and redirecting real API calls, with copy-paste rules.
Someone had to say it.
The backend is "two more days" away. It has been two more days for a while. Here is a spicy position: the UI should never wait for it.
No jargon, no gatekeeping.
There is no single best proxy interceptor. There is a best one for penetration testing, for mocking APIs in Chrome, for native mobile apps, and for Smart TVs. Here is how the 10 leading tools compare.
Painfully familiar.
Composite stories of five bugs every QA team has met, all invisible on a fast laptop and all reproducible in ten seconds once you can slow the API on demand.
Tick the boxes. Sleep better.
Happy paths get tested. Failure paths get shipped. Use this checklist to force each API failure mode in minutes and make sure your UI handles it.
Laugh first, learn second.
Nobody ever said "great retro" about a 3 a.m. incident. But they should. Here is how teams make on-call less awful.
Deep breath. Here we go.
It flashes for 40 milliseconds on my machine and I have declared victory. Deep breath. Let us talk about loading states.
Create a free ProxyCeptor account to mock, delay, block and rewrite API traffic, then share the same rules with your team.