Hi, you’re right it’s not litterally a “bug”. It’s more a strange behavior (that’s why i posted in General section).
Sorry ! it’s right i didn’t checked the last commit because i’m working with fog only in a special environment and i was on others things last days.
It can’t be the ip directly because when you’re hosting the fog webservice in a VirtualEnv environment, you must pass the complete subdomain/domain for your webserver to redirect accordingly. So the client as to send his POST/GET commands to the hostname not the ip !
Hosting services in VirtualEnv is common.
Sure, it’ll work if your fog virtualenv is configured as the default one (pointing to the ip will redirect the webserver to the default virtualenv and it’ll will works), but if you host several webservices on the same webhost (or webhost farm) AND fog is not the default one, you must pass the domain name and not the IP. If you don’t do this, the webserver will answer back with your default virtualenv which can be anything but fog.
BTW, in my opinion, resolving a hostname is a client behavior.
Thanks for your time !