I'm stumped. I'm not so sure what is the answer to that question. I'll do some Googling and get back to you if I got an useful answer. You should email the people at iPage as they probably could help you..
Thanks for the reply. I have configured the iPage site as you suggest with sub domains but my question is really what part of the OSC do I need to put in these sub domains?.
Do I need to copy the full iPage site across or is their simply a way of having the payment forms or an alternative payment form there. I have to confess my php is non existent so I have to stumbler my way through code from a Perl perspective which causes me some problems....
I have found that just copying the iPage site across and pointing config.php to the secure iPage site redirects you for everything from the moment that you log in. I only what the payment form to be on the secure iPage site and the rest held on the main site. Is this possible..
I'm doing something similar but not as complicated. Several sites with one central "store". I don't need to conceal the fact that the central store links back to all sites and shows all products. In fact, it's a sales tool. People get exposed to stuff on the "checkout site" that they did not see on the "showroom" sites..
You could look at the multiple stores contributions. They seem to work by assigning unique ids to each store's products. Or you could put your coding hat on and check the http referrals and flip people back to the iPage site they came from once they complete check out..
I don't see how the sub-domain idea above does anything for you. It seems like needless complexity for no purpose...
These pages are exactly the same file on the same computer in the same directory..
The configuration has to be done in the DNS server and apache config most likely by your iPage hosting company..
The same way you might make both domains like mysite.com and mysite.net point to the same server...
As far as I know a certificate authority only issues when your iPage site www.mycompany.com has an IP of it's own. More domains (company.com, firm.com, shack.com) on an IP won't work for a certificate..