You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for the awesome app.
I just miss one feature: Being able to redirect the unmapped routes to a host that is behind a proxy.
Background:
Usually, we don't map all routes and the unmapped routes are redirected to a host that we call "proxy" within the app. However, that host is sometimes behind a actual HTTP or SOCKs proxy. This way, I can't forward the unmapped routes to that host.
Request:
Being able to start Mockoon and set a HTTP/SOCKs proxy via command line. Like Google Chrome, for example: "C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server=socks5://127.0.0.1:1082
This is the only feature that I miss.. being able to work with APIs that are behind a actual proxy.
Sorry if this is already supported but every time I search for something, Google keeps me suggesting the "Proxy" feature already in the app
Again: Thanks!
The text was updated successfully, but these errors were encountered:
Hello.
First, thank you for the awesome app.
I just miss one feature: Being able to redirect the unmapped routes to a host that is behind a proxy.
Background:
Usually, we don't map all routes and the unmapped routes are redirected to a host that we call "proxy" within the app. However, that host is sometimes behind a actual HTTP or SOCKs proxy. This way, I can't forward the unmapped routes to that host.
Request:
Being able to start Mockoon and set a HTTP/SOCKs proxy via command line. Like Google Chrome, for example:
"C:\Program Files\Google\Chrome\Application\chrome.exe" --proxy-server=socks5://127.0.0.1:1082
This is the only feature that I miss.. being able to work with APIs that are behind a actual proxy.
Sorry if this is already supported but every time I search for something, Google keeps me suggesting the "Proxy" feature already in the app
Again: Thanks!
The text was updated successfully, but these errors were encountered: