Hi Mike, did you check that every, i repeat, every single link, image, js or stylesheet file beginns with either https or has a relative path?
That's one of the main reasons why browsers don't accept certificates. Greetings Max Am 09.06.2010 um 17:06 schrieb Mike Doel: > Our app supports two sites: > > www.vacationtrade.com > www.rrbo.com > > I have uploaded SSL certificates for both, and heroku ssl:add gave me > positive assurances that it understood both by telling me what domains they > were for. > > However, we're having problems with the www.rrbo.com one in some > browsers/platforms. If I go to > > https://www.rrbo.com > > in Chrome on Mac, everything appears to work just fine. I can click the > "lock" icon in the browser and it shows me a valid certificate for > www.rrbo.com. But, if I use either IE or Chrome on Windows, I get browser > error message. And in Chrome in particular, it tells me that it's being > served a certificate for www.vacationtrade.com instead of www.rrbo.com. > > So, is this a heroku bug where it's giving out the wrong certificates in some > cases? Is it a problem with how we configured our certificates? > > Anyone have any clues? > > I've opened a ticket on this, but it's gone unanswered for two days (grumble, > grumble). > > Mike > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
