A Tweeter user mentioned that, when running the CTF challenge locally, requests such as:
curl 'http://127.0.0.1/webhook?url=http://127.1'
return the following error message:
dial tcp: lookup 127.1: no such host
It looks like the URL http://127.1 was interpreted as a hostname instead of an IP address and Go tried to resolve it.
To easily debug the issue, it would be helpful to have:
- the code of the web server for the example, if it was changed from the one on the blog
- Go and OS version used to run the web server
- debug output of the library. This can be enabled by adding
EnableDebugLogging(true) to the config
Additionally, does this behavor happen with a payload like http://127.0.0.1 or any other variant of the loopback IP is used, or is it just http://127.1 causing it?
A Tweeter user mentioned that, when running the CTF challenge locally, requests such as:
return the following error message:
It looks like the URL
http://127.1was interpreted as a hostname instead of an IP address and Go tried to resolve it.To easily debug the issue, it would be helpful to have:
EnableDebugLogging(true)to the configAdditionally, does this behavor happen with a payload like
http://127.0.0.1or any other variant of the loopback IP is used, or is it justhttp://127.1causing it?