Answer the question
In order to leave comments, you need to log in
Traffic interception for REST API development
Hello. On duty, I am developing REST API for various mobile applications. Sometimes it becomes necessary to see what requests our application sends and how the server responds to it. In addition, sometimes you need to change the data in the request and check the application. Technically, I imagine this as a proxy that is running on the local network and to which all traffic is redirected, for example from a test WiFi point. This proxy has an address where I can go and see all the requests that it caught, put a block on some request, or do some other dirty trick / grace. Do you know similar tools? Or you will have to write such a tool yourself.
Answer the question
In order to leave comments, you need to log in
Um… why not just add a request/response logging system to the rest-API? Substitution of data in requests? again, why not just compose your own and send it through the same curl ...
ps I do the same myself, but somehow there has never been a need to monitor what someone sends. What for?
You can write a local (in your network) proxy for your protocol and redirect traffic to it through the substitution of the local DNS record.
With this option, all the cards are in your hands by data substitution + you can “intercept” SSL traffic (you also have your certificate).
Cons - you need to freeze.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question