I am using http-request-plugin to call an API end point using HTTPS. The cert associated with the domain has expired so I would expect the API call to fail, but low and behold the call succeeds and even claims a HTTP 200 header response. I don't know whats happening under the covers so not sure if this is a bug or an improvement/feature, but I am 100% certain it's not using HTTPS or some flag is being used internally to circumvent TLS.
HTTP mode: GET
Here is curl example showing the cert in question has expired:
$ curl -i "https://internal.rpm.datapipe.senderscore.net/health"
curl: (60) SSL certificate problem: certificate has expired
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
Jenkins console output snippet follows from project build that uses the HTTP Request setup I illustrated above:
Sending request to url: https://internal.rpm.datapipe.senderscore.net/publishfile/tusko_message_stream-3.0.0-SNAPSHOT20170210153816.noarch.rpm
Response Code: HTTP/1.1 200 OK
Success code from [100‥399]
If you need a URL to test/debug against that currently has an expired Cert you can use this one but be warned it'll probably stop resolving in the next couple of months:
curl -i "https://metrics.datapipe.senderscore.net/"