• Sales: 1-800-961-2888
  • Support: 1-800-961-4454

Using a staging URL


NOTE: This article is written for our Classic Cloud Control Panel. You can access this interface from the New Cloud Control Panel by clicking your username in the upper-right of the control panel and selecting "Classic Cloud Control Panel".

  • Administrative access to the Rackspace Cloud

Procedure

  • Navigate to Hosting->Cloud Sites, from the list of domains click on the hyperlink of the domain and select General Settings tab
  • Scroll down to the Viewing and Editing section and check the Testing URL link, this identifies the technology, cluster and data center used for this website.
staging.jpg
  • All content and code uploaded to the site can now be accessed with the test or staging url
  • The website can be made public when needed. Site owner must log into the website for the domain reistrar where they bought the domain--for e.g. Godaddy.com or Register,com, and set the DNS name servers for the domain dns1.stabletransit.com and dns2.stabletransit.com. Additionally you can use external name servers and modify DNS records as needed.

Additional Resources



© 2011-2013 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License


See license specifics and DISCLAIMER

4 Comments

How can you turn off or disable the test URL?

I don't think there's a way to turn it off via our control panel, but you could set up a rewrite rule via htacess that could detect the use of the test URL and redirect all requests to a catchall page.

If you add a SSL to a cloud site, will any page that uses the test URL with a https connection come back as a bad SSL cert or just server not available? Other pages that are http seem to still work. Is there any way to get around this before making a site live?

I expect that you would get a "bad certificate" warning, but should be able to continue to the site anyway.

The reason for this is the way certificates are set up. The browser checks the domain against the certificate first. When the domain doesn't match (because it's a test domain) the browser thinks something might be wrong and warns you accordingly. That doesn't mean there would be a problem on the live site - just that the test URL's domain doesn't match the domain in the certificate.

Add new comment