I’m kind of in a jam and I hope someone knows this answer.
One of my customers has an existing website that is basic and w/o a store. (Store as in the kind they sell products through) For a few months we have been building a new site for them which includes a store. The store on the new site works well and has SSL on it and everything is *happy*. Here is the problem. Certain parts of the new website are not ready to go live(through no fault of ours) but the customer is having an event where they really need the store to be able to sell their products this weekend. They were under the impression that since the store works, it can just be used by the old site as a module. To further complicate this, the new site is on a totally separate server from the old site. The new site has an SSL cert installed on it for the store but it is registered under the url of the old site. The idea was to just change the DNS record when the site is done and then all would be well. If you try and access the store by IP you, of course, get all sorts of certificate messages. Does anyone know who I can link the store, that resides in the new site, to work in the old site even though they are not on the same machine and not get certificate errors? Is there a way I could make something like a virtual directory in the old site that points to the store on the new site? For example:
This is the current site:
www.thesite.com
This is where the store resides(Can only be accessed by IP):
XXX.XXX.XXX.XXX/store.asp
What I want to do is have it like this:
www.thesite.com/store.asp
but store is not on the server and I can’t have it complain about the certificate or else the customers won’t trust the site which means they won’t buy from it. Any ideas? I’ve not come across a situation like this but I’m in desperate need of this kind of functionality. Both the store and old site are on machines running Windows 2003 with IIS6 using ASP.
PLEASE HELP, I’M GOING INSANE OVER THIS!
Thank you for anything anyone can tell me… even if it’s bad news.