Jump to content
iwato

HTTP and HTTPS Compatibility

Recommended Posts

BACKGROUND:  Sometimes I believe that I will never launch my project.  The reason for this doubt is clear.  Each time that I believe that I have got everything right, I make a small change that i am told will make everything better, and I finish by having to redo much of what I have already done simply to make it work as it did before with the new feature.  What keeps me going on the other hand is that I have always somehow been able to overcome each of these sorts of major hurdles.  No wonder it has taken me 14 months just to be able to get where I have gotten.

DILEMMA:  In order to observe the issue that I am having you are requested to follow the steps below.  Mind you, the result of the experiment appears to be the same no matter the browser.  I have tried it with Chrome, Safari, and Firefox.

Step 1:  Using the http:// protocol open to the following splash page: http://www.grammarcaptive.com

Step 2:  Click on the Freeman.  This should open to a page with two preceding splash pages

Step 3:  When the 2nd splash page opens, you should see what appears to be a frame with a series of frames in which each frame is still another set of frames.

_______

Step 4: Using the https:// protocol  open to the following splash page:  https://www.grammarcaptive.com. 

Step 5: Click on the Freeman.  This should open to a page with two preceding splash pages.

Step 6: When the 2nd splash page opens, however,  the nested sets of frames have disappeared.

_______

DISCUSSION:  Now, I have made what I believe to be a fairly thorough check for the presence of the https:// prefix on all pages that refer to a link containing Javascript that might influence the behavior of the splash pages in question.  I suspect that by having changed the prefix from http:// to https:// that I have, at least for some pages,  introduced new code that is no longer compatible with the Javascript code that I am using.  My Javascript console tells me that the jQuery variable is missing.

Any ideas?

Roddy

Share this post


Link to post
Share on other sites

In your HTTPS page all the Javascript files should also be loaded with the HTTPS protocol because the browser does not allow loading unencrypted content on an encrypted page.

This file on your page is still using unencrypted HTTP: http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js

  • Thanks 1

Share this post


Link to post
Share on other sites

Yes, you are right.  I simply forgot to upload a block of files whose prefix I had changed on my test server, but failed to upload to my host server.

Thanks!  I simply could not bear the thought of having to do everything all over again.

I feel so relieved.

Have a great weekend!

Roddy

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×