JIRA and an aliased server/host

[Glenn Edwards]

I have an instance of JIRA 6.1.x running on Tomcat w/o Apache sitting in front and need to move the application to a new url.  To give the users a bit of time to get used to the new url it was decided that a redirect would be ebst for a few days.  So the canonical/host name and associated cert for the server changed/updated, but an alias to the old url was retained.  After modifying urlrewrite.xml to perform the redirect an error from the browser (Firefox in this case) is received:

"Firefox has detected that the server is redirecting the request for this address in a way that will never complete"

Several variations of the urlrewrite.xml were tried to no success, but this works w/o issue in a non-prod environment which isn't aliased.  Is it possible that alias on the host/server is the issue?  Is it possible to run JIRA on a server that has an alias?

[Daniel Wester]

It won't work... You'll want the baseUrl configured in JIRA to match with the publicly published dns entry. Things like the Add-on Manager, JIRA Agile etc won't work

Any reason why you can't do a redirect? That would make people get used to the new location.