-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configuration parameter web.application_root_url
neglected on some forwards (HTTP 302)
#367
Comments
Dear @jane-heller-bkg, Best regards, |
We have used the branch |
Dear @unaibrrgn, I stumbled upon another case where a URI generation is not done correctly. If I issue a clarification via Should I issue another ticket for that or should we summarize all issues w.rt. to URI generation here? Best Jane |
Dear @jane-heller-bkg, We suggest you to open a new ticket with the issue you are currently experiencing. Any additional information would be appreciated. Best regards, Irati. |
Hello @iratigarzon , I opened another issue w.r.t. here: #438 Best Jane |
The re3gistry webapplication does not seem to follow the
web.application_root_url
configuration value correctly all of the time.
My setup is as follows:
I have a frontend proxy delivering the application to say
http**s**://{HOSTNAME}/codelist
. The backend webserver is running a tomcat which is deploying:both to their according subfolders on local http.
re3gistry2/WEB-INF/classes/configurations_files/configuration.properties
contains:If I open the webservice and login, I receive a
HTTP 302
to the following destination:it should however contain
It seems to me, that the webapplication is costructing the path to be returned in a 302 on its own, by concatenating
http
the http host coming from the http connections variable and the folder on which the webapp is delivered locally.It should forward to URLs based on
web.application_root_url
in any case.The text was updated successfully, but these errors were encountered: