Local URLs in your static pages and fwx scripts should never be fully qualified with IP addresses or server names. This ensures that you do not have to modify your pages whenever you move to a different host name/IP address.
Are you using fully qualified URLs because you want to switch from HTTP to HTTPS? If yes, I recommend that you dynamically construct a self-referencing URL. The following code should prove useful:
Another alternative would be to modify your hosts file so as to redirect your hosted site's host name/IP address to your local server. The problem with this is that this will prevent you from accessing your hosted site from that computer.
Sent by Joe Goldsmith on 07/14/2006 11:21:08 PM:
I have an application that I am just about ready to pack on a new 1U rack mount computer and take to a co-location service. As such, I will need to change IP addresses.
The problem is once I send the website to a co-location service how do I not work on the website?
Certainly, I can load the website on my local workstation or server but the co-located code has embedded local URLs with HTTS and other stuff that I cannot test locally as it will want to go over the Internet to the co-located server.
Any one have an idea how to maintain, upgrade, and test the website locally?