can this be solved using ASP?
in [ASP]
|
From: c676228 on 17 Mar 2008 00:35 Hi All, Our company is merging two production domains(from two different servers) onto one server. So during the migration we use an intranet testing server to hold all files from these two domain, when we do testing, we use host file to map intranet IPs to these two domains. It will not impact on production sites since it won't be seen externally. These two domains navigable each other, that means from domainA we have links to domainB, while from domainB, we have links to domainA. These domain names are all hard coded in the program. Now it seems a big problem. When we move all these file to a new production server which is at a public hosting company, we need to do testing, at this moment, old production servers are still running and we have to use IPs to do testing, cannot map IPs to domain names at all. That means all hard-coded links from domainA to domainB will not work, and I have to change all the links from domain name to IP? Then when we finally go live with our new production server, I have switch back to domain name, what a mess? I didn't think through all those steps when we did it. Anybody has better solution? Thank you so much -- Betty
From: Adrienne Boswell on 17 Mar 2008 10:55 Gazing into my crystal ball I observed =?Utf-8?B?YzY3NjIyOA==?= <betty(a)newsgroup.nospam> writing in news:732B66ED-FE25-4E05-A003-1E0B9AE03475(a)microsoft.com: > Hi All, > > Our company is merging two production domains(from two different > servers) onto one server. So during the migration we use an intranet > testing server to hold all files from these two domain, when we do > testing, we use host file to map intranet IPs to these two domains. It > will not impact on production sites since it won't be seen > externally. These two domains navigable each other, that means from > domainA we have links to domainB, while from domainB, we have links to > domainA. These domain names are all hard coded in the program. > Now it seems a big problem. When we move all these file to a new > production server which is at a public hosting company, we need to do > testing, at this moment, > old production servers are still running and we have to use IPs to do > testing, cannot map IPs to domain names at all. That means all > hard-coded links from domainA to domainB will not work, and I have to > change all the links from domain name to IP? > Then when we finally go live with our new production server, I have > switch back to > domain name, what a mess? I didn't think through all those steps when > we did it. > Anybody has better solution? > Thank you so much > > If they are hard coded absolute paths, you should be able to do a global search and replace, eg. replace http://www.example.com/somepage.asp with http://www.example.net/somepage.asp just replace all example.com with example.net. -- Adrienne Boswell at Home Arbpen Web Site Design Services http://www.cavalcade-of-coding.info Please respond to the group so others can share
From: "Steven Cheng" on 18 Mar 2008 01:51 Hi Betty, How many pages or links will you need to replace here? I'm afraid for such scenario, there hasn't any quick & simple means to do a replace or redirection. Also, since the problem only occurs during the time your pages are deployed on external server and want to test from internal, I think adding additional code logic to do redirection is also not quite reasonable. I will still suggest manually replace those link's servername. Steven Cheng Microsoft MSDN Online Support Lead Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg(a)microsoft.com. This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- >From: =?Utf-8?B?YzY3NjIyOA==?= <betty(a)newsgroup.nospam> >Subject: can this be solved using ASP? >Date: Sun, 16 Mar 2008 21:35:01 -0700 > >Hi All, > >Our company is merging two production domains(from two different servers) >onto one server. So during the migration we use an intranet testing server to >hold all files from these two domain, when we do testing, we use host file to >map intranet IPs to these two domains. It will not impact on production >sites since it won't be seen externally. These two domains navigable each >other, that means from domainA we have links to domainB, while from domainB, >we have links to domainA. >These domain names are all hard coded in the program. >Now it seems a big problem. When we move all these file to a new production >server which is at a public hosting company, we need to do testing, at this >moment, >old production servers are still running and we have to use IPs to do >testing, cannot map IPs to domain names at all. That means all hard-coded >links from domainA to domainB will not work, and I have to change all the >links from domain name to IP? >Then when we finally go live with our new production server, I have switch >back to >domain name, what a mess? I didn't think through all those steps when we did >it. >Anybody has better solution? >Thank you so much > > >-- >Betty >
From: c676228 on 20 Mar 2008 19:07 Hi Steven, I am thinking I will still use host file to map our domain name to our new production server for testing. That way I don't need to write any code or replace any code. But I am not sure if it is OK or if it will confuse google search engine or some DNS Servers since our DNS server will still point our domain name to our current(old) production server (old IP address). I am just wondering if the real world will see our domain name has two IPs since our new production server is located at public hosting company too. Or the question is if you use another IP to map to a domain name in production for the purpose of testing, will it hurt our current production site? Hopefully -- Betty ""Steven Cheng"" wrote: > Hi Betty, > > How many pages or links will you need to replace here? I'm afraid for such > scenario, there hasn't any quick & simple means to do a replace or > redirection. Also, since the problem only occurs during the time your pages > are deployed on external server and want to test from internal, I think > adding additional code logic to do redirection is also not quite > reasonable. I will still suggest manually replace those link's servername. > > Steven Cheng > Microsoft MSDN Online Support Lead > > Delighting our customers is our #1 priority. We welcome your comments and > suggestions about how we can improve the support we provide to you. Please > feel free to let my manager know what you think of the level of service > provided. You can send feedback directly to my manager at: > msdnmg(a)microsoft.com. > > This posting is provided "AS IS" with no warranties, and confers no rights. > > -------------------- > > >From: =?Utf-8?B?YzY3NjIyOA==?= <betty(a)newsgroup.nospam> > >Subject: can this be solved using ASP? > >Date: Sun, 16 Mar 2008 21:35:01 -0700 > > > > >Hi All, > > > >Our company is merging two production domains(from two different servers) > >onto one server. So during the migration we use an intranet testing server > to > >hold all files from these two domain, when we do testing, we use host file > to > >map intranet IPs to these two domains. It will not impact on production > >sites since it won't be seen externally. These two domains navigable each > >other, that means from domainA we have links to domainB, while from > domainB, > >we have links to domainA. > >These domain names are all hard coded in the program. > >Now it seems a big problem. When we move all these file to a new > production > >server which is at a public hosting company, we need to do testing, at > this > >moment, > >old production servers are still running and we have to use IPs to do > >testing, cannot map IPs to domain names at all. That means all hard-coded > >links from domainA to domainB will not work, and I have to change all the > >links from domain name to IP? > >Then when we finally go live with our new production server, I have switch > >back to > >domain name, what a mess? I didn't think through all those steps when we > did > >it. > >Anybody has better solution? > >Thank you so much > > > > > >-- > >Betty > > > >
From: "Steven Cheng" on 21 Mar 2008 01:44 Hi Betty, I think host file solution should work for your own internal network since you can control the host files for your internal client machines or the local DNS server. However, for external network and environment, when they visit the ASP pages and visit the link, they'll get the actual IP through internet DNS server, I think it will exsit some difference between your internal clients. Do you think so? Sincerely, Steven Cheng Microsoft MSDN Online Support Lead Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg(a)microsoft.com. This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- >Thread-Topic: can this be solved using ASP? >thread-index: AciK3xsa1beYvTorSAy5drl5zfgYPg== >X-WBNR-Posting-Host: 63.241.246.249 >From: =?Utf-8?B?YzY3NjIyOA==?= <betty(a)newsgroup.nospam> >References: <732B66ED-FE25-4E05-A003-1E0B9AE03475(a)microsoft.com> <2mgmewLiIHA.4672(a)TK2MSFTNGHUB02.phx.gbl> >Subject: RE: can this be solved using ASP? >Date: Thu, 20 Mar 2008 16:07:01 -0700 > >Hi Steven, > >I am thinking I will still use host file to map our domain name to our new >production server for testing. That way I don't need to write any code or >replace any code. But I am not sure if it is OK or if it will confuse >search engine or some DNS Servers since our DNS server will still point our >domain name to our current(old) production server (old IP address). > >I am just wondering if the real world will see our domain name has two IPs >since our new production server is located at public hosting company too. > >Or the question is if you use another IP to map to a domain name in >production for the purpose of testing, will it hurt our current production >site? > >Hopefully >-- >Betty > > >""Steven Cheng"" wrote: > >> Hi Betty, >> >> How many pages or links will you need to replace here? I'm afraid for such >> scenario, there hasn't any quick & simple means to do a replace or >> redirection. Also, since the problem only occurs during the time your pages >> are deployed on external server and want to test from internal, I think >> adding additional code logic to do redirection is also not quite >> reasonable. I will still suggest manually replace those link's servername. >> >> Steven Cheng >> Microsoft MSDN Online Support Lead >> >> Delighting our customers is our #1 priority. We welcome your comments and >> suggestions about how we can improve the support we provide to you. Please >> feel free to let my manager know what you think of the level of service >> provided. You can send feedback directly to my manager at: >> msdnmg(a)microsoft.com. >> >> This posting is provided "AS IS" with no warranties, and confers no rights. >> >> -------------------- >> >> >From: =?Utf-8?B?YzY3NjIyOA==?= <betty(a)newsgroup.nospam> >> >Subject: can this be solved using ASP? >> >Date: Sun, 16 Mar 2008 21:35:01 -0700 >> >> > >> >Hi All, >> > >> >Our company is merging two production domains(from two different servers) >> >onto one server. So during the migration we use an intranet testing server >> to >> >hold all files from these two domain, when we do testing, we use host file >> to >> >map intranet IPs to these two domains. It will not impact on production >> >sites since it won't be seen externally. These two domains navigable each >> >other, that means from domainA we have links to domainB, while from >> domainB, >> >we have links to domainA. >> >These domain names are all hard coded in the program. >> >Now it seems a big problem. When we move all these file to a new >> production >> >server which is at a public hosting company, we need to do testing, at >> this >> >moment, >> >old production servers are still running and we have to use IPs to do >> >testing, cannot map IPs to domain names at all. That means all hard-coded >> >links from domainA to domainB will not work, and I have to change all the >> >links from domain name to IP? >> >Then when we finally go live with our new production server, I have switch >> >back to >> >domain name, what a mess? I didn't think through all those steps when we >> did >> >it. >> >Anybody has better solution? >> >Thank you so much >> > >> > >> >-- >> >Betty >> > >> >> >
|
Next
|
Last
Pages: 1 2 Prev: some users cannot open asp page or see some images on the intr Next: Trading Forex |