Handle edge cases in Playwright route.fulfill()/route.fallback() network mocking, including handler chaining and forbidden header overrides
domain: playwright.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register page.route() handlers before navigation so no requests race past unhandled
Use route.fallback() instead of route.continue() when the next matching handler in the chain should still run, since route.continue() sends immediately and skips remaining handlers
Remember handlers registered later run first (LIFO order), so register the most specific mock last if it must win
To edit a live response body, call route.fetch() to get the real response then route.fulfill() with the modified body, since route.continue() cannot change response content
Know that some request headers (Cookie, Host, Content-Length, etc.) are forbidden and cannot be overridden via route.continue()'s headers option
Known gotchas
route.continue() sends immediately and skips remaining matching handlers, while route.fallback() lets the next matching handler run first
Forgetting to resolve every matched route with fulfill/continue/abort leaves the request hanging indefinitely
Bundlers can split one logical resource into several sub-requests, so a route pattern matching the entry file may miss chunked assets
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?