Last updated: September 5, 2026

ResReq is a DevTools extension for Google Chrome, Microsoft Edge, and Mozilla Firefox that helps developers inspect, format, and copy complete HTTP request and response exchanges.


ResReq processes captured network request and response information strictly locally within the user's browser DevTools panel. ResReq does not operate a remote server, analytics service, or cloud backend that receives, logs, or stores captured network traffic.

Captured entries are kept in temporary browser memory solely for the current DevTools session. Using Clear all removes all entries from memory. Closing the DevTools window immediately clears all session state.


HTTP traffic frequently contains sensitive credentials, such as authentication tokens, session cookies, CSRF tokens, and API keys. ResReq automatically masks common sensitive headers by default across the UI and export generators. Users may explicitly toggle Sensitive to view or copy unmasked values for authorized local debugging.

Users are responsible for avoiding accidental disclosure of sensitive credentials when copying or sharing HTTP exchanges.


ResReq requests only the standard permissions required to operate within DevTools:
- devtools APIs: To create the ResReq panel and listen to network request events in the inspected tab.
- clipboardWrite: To allow the user to copy exchanges, cURL commands, and JSON structures to their system clipboard upon clicking copy controls.

ResReq requires zero host permissions (<all_urls>), zero background service workers, and zero content scripts injected into user pages.

• Google Chrome Web Store: Complies with the Chrome Web Store Single Purpose Policy and Data Usage Policy (zero remote data transmission).
• Microsoft Edge Add-ons: Certified for Microsoft Edge Add-ons with no external tracking.
• Mozilla Firefox Add-ons (AMO): Explicitly declares browser_specific_settings.gecko.data_collection_permissions: { "required": ["none"] }.

If ResReq's data practices change, this policy will be updated before any such changes are published to web stores.


Replace this section with your developer/publisher contact email or GitHub issues link prior to public store submission.