Don't launch capnet with 404 or time out

[Danielle Foré]

We were talking about how to avoid error with capnet showing when it's not supposed to and we realized a problem:

If capnet received a 404 (not found) or 408 (timeout) then it most certainly will not render a captive portal when launched. So for these two cases, we should not launch capnet since it would be useless.

[Cassidy James Blaede (cassidyjames)]

Confirmed in-person with Dan at SCALE. :)

[Gustavo Puy (info-gustavopuy)]

I'll add "sudo chmod -x etc/NetworkManager/dispatcher.d/90captive_portal_test" until bug where fixed.

That script waits for process nm-applet to start browser but I think there's not the correct approach. Something like resolve an URL before launch browser would be better.