You are not logged in.
Good day, Arnaud!
When we use useHttpApiRegisteringURIOnly with TSQLHttpServer and provide the address 127.0.0.1 (instead of '+'). It works as expected and is not reachable from 192.168.xxx.xxx or any external IP.
But if we use useHttpAsync (which i suppose is the optimal option) then the parameter is ignored and server binds on 0.0.0.0 whatever we pass.
The reason we need it, because after a penetration test the security company reported that the services listen to the addresses they should not.
So it works fine useHttpApiRegisteringURIOnly but requires admin rights (first time) even for localhost! Can't socket's implementation/fallback also consume that parameter or is there a way to force that?
Thanks you in advance.
Last edited by zensan (2026-07-28 15:00:19)
Offline
Offline
Thank you! You are the best ![]()
Offline