Enforce JIRA not to run when base URL doesn't matches the actual URL.

[Tayyab Bashir]

Hi,
We have multiple test instances that are replice of our Production Servers.
We normally keep restoring test instances with latest XML backups from production server for testing purposes.

When an XML backup is restored, it brings in all the data from production including its URL in general configuration.
And often times developers forget to change the URL and start testing on it. 

So for example, if you open an open a new dashboard in new window with the middle button of mouse, it opens with the actual Production Server. 
And often times this could lead to making test changes on Production server.

Could anyone tell if there's a way to enforce JIRA not to run when Base URL doesn't matches the actual url? 
Lately, I've noticed that the warning also doesn't appear, telling you're accessing with incorrect URL. 
But even without the warning is there a way to enforce JIRA doesn't run with incorrect URL?

Many thanks,
Tayyab

[somethingblue]

Hi Tayyab,

Something like that would have to be done with a proxy.  There is a communities post that deals with a very similar topic for Confluence titled Redirection to another confluence base url that you can start with.

Here is some additional documentation for re-directing:

Apache: Redirecting and Remapping with mod_rewrite

Creating NGINX Rewrite Rules

IIS: Creating Rewrite Rules for the URL Rewrite Module

Cheers,

Branden