Home / server / Questions / 1108041
In Process
janneb
Asked: 2022-08-13 04:25:47 +0800 CST

traceroute for HTTP

  • 772

I'm trying to track down an elusive issue where a particular URL refuses to work. My investigations so far suggests there's some kind of DPI firewall/proxy/whatever between the client and server that looks at the path of the request and refuses based on that, and I'd like to known where that one is so I know who to contact to resolve the issue. In short

curl http://server/path   # FAILS with HTTP 401 Access Denied
curl https://server/path  # WORKS
(client on another network)# curl http://server/path  # WORKS
curl http://server/another_path # WORKS

So I'm wondering if there is some kind of traceroute-like tool that would work with HTTP. Basic traceroute doesn't work, because I can't tell traceroute to send a well-formed HTTP request with the particular path that is causing problems. I found https://github.com/watson/http-traceroute but that tracks only HTTP redirects, and doesn't help with this particular issue. Any ideas?

EDIT No, the server is not managed by me. It's a publicly accessible server managed by another organization entirely.

http

0 Answers