Unable to intercept CMD/Terminal/Powershell requests.

[Itroublve]

It all works fine to intercept requests and modify as long as it's not console based, but as soon as I try to capture requests from console it doesn't work.

ie. a discord webhook, curl -d "content=sad" -d "username=pain" -X POST https://discord.com/..../.../...., if you run that in CMD, then the request is invisible to the web proxy. Is there anyway to intercept that as well without really modifying the curl request?

Edit: After some searching, I've figured out that they don't use system wide proxies by default. But is there any workaround to it? With only the interception code?

[honfika]

If curl is not using that proxy - as you worte - , I think it is not possible. So you can not modify curl request? Why? Where is it come from? I think the easiest and best solution is ask that developer/company to add proxy support for that software which is calling the curl... only a --proxy parameter should be passed to curl somehow.

[Itroublve]

If curl is not using that proxy - as you worte - , I think it is not possible. So you can not modify curl request? Why? Where is it come from? I think the easiest and best solution is ask that developer/company to add proxy support for that software which is calling the curl... only a --proxy parameter should be passed to curl somehow.

The curl requests is used to send malicious information, which I want to in turn block. But editing the code of the request origin isn't a possibility as I have no control over when and where the request may be sent.

I'll look into it, and try to figure out a workaround, I'm currently thinking I can maybe make a virtual network adapter and monitor the requests sent over. Right now, I'm not sure if that's possible so will have to test using a VM, but I'll let everyone here know if I figure out something.