Why is Ipv4StatusUrl/Ipv6StatusUrl needed in /etc/connman/main.conf? [answered]

Thanks! I set up my own nginx server to tackle this.

server {
   listen $IPV4ADDRESS;
   listen [$IPV6ADDRESS]:80;
   server_name ipv4.cm.example.com ipv6.cm.example.com;

   access_log /var/log/nginx/connman_access.log mainlog;
   error_log /var/log/nginx/connman_error.log;

   client_max_body_size 128K;
   root /var/www/html/connman;

   location / {
       add_header X-ConnMan-Status online;
   }
}

Then added a fairly empty index.html.

For Apache admins:

<Location /return_204>
    Header always set X-ConnMan-Status "online"
</Location>
RedirectMatch 204 ^/return_204$

Do these configs still work?

I'm trying to hack the network status by running nginx on the phone, and pointing connman to the local server.

nginx works fine, and has the required X-ConnMan-Status header, I also tried setting it to return 204 status but it seems to break the status checker

@r0kkerz You need only to return the X-ConnMan-Status header OR http status code 204. Both do work, per default we use http status code 204 because some networks have proxies which are removing http headers for no reason.

I can confirm that the nginx config still works for me. However, returning HTTP 204 may be a better solution in some networks. For my network provider, there are no HTTP header filtering so it works well.