PDA

View Full Version : Problem with SSL and flash buttons


markblair
08-17-04, 08:16 PM
OK, something is really irritating me. I have another site that I'm working on that I just bought an SSL certificate for. The certificate is installed but when I set a link to go to https:// instead of the standard http:// I get the error message in the attachment below.

This only happens in IE. In Mozilla, Firefox and Opera, the page loads fine. If I choose 'Yes' to the error message in IE, the page loads but I don't get the lock icon showing that the page is secure. If I choose 'No', the lock icon shows and nothing looks odd on the page. I can't have this though as it looks unprofessional and would scare people away from using the site.

I found the problem though. I am using flash buttons on the site (I'm cheap so I've used the ones that come with Dreamweaver) and when I remove them from one of the secure pages, the error doesn't appear. The URL to the buttons has been tested with https:// and just the direct path being ../images/buttons, etc. I even moved the buttons into the same directory as the secure page and still the same thing happens.

I don't really want to abandon using these flash buttons. They were easy to setup and I like them. Plus I'm sure someone else out there has figured out how to secure a page with flash images or buttons on the same page. Sooo, does anyone here know how I can do this? Is there some trick I am not aware of that needs to be done? Help, I'm lost... :(

Greg
08-18-04, 12:56 AM
http://www.experts-exchange.com/Web/Q_20853401.html

http://www.macromedia.com/support/flash/ts/documents/https_error.htm - I think that could be your awnser

Hope that helps, I included the links where i got it all from.

So,

Modifying the codebase attribute will prevent end users from being confused by the Security Information dialog box.


Greg

markblair
08-18-04, 06:41 PM
Originally posted by Greg:

http://www.macromedia.com/support/flash/ts/documents/https_error.htm - I think that could be your awnser I cannot believe it was that simple. :D It was the 'codebase=http://...' command for each flash button. The 'codebase' line points to Macromedia's site so a person can install Flash if they haven't already done so. Changing it to 'codebase=https://...' fixed the problem. Thank you so much for posting that information Greg. Now I can worry about much more important things with the site this is for. ;)