Check how requests sent through the proxy server look at the destination

My web application makes a request to third-party servers, and we sometimes route them through proxies. I would like to be able to "see what they see" - to see what the request looks like once it has been passed through the proxy.

In particular, I am interested in how much identification information about the source (my web application) is left in the request after it reaches the destination by routing through the proxy server.

Does anyone know an easy way to do this? Maybe a web service that will simply reflect all the information about the incoming request in the outgoing response?

+4
source share
3 answers

Not a complete answer, but maybe you can try:

http://www.cantoni.org/2012/01/08/simple-webservice-echo-test

And the other 2 web pages mentioned there: http://respondto.it/ http://requestb.in/

To set up a URL to send your requests and see if the information helps you.

+3
source

I just declare that this is an idea that came to me. You can try sending requests to your own URL that you control (i.e., the Resource in your own web application). That way, you can use the debugging infrastructure or other objects (basically anything) to test the request coming into your application. I think this may be the most powerful / easiest way to do this. It will not allow you to check the URL that you tried to test, but from the point of view of the proxy server visibility this may be what you need.

Good luck

+2
source

If the proxy server supports the TRACE method and the Max-Forward header, you can use it. However, not all.

+1
source

All Articles