Question about 2Checkout & "Secure and Insecure Items" warnings

HttpS calling Header & Footer files from my server, do frames remove msg?

[MultiMan]

Not sure if my question belongs here, but I first posted it in "Webmaster General"

[webmasterworld.com...]

[Abdelrhman Fahmy]

Just adding the HTTPS to the images and objects tags will remove the security warning message,you don't have to add it to the links tags,also you should upload the header and footer again.

Abdelrhman,

[MultiMan]

Thank you for trying. I tried your suggestion, and just as I thought, that did not work because the images and css file are NOT actually stored on an httpS server. When doing it that way, the images and CSS file do not even come in. But thanks for trying!

[wackal]

Abdelrhman is right, you need to check your image and object links. they should all begin with https://

there is no such thing as an https server. the ssl cert is registered to the server and that server can then serve both secure and non secure pages. it is still one server though.

[Abdelrhman Fahmy]

he don't has a SSL certificate at all as i understand

[Span]

When using 2CO, and using a custom header and footer, those files may be on your server, but only spidered once by the 2CO robot to save them on their server.
IN those custom header and footer you need to put http:// links to the images on your domain:
<img src="http://www.domain.com/2co/image.jpg" alt="">

and they will look like this on an actual check out page:
<img src="https://sellers.2checkout.com/sellersfiles/XXXXX/domain/image.jpg" alt="">

Also, don't use xhtml in your template (images won't show because of the " /> slash), use embedded style and scripts.

[MultiMan]

Thanks for all the input.

1) Correct, we do NOT have a SSL certificate. So, "httpS:" on our own server for the header and footer include-files is not applicable.

2) When I right-click and select "Properties" on the images in the https-2CO pages, the URLs for the images are NOT on the 2CO server. They are called at our own server. (That is, they appear to NOT be spidered and cached into 2CO.)

So, it seems the include-files called from 2CO are called as similar to using the fopen() & fclose() command in PHP, opening a file from our server to include it in the file being dynamically created at 2CO. The consequence is that it calls the image-files and CSS-files from our NON-secure server.

[kjbrown]

I've used my template on 2CO with no problems. Make sure all links are full, not relational (meaning [....etc.)....] Sometimes you have to play around with it a few times to get 2CO to spider it correctly but it will work. Check out the store in my profile for an example. I can send you the code of my templates if you want. Just PM me.

<edit> I acutally just realized I'm logged into my friend's account so checkout the profile of JonR28 and PM him for that info </edit>

[MultiMan]

Non-sequitur.

I cannot understand your help here (even though I appreciate your making it!).

On a https: / / page at 2CO, how on earth can a
< IMG SRC = http: / / www.myowndomain... > file-call (for the image) --- which is to another domain (ours) --- suddently become "relative" enough to be considered as "in" the httpS page at 2CO? Technologically, it cannot. So, the result is calling an image file from an INSECURE site, in to the html page at 2CO which is a Secure page.

I admit, this suggestion is honestly making absolutely no sense to me. If you could clarify before I do any sticky business, I would appreciate it. Thanks.

[JonR28]

Okay. Sorry I'm not very understandable. What 2CO does is it takes your header and footer file and copies it as well as all of the images to its SSL enabled server.

ergo:
h**p://www.widgets.com/checkouttitle.gif
would turn into
h**ps://www.2checkout.com/whatever/checkouttitle.gif

They actually copy your header and footer and all graphics over to their server.

Now the tricky part is making sure that you don't use relavent URLS in your header, i.e. just "/files/image.jpg" instead of "h**p://www.widgets.com/files/image.jpg".

2CO has a lot of trouble caching web pages properly to its server so just be VERY careful with your coding.

Do not even bother with your own HTTPS address, leave yours as HTTP because it will get copied over anyway.

After you have done all this go back to the customizing page and make turn off the template mode, then turn it back on with the URL for your files. This will encourage 2CO to spider. Then be PATIENT, just wait about 30 minutes and it should all work out fine.

I hope you understood this post better.