Checkout page not loading as a secured page

Discussion in 'HTML & Website Design' started by relic180, Nov 2, 2009.

  1. #1
    I'm having an issue making my checkout pages load in a browser with the little padlock icon showing up. From what I can tell, everything on the page is coming from an 'https' source... but the thing that's really confused me is that if you simply reload the page then it is secured.

    Also, only the first page of the checkout process seems to have this problem. Once you enter your information and go the second page then it is fully secure and the padlock shows up. The biggest problem with this is that users are suppose to enter their credit information on the first page so that padlock really needs to be there.

    I've tested in IE7, IE8, FF3, FF3.5, Opera10 with the exact same results. Not secured, but refreshing the page makes it secure. Also, it only seems to behave this way about 80-90% of the time. Occasionally, I've gotten it to load up the first checkout page securely. Also, I tested in Chrome and I get a security error on everypage even after reloading.

    The site is located here:
    http://www.skullcrow.com
    NOTE: This site contains mature language. FYI.

    One last thing, I'm having more difficulty troubleshooting this as I don't really know how to ask any of the browsers so far how to tell me specifically what on the page is not loading securely. The closest I can get is to get a warning from IE asking if I only want to display the secure stuff, then I have to figure out what didn't load up on the page. Is there a better way than this?

    Thanks for any help.
     
    relic180, Nov 2, 2009 IP
  2. relic180

    relic180 Peon

    Messages:
    7
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #2
    Finally figured out the problem with some help from FF firebug addon.

    The google search box from the previous page was sending out a request for an 1x1 pixel gif file after leaving that page (apparently another browsing behavior data gathering by google). The transfer happened in http but occured during the next page load. Fortunately, users only go to checkout from one page on the site so by removing the search box from the shopping cart page, the checkout pages become secured and problem solved.

    More details can be found here, if anybody else runs into this:
    http://groups.google.com/group/google-ajax-search-api/browse_thread/thread/be3a5224f157f9ba/eaafa0b9de12699e?show_docid=eaafa0b9de12699e&pli=1
     
    relic180, Nov 2, 2009 IP