Issue Description
This article pertainwas created for 6.3 and 6.4, but see notes at bottom for a better approach in recent versions.
A customer using a reverse proxy noticed that after login, certain http requests from the browser are referencing the internal hostname rather than the external hostname
Using browser developer tools, you can watch the Network pane to see the full path of requests. If some are for the correct host, but others are not, test whether the problem only occurs when browsing thru the proxy rather than browsing directly against the appserver. If the problem only occurs thru the proxy an extra configuration might be required. Using the network pane, check the contents of the http request for http://<your host and port>/jasperserver-pro/rest_v2/hypermedia/root. If the contents contain references to the wrong host, review the resolution below
Resolution
backup then edit WEB-INFjs.config.properties, updating the deploy.base.url
The default file contains:
# Control links in hypermedia documents
# for example: deploy.base.url=http://bi.example.com
# right now works only for home page
# if empty then use request url
deploy.base.url=
This setting is described in the Admin guide, here: http://community.jaspersoft.com/documentation/tibco-jasperreports-server-community-project-administrator-guide/v640/configuration-0
NOTE:
In recent versions, deploy.base.url should be your last approach. A more complete approach is correcting the in-bound http headers from your proxy/loadbalancer, or tweaking the application Server's settings, like Tomcat's proxyHost, scheme, etc see:
And
Ref. Case 01537074
Recommended Comments
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now