I upgraded Geoserver on my test server to version 2.19.0. I have been using this version on my dev server without issue.
The difference between the dev and test servers is the test has a reverse proxy set to allow external access to the layers. As a consequence I have set the Proxy Base URL in the Geoserver Global Settings to match. The Proxy Base URL is also set on the Edit Workspace page. This has been working without issue in previous versions and the Admin interface uses the local URL. My production server is running version 2.18.1 with this configuration.
If I have the Proxy Base URL set in both places in my test instance the Admin interface applies the Proxy Base URL (from the Global Settings page) to all the pages in the Admin interface. The consequence for me is that when a request to Geoserver goes through the reverse proxy an authorization header is added. This means that I am no longer logged in as an administrator.
If I remove the Proxy Base URL from the Global Settings page Geoserver works normally.
While this does not seem to be a major problem, the behaviour is different to previous versions.
You are the first person to bring this up - I was not aware of any expected change here - and do not see anything in the release notes (2.19.0 | 2.19-RC ).
I would ask you to try updating step by step, 2.18.1 → 2.18.2 → 2.18.3 → 2.19.0 to see if we can catch when this regression was introduced.
We did take some effort to centralize the http configuration for cascaded services (like republishing WFS, WMS or WMTS) but that should not affect the user interface.
I have stepped through several versions from 2.18.1 → 2.18.2 → 2.18.X(Nightly build) → 2.19.0
The problem only occurs for both 2.19.0 and 2.19.RC.
Cheers,
Graham
···
Graham:
You are the first person to bring this up - I was not aware of any expected change here - and do not see anything in the release notes (2.19.0 | 2.19-RC ).
I would ask you to try updating step by step, 2.18.1 → 2.18.2 → 2.18.3 → 2.19.0 to see if we can catch when this regression was introduced.
We did take some effort to centralize the http configuration for cascaded services (like republishing WFS, WMS or WMTS) but that should not affect the user interface.
I upgraded Geoserver on my test server to version 2.19.0. I have been using this version on my dev server without issue.
The difference between the dev and test servers is the test has a reverse proxy set to allow external access to the layers. As a consequence I have set the Proxy Base URL in the Geoserver Global Settings to match. The Proxy Base URL is also set on the Edit Workspace page. This has been working without issue in previous versions and the Admin interface uses the local URL. My production server is running version 2.18.1 with this configuration.
If I have the Proxy Base URL set in both places in my test instance the Admin interface applies the Proxy Base URL (from the Global Settings page) to all the pages in the Admin interface. The consequence for me is that when a request to Geoserver goes through the reverse proxy an authorization header is added. This means that I am no longer logged in as an administrator.
If I remove the Proxy Base URL from the Global Settings page Geoserver works normally.
While this does not seem to be a major problem, the behaviour is different to previous versions.
Is this the expected behaviour?
Regards,
Graham Humphries
CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list: