- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 4.6k
Connectivity check: test https OR ELSE http #31426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| That means that an SSL expiration problem for instance would not be spotted if the http version works? I understand that more and more domains are not available by http, but I feel like https should always work? | 
| @come-nc I agree. How about only testing https? It feels a bit harsh... Another (heavy) solution would be to have a config setting to choose which protocol is tested in this connectivity check. | 
| I did not understand the context at first, but this is only used to test whether the server has internet access. Other solution would be to allow putting URIs with protocol instead of just domains in the config, but I would say that is overkill for this feature. | 
| 😁 The context is someone who does not have proper internet access but who needs this test to pass to use a custom appstore URL. So they provide custom  | 
79e0584    to
    e147127      
    Compare
  
    | @come-nc Rebased on master, added method signature types. It would be awesome to backport this to stable23 and stable22. | 
| My fear is that http is a lot less useful check, you may be on a network where all external accesses are redirected to a blocker page. With https this would be detected. | 
e147127    to
    135fcbe      
    Compare
  
    Signed-off-by: Julien Veyssier <eneiluj@posteo.net>
135fcbe    to
    d5574cf      
    Compare
  
    | @come-nc Great, nice catch, thanks for the feedback. | 
| Drone failure seems unrelated. | 
| /backport to stable23 | 
| /backport to stable22 | 
Instead of https AND http.
As tested domains can be set by admins with
connectivity_check_domainsconfig value, we can't know for sure those domains are reachable with both http and https.This avoids the connectivity warning in admin setting's overview section when a domain is only accessible via either http or https.