Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Issue #1062178: Add configuration option to allow invalid/unverified or (self certified) SSL certificates allows you to allow an invalid or self-signed SSL certificate. However, it does not allow the use of certificates with a different hostname than the current site. In this case it displays an error such as
ERROR: cURL error (51) SSL: certificate subject name '*.acquia-sites.com' does not match target host name 'dev.multisite.example.com' for https://dev.multisite.example.com/feeds/example.json
This can be allowed by setting the CURLOPT_SSL_VERIFYHOST option to 0.
Comment | File | Size | Author |
---|---|---|---|
#3 | 2644868-feeds-allow-bad-hostname.patch | 490 bytes | diamondsea |
|
Comments
Comment #2
diamondseaComment #3
diamondseaThis patch disables hostname checking within the SSL certificate when the accept_invalid_cert option is set.
Comment #4
diamondseaComment #5
mmcintosh CreditAttribution: mmcintosh commentedreviewing and testing this patch
Comment #6
mmcintosh CreditAttribution: mmcintosh commentedworks for me thx
Comment #7
brooke_heaton CreditAttribution: brooke_heaton as a volunteer commentedTested and works for my case.
Comment #8
brooke_heaton CreditAttribution: brooke_heaton as a volunteer commentedComment #9
MegaChriz CreditAttribution: MegaChriz as a volunteer commentedThanks for testing. I checked what
CURLOPT_SSL_VERIFYHOST
actually is: verifying if the name in the certificate is equal to the server name. I looks okay to me skip this verification when you already enabled the option to accept invalid SSL certificates.Committed #3.