Forum Moderators: phranque
In configuring a commerce situation with 2checkout.com (2CO), the setup allows me to create both a header and a footer file in order to have the processing still appear in same layout as our website. These 2 files are then stored as html files on our own server. Then we give 2CO the URLs for each of the two files.
In these two files, the logo, a few other images, and the CSS file are all called from the httpS commerce setup pages (which obviously come from the assigned header and footer files being text-streamed via the 2CO pages).
There are two ways of setting up the situation.
EITHER
#1) use the initial ordering page on our site in its own frame (i.e., no frame at all)
OR
#2) create a frame parent to hide the order page (as one of the frames) and keep all processing of pages inside that frame (with the other, unseen top frame being set to "0" height, of course).
When the ordering page ultimately proceeds to the httpS server of 2CO, two different events occur ---depending on which of the above options is happening.
If #1 (no frame), the httpS page (at 2CO) displays the expected warning about "secure and insecure items" displayed on that page. (This is not good to have on a payment page, of course.)
But if #2 and the page is hidden inside a frame, that warning does not appear.
Is this only my browser making this difference or is this (#2) something I can legitimately count on?
Or, do I have to create the header and footer file solely without any other files being called in the HTML? (Getting my own httpS certificate is not really something all that important at this point.)
I would really like to avoid the warning message and I particularly like the frame-hiding application too. But I do not want to rely on it if this is not going to be functional overall.
Does anyone have any insight on this?
Do frames really remove that warning message?
Thanks in advance.
[webmasterworld.com...]
