[ 
https://issues.apache.org/jira/browse/NUTCH-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18135404#comment-18135404
 ] 

Hudson commented on NUTCH-3221:
-------------------------------

SUCCESS: Integrated in Jenkins build Nutch ยป Nutch-trunk #281 (See 
[https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/281/])
NUTCH-3221 HTTP protocols to verify TLS/SSL certificates by default (snagel: 
[https://github.com/apache/nutch/commit/e29a1d46a75a929dc2ddf2a6b0c2e31f4a46d201])
* (edit) 
src/plugin/lib-http/src/java/org/apache/nutch/protocol/http/api/HttpBase.java
* (edit) conf/nutch-default.xml


> HTTP protocols to verify TLS/SSL certificates by default
> --------------------------------------------------------
>
>                 Key: NUTCH-3221
>                 URL: https://issues.apache.org/jira/browse/NUTCH-3221
>             Project: Nutch
>          Issue Type: Bug
>          Components: protocol
>    Affects Versions: 1.23
>            Reporter: Sebastian Nagel
>            Assignee: Sebastian Nagel
>            Priority: Major
>             Fix For: 1.24
>
>
> Verification of SSL/TLS certificates is off by default 
> (http.tls.certificates.check = false).
> If verification is off, a no-op X509TrustManager is used in the protocol 
> implementations to bypass the verification.
> For a web crawler, it can be a valid use case to skip the certificate 
> verification, in order to crawl sites with expired or self-signed 
> certificates. But this shouldn't be the default.
> See also 
> [stormcrawler#2079|https://github.com/apache/stormcrawler/issues/2079].



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to