Media
4 items
Description
Modify or redirect network requests, mock APIs, delay responses, and modify headers. ModiNet - Lightweight Network Rule Manager for Chrome Redirect URLs, mock API response bodies, simulate request delays, and modify HTTP headers directly in your browser. ModiNet is a lightweight Chrome extension for frontend developers, QA engineers, and anyone who needs to test different network behaviors without configuring a proxy or running a separate debugging server. 🔄 URL REDIRECTION • Redirect matching requests to another URL • Use URL filters or regular expressions • Filter by resource type, including scripts, stylesheets, main frames, XHR/fetch requests, and images • Enable or disable individual rules • Pause or resume all ModiNet rules from the extension popup 🧪 MOCK API RESPONSE BODIES • Return a mock response body without running a backend server • Support multiple HTTP methods, including GET, POST, PUT, PATCH, DELETE, OPTIONS, and HEAD • Use JSON, text, HTML, form data, or raw response bodies • Match request URLs using wildcard patterns • Choose whether query strings participate in URL matching • Format and preview JSON while editing • Enable or disable each mock rule independently Please note: Mock API rules currently replace the response body only. Custom HTTP status codes and custom response headers are not supported in Mock API mode. ⏱️ REQUEST DELAY SIMULATION • Delay fetch and XMLHttpRequest requests • Test loading indicators, slow APIs, timeout handling, and other latency-related behavior • Configure delay time in milliseconds for each rule • Filter requests by URL pattern and HTTP method • Use Delay rules with real backend APIs • Enable or disable each Delay rule independently Please note: Delay rules apply to fetch and asynchronous XMLHttpRequest calls. Synchronous XMLHttpRequest calls are not delayed. 🔧 HTTP HEADER MODIFICATION • Set, append, or remove request and response headers • Apply one header rule to multiple request URL patterns • Optionally restrict rules to specific top-level page URL patterns • Filter rules by HTTP method and resource type • Choose separately whether query strings participate in request URL and page URL matching • Use built-in presets for common development scenarios: - CORS response headers - Cache-control headers - Security header removal - Custom Authorization headers • Create custom request and response header operations Some protected headers cannot be modified because of Chrome extension restrictions. ModiNet validates and blocks unsupported header operations when saving a rule. ✨ RULE MANAGEMENT • Manage Redirect, Mock API, Header Modify, and Delay rules in one place • Organize rules into Rule Sets and switch the active Rule Set • Move existing rules between Rule Sets while editing • Create, rename, and delete Rule Sets • Sort and filter rules by name, type, or creation order • Test URL patterns before saving • Import and export rules and Rule Sets as JSON • Enable or disable individual rules • Pause or resume all rules • Multilingual interface supporting English, Korean, and Japanese • Built-in sample rules and a demo page for first-time users 💼 USE MODINET TO • Redirect production resources to local or staging environments • Develop frontend features before backend APIs are ready • Test loading states and slow-network behavior • Override authentication or development headers • Apply header changes only when browsing specific pages • Disable caching while debugging • Test different API response-body variations • Switch between different network configurations using Rule Sets • Share rule configurations through JSON files • Reproduce network-related development and QA scenarios 🚀 GETTING STARTED 1. Install ModiNet and open the extension popup. 2. Select “Manage Rules.” 3. Choose Redirect, Mock API, Header Modify, or Delay. 4. Enter a URL pattern and configure the rule action. 5. Test the URL pattern when available. 6. Save and enable the rule. 7. Reload the target page if necessary. 🔒 PRIVACY ModiNet processes network rules locally in your browser. Your browsing history, page content, saved rule configurations, and Rule Sets are not sent to external servers by default. Rules, Rule Sets, and settings are stored in chrome.storage.local. When page URL filtering is used for Header Modify rules, ModiNet checks open tab URLs locally to apply rules only to matching tabs. Optional automation and relay features communicate externally only when they are explicitly enabled and configured by the user. 📋 PERMISSIONS ModiNet requires access to website requests so it can apply the network rules you create. Chrome may therefore display permission to read and change data on websites. This permission is used to: • Redirect matching network requests • Return configured mock response bodies • Apply request and response header rules • Match Header Modify rules against configured page URL patterns • Simulate delays for fetch and XMLHttpRequest calls ModiNet does not use these permissions to collect browsing history. 📌 CURRENT LIMITATIONS • Mock API mode supports response bodies but not custom HTTP status codes or response headers. • Delay rules support fetch and asynchronous XMLHttpRequest calls only. • Chrome restricts modification of certain protected headers. ModiNet does not impose a product or license-based limit on the number of locally saved rules. Requires a Chrome or Chromium-based browser with Manifest V3 support. Install ModiNet and start testing network behavior directly in your browser.