[JIRA] (JENKINS-41934) HTTPS/TLS Cert check bypassed

[jcrotty_alp...@hotmail.com (JIRA)]

Title: Message Title

Joseph Crotty created an issue   Jenkins / JENKINS-41934 HTTPS/TLS Cert check bypassed Issue Type: Bug Assignee: Janario Oliveira Components: http-request-plugin Created: 2017/Feb/10 4:39 PM Environment: Jenkins ver. 2.32.2 LTS (i.e., docker 2.32.2:latest) HTTP Request Plugin 1.8.13 All plugins are current Priority: Major Reporter: Joseph Crotty 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 a improvement/feature, but I am 100% certain it's not using HTTPS or some flag is being used internally to circumvent TLS. URL: https://internal.rpm.datapipe.senderscore.net/publishfile/$ {RPM_FILE} HTTP mode: GET Jenkins console output snipped follows HttpMode: GET URL: https://internal.rpm.datapipe.senderscore.net/publishfile/tusko_message_stream-3.0.0-SNAPSHOT20170210153816.noarch.rpm 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] Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.