[Bug 699509] Support NetworkManager connectivity checking



https://bugzilla.gnome.org/show_bug.cgi?id=699509
  sysadmin | Other | unspecified

Jeff Schroeder <jeffschroeder> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeffschroeder computer org

--- Comment #2 from Jeff Schroeder <jeffschroeder computer org> 2013-05-03 00:11:12 UTC ---
What about a page off of the main networkmanager site?

http://projects.gnome.org/NetworkManager

Dan, could you create a page there named online with the contents of something
like:
"NetworkManager is online"


http://projects.gnome.org/NetworkManager/online

Then in the projects.g.o apache vhost config I'm relatively confident
(untested) this will work:

<Location /NetworkManager/online>
  Header unset ETag
  Header set X-NetworkManager-Status online
</Location>

Then in the nm code you could do a HEAD http request like I simulate here with
netcat:

[jschroeder desktopmonster ~]$ nc projects.gnome.org 80
HEAD /NetworkManager/ HTTP/1.1
Host: projects.gnome.org        

HTTP/1.1 200 OK
Date: Fri, 03 May 2013 00:07:52 GMT
Server: Apache/2.2.15 (Red Hat)
Last-Modified: Thu, 02 May 2013 10:06:26 GMT
ETag: "1abf6-195d-4dbb9632a6c80"
Accept-Ranges: bytes
Content-Length: 6493
Connection: close
Content-Type: text/html; charset=UTF-8

That should be less overhead than a GET request even if only marginally. It
would also not include the ETag which doesn't make a lot of sense for checking
if the host is online.

Thoughts gentleman? A subdomain seems massively overkill when you can do this
faster with an apache config tweak.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the QA contact of the bug.
You are watching the assignee of the bug.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]