SSL certificate hostname mismatch when consuming feed on external site

• 

  supernovia · Staff · Apr 18, 2016 at 5:34 pm

  • Copy link

  Hi @johndonohoeumuc, thanks for the extra details.

  We then found that <cffeed> still wasn’t working

  Hmmm, sorry to hear that. What errors were you getting then?

• 

  johndonohoeumuc · Member · Apr 18, 2016 at 8:17 pm

  • Copy link

  Unfortunately, the same error:

  “hostname in certificate didn’t match: <globalmedia.umuc.edu> != <*.wordpress.com> OR <wordpress.com> OR <*.wordpress.com>”

  The assumption was that <cffeed> was tied to <cfhttp> internally, but this doesn’t appear to be the case.

• 

  supernovia · Staff · Apr 18, 2016 at 10:33 pm

  • Copy link

  Hmm. I’ll see if I can dig up any more information on this. Thanks :) In the meantime, though, I’m glad you’ve got a workaround.

• 

  supernovia · Staff · Apr 18, 2016 at 11:31 pm

  • Copy link

  So we dug a bit more; while we don’t have CF for testing, one of our admins did a test with JDK 7 and it was able to pull the feed through without any trouble. So we aren’t sure why CF will not recognize it.

  I’m glad you’ve got a workaround in the meantime, though.