Skip to content
This repository has been archived by the owner on Nov 5, 2021. It is now read-only.

[Feature Request][Documentation] Example on how to use the HTTP probe with TLS/HTTPS/443 #380

Open
DenisBiondic opened this issue Mar 12, 2020 · 2 comments

Comments

@DenisBiondic
Copy link

I've searched quite a while on how to use HTTP probe when you want to probe 443 instead of 80. I managed to do so by specifying the 443 port, but then I get issues from the backend servers such as HTTP 400: the plain http request was sent to https port

If there is such documentation, can you point me to the right place? Even if it exists, is should be perhaps more prominent somewhere in the examples.

P.S. I've also found out that the cloudprober follows the redirect, so currently what we do is we probe the port 80, we get the 3xx redirect and then the 443 is probed, but I would like to prevent the extra redirect request on every probe...

@DenisBiondic DenisBiondic changed the title [Feature Request][Documentation] Example on how to use the HTTP probe with TLS [Feature Request][Documentation] Example on how to use the HTTP probe with TLS/HTTPS/443 Mar 12, 2020
@manugarg
Copy link
Contributor

Sorry for the insufficient (not so user-friendly) documentation.

Probe config options can be derived from the protobuf fields. For example here is the config protobuf for the HTTP probe type:
https://github.com/google/cloudprober/blob/master/probes/http/proto/config.proto

There are also some examples in the examples directory, though they are not easy to find too.

We'll try to improve the documentation, but for your particular use case, you need to configure 'protocol' as HTTPS:

probe {
  type: HTTP
  http_probe {
    protocol: HTTPS
    url: ...
    port: ..
  }
}

Hope this helps for now.

@DenisBiondic
Copy link
Author

thx! that was exactly what we were looking for :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants