Improve HealthCheck command#119
Conversation
This makes curl follow the redirect from http to https. Also disables SSL verification so that we can check the health if https is using some certs signed by a private, not trusted by default CA. As this connects from the container to the container that shouldn't be a security issue (if someone's doing a MITM inside the container, we have worst problems to deal with)
|
The reason for the current health check is documented here: #39 |
|
Well I tried and i see no error popping up And the problem with the current curl command is that if http->https is on, it will just check that the server is responding and Another solution would be to reply for the health-checks on the http endpoint but that would require codebase changes I am currently using the suggested change with no apparent issues. So I don't really understand why it should stay like that If you want me to try anything else pls let me know |
This makes curl follow the redirect from http to https. Also disables SSL verification so that we can check the health if https is using some certs signed by a private, not trusted by default CA.
As this connects from the container to the container that shouldn't be a security issue (if someone's doing a MITM inside the container, we have worst problems to deal with)