I've an interior application (Jira) that i wish to use inwardly and outwardly, now there can be one other way to do this by which situation i am available to it, but this is exactly what i've to date:

URL one: https://domainname.com/jira  - external domain name for it
URL two: https://domainname.local/jira - internal network name for it.

I'm running Apache like a reverse proxy and that i have this:

<Location /jira>
    ProxyPass http://127.0.0.1:8080/jira
    ProxyPassReverse http://127.0.0.1:8080/jira
</Location>

Jira produces all its links utilizing a base url, which within this situation is placed to 'https://domainname.local/jira', so clearly when pages get offered towards the outdoors world they've .local in it.

Now you ask ,, it is possible to way to achieve the content rewritten because it is offered to be able to alter the .local addresses inside the HTML to become the .com ones?

Or shall we be held as being a retard and there's an simpler method to solve this?

Cheers for just about any help....

Andy

How about provide a unique Hyperlink to JIRA? Your customers may love this!

We make use of this with CNames, Apache's VirtualHosts, mod_jk to jira stand alone edition and reverse proxies.

HIH!

My jira operates on local:84 which is the setup to gain access to it as being jira.yourdomain.com:

#Jira
<VirtualHost *:80>
ServerName jira.yourdomain.com
ServerAlias jira.yourdomain.com

#jirafast?
ExpiresActive On
ExpiresDefault "access plus 300 seconds"
    ExpiresByType text/html "access plus 1 day"
    ExpiresByType text/css "access plus 1 day"
    ExpiresByType text/javascript "access plus 1 day"
    ExpiresByType image/gif "access plus 1 month"
    ExpiresByType image/jpg "access plus 1 month"
    ExpiresByType image/png "access plus 1 month"
#jirafast? -


ProxyPreserveHost On
ProxyPass / http://localhost:84/
ProxyPassReverse / http://localhost:84/
<Proxy http://localhost:84/>
#  Order Allow,Deny
#  Allow from all
   Order Deny,Allow
   Allow from 127.0.0.1
</Proxy>
</VirtualHost>

If it's sub-optimal, you shouldn't be suprised, all I understand is it works

Jira will build Web addresses in line with the URL accustomed to access the server. Inside your situation mod_proxy is applying the proxy Hyperlink to connect.

You have both domain names proxying right through to the neighborhood machine, which appears unnecessary considering that exactly the same web server is serving both domain names. If you're able to, I'd eliminate the Apache middle-guy and configure both domain names to suggest straight to Jira.

With that said though, should you include ProxyPreserveHost On inside your config, it'll persist the hostname right through to the server.