Merge ~jbicha/network-manager:master into network-manager:master
| Status: | Rejected | ||||
|---|---|---|---|---|---|
| Rejected by: | Jeremy Bicha on 2017-08-27 | ||||
| Proposed branch: | ~jbicha/network-manager:master | ||||
| Merge into: | network-manager:master | ||||
| Diff against target: |
64 lines (+29/-0) 4 files modified
debian/20-connectivity.conf (+3/-0) debian/changelog (+9/-0) debian/control (+16/-0) debian/network-manager-config-connectivity.install (+1/-0) |
||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Aron Xu | 2017-02-22 | Needs Information on 2017-02-23 | |
|
Review via email:
|
|||
Description of the Change
By adding a separate package for this config snippet, it enables Ubuntu flavors to easily opt into the NetworkManager connectivity status check by recommending this package. Ubuntu users can easily override the default by installing or uninstalling this package.
I will be proposing this for zesty Feature Freeze Exception and I will bring it up for discussion on the ubuntu-devel list, so let's wait to merge until we get approval.
| Jeremy Bicha (jbicha) wrote : | # |
Aron, could you ask someone in Canonical's web development about your first question?
I think this will have zero affect on other network operators. (All the other major operating systems do basically the same thing and almost anything else that uses the web will have a bigger effect.)
I don't know anything about #2. I think generally these network-
Also, could you maybe bring up your concerns on the ubuntu-devel list thread I started so that more people will see?
| Jeremy Bicha (jbicha) wrote : | # |
There are many other URIs that work. Some I know of are:
http://
http://
http://
http://
I think it would be preferable for it to be Canonical-hosted though.
| Saurav Sengupta (sauravsengupta) wrote : | # |
Does that Lorem ipsum response for the uri in this proposal work? It didn't work for me on Ubuntu GNOME 16.10 (the login popup appeared with the root page open for nmcheck.gnome.org). I think it should be something like response=<!DOCTYPE HTML PUBLIC for uri=http://
- fe4efd3... by Jeremy Bicha on 2017-02-24
| Jeremy Bicha (jbicha) wrote : | # |
Saurav, thanks for the feedback. Yes, I see that the start.ubuntu.com URI does not work. I am going to see if I can find someone at Canonical that can set up one that works. Meanwhile, I'll set the URI to Debian's which I did test.
You also saw something else because gnome-shell hardcodes a nmcheck.gnome.org URI which I think we'll want to patch out:
https:/
| Saurav Sengupta (sauravsengupta) wrote : | # |
A bit off-topic here, but if you're going to patch the portal helper, could you also see if the window can be made to remain in the background (perhaps insert a set_keep_below call (https:/
| Jeremy Bicha (jbicha) wrote : | # |
This has been merged in, similarly but slightly differently in Artful and Debian unstable.
Unmerged commits
- fe4efd3... by Jeremy Bicha on 2017-02-24
- a274d13... by Jeremy Bicha on 2017-02-22
- b2bcc9a... by Barry Warsaw on 2017-02-17
- c86a11b... by Barry Warsaw on 2017-02-16
- 74f78d0... by Martin Pitt on 2016-12-02
- 0daf8f8... by Martin Pitt on 2016-12-01
- 1564f7d... by Barry Warsaw on 2017-02-16
- 4a73ffc... by Mathieu Trudel-Lapierre on 2017-02-16
- 80710c3... by Aron Xu on 2017-01-12
- a57df67... by Aron Xu on 2017-01-12


I have a few questions:
1. Whether the 5-minute checks will congest Canonical's web servers? Or local network operators may see a lot of Ubuntu desktops flooding the same request so frequently.
2. How to deal with caches? Google uses HTTPS + 204 response code, and Apple uses HTTPS + text file. The approach we are using is more likely to the latter one, but it does not support HTTPS.