Re: HTTP GET usage for Ready to Online state transition

Currently, ConnMan uses an http get operation to transition a service from Ready to Online state. This is implemented in the wispr module, where a hard-coded http url is used: #define STATUS_URL_IPV4 "http://ipv4.connman.net/online/status.html" #define STATUS_URL_IPV6 "http://ipv6.connman.net/online/status.html" Additionally, the http server must return a custom header in the reply: "X-ConnMan-Status" This is a problem for us, as we are planning to release a product, which must not depend on the ConnMan's http server. I think we need to make a change to add a config field, which allows the user to: - provide a custom http URL - disable http get - automatically transition from Ready to Online state - let the application detect the end-to-end connectivity I am not sure what to do with the "X-ConnMan-Status" http reply header. Should checking of it be disabled in case the config provides a URL from the user? I realise that this functionality is also used to detect proxies, so I would keep the current code as default, and provide an optional config field to change wispr URL or disable it. Does this make sense? It is an issue we definitely have to address to use ConnMan. I would like to make changes, which would be usable by others too.