Skip navigation
Currently Being Moderated

Secure Donation Page (HTTPS) has an Error

Apr 12, 2012 2:57 PM

Tags: #https #ssl #securityerror

My clients website donation page = https://wildlifewaystation.worldsecuresystems.com/donation-for-rescued -animals shows an error next to the URL. If you look at the source code I updated all links to https as BC instructed me to except one-I can't get rid of the one http protocol on the <html> element. What am I doing wrong. Why is the page SSL still showing an error? Is it the darn <html> html tag showing http instead of https or another possibility?

 

 

Regards,

Richard R

intergratedwebbusiness.com

 
Replies
  • mario_gudelj
    1,679 posts
    Oct 13, 2010
    Currently Being Moderated
    Apr 12, 2012 3:07 PM   in reply to richirich33

    Hi Richard,

     

    It looks fine to me in Chrome and Firefox on Mac. Here are some screenshots:

     

    wild1.jpg

    wild2.jpg

     

    I also had a look at all 37 requests and they're all https:// request. Are you seeing this in some weird Chrome version? Have you tried updating to the latest one? Also, try clearing your cache.

     

    Cheers,

     

    Mario

     
    |
    Mark as:
  • mario_gudelj
    1,679 posts
    Oct 13, 2010
    Currently Being Moderated
    Apr 12, 2012 3:08 PM   in reply to mario_gudelj

    BTW, PayPal express orders will not be created in BC. Customers will be sent to PayPal and the funds will be collected, but BC will not know about them.

     

    -mario

     
    |
    Mark as:
  • Liam Dilley
    6,690 posts
    Feb 28, 2012
    Currently Being Moderated
    Apr 12, 2012 3:32 PM   in reply to mario_gudelj

    One Chrome build had a false positive bug showing errors even when there were none under HTTPS. Other issues come from some Chrome Plugins.

     
    |
    Mark as:
  • mario_gudelj
    1,679 posts
    Oct 13, 2010
    Currently Being Moderated
    Apr 12, 2012 5:30 PM   in reply to richirich33

    I tested this in other browsers and none of them have this problem. It seems to be Google Chrome issue. I did some digging around and came across this http://zach.be/2011/11/chrome-https-issue/

     

    What you'll need to do is replicate that template and in the new template set all the paths to absolute http://wildlifewaystation.org/ pathes, then wrap the secure pages into that template. Browsers shouldn't complain about the http:// hrefs. They only throw that error is there is a GET request going to a non-secure resource.

     

    Cheers Richard.

     

    -m

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points