How to configure Stoobly to intercept HTTP(s) traffic
Before we can record or mock requests, they must first be intercepted by the agent. To do this, we can either setup the agent as a forward or reverse proxy.
Some applications have their own proxy configurations e.g. Docker. Please refer to the application's documentation when applicable.
We support two different setups for intercepting requests:
Use a reverse proxy when you have one upstream API service to intercept. This is the simplest setup as it routes all traffic for a specific domain through Stoobly.
Best for:
Single API service
Simple, straightforward routing
When you want all requests to a domain intercepted
Use a forward proxy with filter rules when you need to intercept requests to multiple different services or want fine-grained control over which requests are intercepted.
Best for:
Multiple upstream API services
Selective request interception
Applications that make requests to various domains
When you need to filter or exclude specific requests
With filter rules, you can:
Include or exclude specific URL patterns
Filter by HTTP method (GET, POST, etc.)
Apply rules to specific modes (record, mock, replay)
Control which requests get intercepted
To verify successful setup of the agent, send a requests and check the logs to see if it was intercepted. For example, send a request with curl https://docs.stoobly.com, then in the agent logs you should see:
Last updated
127.0.0.1:36368: GET https://docs.stoobly.com/ HTTP/2.0
<< HTTP/2.0 200 OK 263k