On Fri, May 30, 2014 at 11:55:32AM -0400, bwellsnc wrote: Hi there,
> This is the issue. I am using a fortigate device to protect my network and > I want to use the https connection in the web portal to access my Jira > instance. The problem is that jira always expects a > https://jira.internal.example.com, because that is what is set in it's base > url. The fortigate sends this to nginx: > > https://vpn.example.com/proxy/https/jira.internal.example.com/secure/Dashboard.jspa According to the proxy_pass documentation, location ^~ /proxy/https/jira.internal.example.com/ { proxy_pass https://[jira hostname or ip]/; proxy_set_header Host jira.internal.example.com; } should do what you seem to be asking for. (Replace [this bit].) But I'm not aware of any proxy/firewall devices that do what you say your fortigate is doing. So it may not end up doing what you actually want. f -- Francis Daly [email protected] _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
