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.

CommentFileSizeAuthor
#3 2644868-feeds-allow-bad-hostname.patch490 bytesdiamondsea

Comments

diamondsea created an issue. See original summary.

diamondsea’s picture

diamondsea
he/him/his
Primary language English
commented
Issue summary: View changes
diamondsea’s picture

diamondsea
he/him/his
Primary language English
commented
StatusFileSize
new 2644868-feeds-allow-bad-hostname.patch490 bytes

This patch disables hostname checking within the SSL certificate when the accept_invalid_cert option is set.

diamondsea’s picture

diamondsea
he/him/his
Primary language English
commented
Status: Active » Needs review
mmcintosh’s picture

mmcintosh commented

reviewing and testing this patch

mmcintosh’s picture

mmcintosh commented

works for me thx

brooke_heaton’s picture

brooke_heaton commented

Tested and works for my case.

brooke_heaton’s picture

brooke_heaton commented
Status: Needs review » Reviewed & tested by the community
megachriz’s picture

megachriz
Primary language Dutch
commented
Status: Reviewed & tested by the community » Fixed

Thanks 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.

  • MegaChriz committed b9a7eda on 7.x-2.x authored by diamondsea 
    Issue #2644868 by diamondsea: Skip verification of the certificate's...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.