Results 1 to 8 of 8

Thread: Problem with https feeds?

  1. #1

    Problem with https feeds?

    I am having a problem with one of my podcasts and, after talking to them, they said it could be because they have changed their feed to the more secure "https". Here is what they say:

    "If your podcast client is giving you errors, it is most likely because your podcast client is not forwarding automatically from http to https. Check the settings to see if there is the option to enable this automatic forwarding. If there is no such setting, you many need to unsubscribe and re-subscribe under the new https url."

    I don't see any settings for this forwarding issue, is this something I need to figure out? the feed itself is:

    https://gigaom.com/tag/chrome-show/feed/

    This is showing an inability to get to the feed. Any suggestions?

  2. #2
    Junior Member
    Join Date
    Apr 2013
    Posts
    2
    I have the same issue with the same podcast. Is this something that can be fixed soon?

  3. #3
    BeyondPod Team
    Join Date
    Feb 2012
    Posts
    1,033
    We looked into this. It seems like something is wrong with their certificate (or at least the way Android interprets it).

    The error that we get is:

    SSLException - hostname in certificate didn't match: <gigaom.com> != <*.wordpress.com> OR <*.wordpress.com> OR <wordpress.com>.
    For some reason Android thinks that the certificate is for wordpress.com (my thinking is that they used to host it there at some point).

    One way to work around this is to get the feed through Feedly. You can find more information here: http://www.beyondpod.mobi/android/help/Feedly.htm.

  4. #4
    Stefan, here is their page explaining the change they made, maybe it will make more sense to you than me:

    http://support.gigaom.com/hc/en-us/a...ment_200527395

  5. #5
    Stefan, it seems they are saying it is a problem on the players side, not managing the SSL right. If you say it is on their end, I will take it back to them and let them know.

  6. #6
    The podcast producer gave me a workaround:

    "We confirmed the certificate errors your seeing and, unfortunately, cannot find a workaround until we get a specific type of domain mapping support from our hosting provider.

    There is a workaround though. If you replace the feed url with a search URL BeyondPod should be able to read the feed without error. Please use the following URL for the Chrome Show:

    http://search.gigaom.com/tag/chrome-show/feed/

    Hope that fixes it for you!"

  7. #7
    BeyondPod Team
    Join Date
    Mar 2012
    Location
    UK (BP Team member from Jun 2012 to Mar 2017), http://blog.juwlz.co.uk/
    Posts
    4,169
    And does it?

  8. #8
    yes, it does!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •