Look more closely.
You need to respond with the right header. ConnMan looks for 'X-ConnMan-Status'
header with value of 'online'.
This is how to do it with nginx
server {
server_name someserver;
access_log /var/log/nginx/connman_access.log;
# 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;
}
}
It's a good design decision. HTTP 200 is not a guarantee, especially with ISP
based redirects when DNS lookups fail.
Sam Nazarko,
https://osmc.tv
-----Original Message-----
From: connman [mailto:[email protected]] On Behalf Of Ernast Sevo
Sent: 08 July 2015 22:34
To: [email protected]
Subject: connman online test
Hello!
I have been wanting to switch the status URL to point to a server that I have
setup and have applied the following patch to my connman
(1.27):
diff --git a/src/wispr.c b/src/wispr.c
index ef4bdab..9480cab 100644
--- a/src/wispr.c
+++ b/src/wispr.c
@@ -30,7 +30,7 @@
#include "connman.h"
-#define STATUS_URL_IPV4 "http://ipv4.connman.net/online/status.html";
+#define STATUS_URL_IPV4 "http://foo.bar.com/status.html";
#define STATUS_URL_IPV6 "http://ipv6.connman.net/online/status.html";
struct connman_wispr_message {
I assumed that this would be the only thing required to make this happen,
however none of my networks actually go online. I have confirmed that I can
wget the status file once the network goes to ready but unsure why connman is
failing to do the same. Am I missing something?
Thanks,
Ernast
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman
