mockinghow-to
Run a fake API on a port of its own, with routes, cases, WebSocket connections and streamed AI-style answers, then flip it into a failure on demand. Build one by hand or import it from an OpenAPI spec.
how-tovariables
One Mittelware rule keeps a header from a login response in a variable, and a second rule sends it with every later request. No scripting, no copy and paste, and no changes to the app or the server.
tipsrules
Group rules into collections such as checkout flow or staging setup, switch a whole collection off and on with one click, and use the order of collections to decide which rule wins.
how-tomobile
Send an iPhone, an Android phone or a tablet's traffic through Mittelware on your computer. Scan a code, install the certificate, set the proxy, and read every request its apps and sites make, then change them with rules.
how-todebugging
Test a front-end fix inside the real, deployed site. One Mittelware rule answers from a folder on your computer and passes everything else to the real server, and another swaps a single script for your dev server.
how-todebugging
Your frontend runs on localhost and your data lives on staging. Add the auth and tenant headers the server wants and change one response, using two Mittelware rules, without touching the code, the config or the server.
how-towebsockets
Watch a live WebSocket connection message by message, then change, drop, delay, hold or close messages with a rule. Debug the real app against the real server, with no throwaway client script.
mockingtesting
API mocking replaces the API with a fake. API interception edits real traffic as it passes. See the difference with diagrams, and when to use each.
debuggingai
AI-written code breaks at the network boundary. See how a network interceptor lets you edit API responses in transit, force errors and find bugs without touching the backend.
funtesting
Make a real server answer "I'm a teapot" on demand. A silly status code that's secretly the best way to find out whether your app copes with errors it has never heard of.
how-totesting
Make a payment, login or search endpoint fail on demand, so you can see how your app handles errors. Two rules, no code changes, and one detail that keeps you from double-charging a card.
how-todebugging
Redirect requests from a deployed web app, desktop app or Postman to the API running on your laptop, using a single Modify Request rule and a template variable.
how-tomocking
Build the frontend first. Use a Modify Response rule to return realistic JSON for an endpoint that doesn't exist yet, including values pulled from the request URL.
how-tohttps
A step-by-step guide to seeing the requests and responses your apps send, even over HTTPS, and how to read what you find.
how-totesting
Make an endpoint hang, answer late, or fail after a delay, to check how your app behaves when the network is the problem rather than the server.
how-todebugging
Use a Pause and Review rule to freeze matching requests before they leave your machine, change the method, URL, headers or body, and resume or drop them. A manual breakpoint for the network.
tipsrules
Scope rules to one app, match several values at once, capture parts of a URL with regex, react to the response, and keep a library of rules you can switch on, off and share.
troubleshootinghttps
Work through the usual reasons a request doesn't appear in an intercepting proxy, from the system proxy and certificates to Node, Python, pinned certificates and localhost.