Using ModResponse
Advanced
Login & subscriptions
Changelogs
Introduction
ModResponse is our new tool that makes it easy for web developers to modify, mock, and replay HTTP response. Unlike ModHeader, which specializes in modifying request and response headers, ModResponse focuses on modifying HTTP response. With ModResponse, you can change the HTTP response body, status code, and response headers.
Known issues with ModResponse
- 1.You will see ["ModResponse" started debugging this browser] banner when ModResponse is activated. This is because it uses the debugger API, which is needed for response modification. Due to Chrome's security policy (https://crbug.com/1096262), that banner would show up on all tabs even when a tab is not being modified, and it may still for a few more seconds after ModResponse is paused or disabled. To hide it, you can run chrome with --silent-debugger-extension-api command line switch.
- 2.Clicking on the "Cancel" button on the ["ModResponse" started debugging this browser] banner will not deactivate ModResponse. To deactivate it, please open ModResponse and click on the "Pause" button. Once paused, the banner should disappear in a few seconds.
- 3.Newer versions of Chrome does not properly modify the status code and response headers due to https://crbug.com/1275920. It only modifies the response body. All modifications are working properly on Brave and Edge though.
How do I contact the support team?
The best way to reach us is to send us a message via our contact form, or send us an email at [email protected].
When will I get a response?
We will try to get back to you within 48 hours if you contact us via the contact form or through the email above. However, we receive quite a bit of spams, so some emails may get sent to our spam inbox, or we may ignore spammy inquiries. If you have not received a response from us within 48 hours, please reach out again.
Last modified 11d ago