I am also proxying tomcat to Apache https to have a nice url without the port, so from 8080 to 80 ( 442). For me, the global setting worked for the proxy but I believe I could still go through tomcat (xxx:8080) prior to closing the port. Might be a workaround.
If you can't get around it, geoserver is all just XML, you can write a bash script to set the setting in your workspaces. Back up first 😂😂🤣. I little curious why you need this though. My servers are headless Linux so I can't test localhost unfortunately. Vera On Fri., Jun. 10, 2022, 1:58 a.m. Mattias Andrén via Geoserver-users, < geoserver-users@lists.sourceforge.net> wrote: > Thanks Graham, > > > > I will try this. > > > > I would prefer to have a global setting for this since I have 62 > workspaces which I really don’t want to enable local settings for. > > > > Is it possible to add a global setting to enable the old behavior > regarding this? > > > > Regards > > > > *Mattias Andrén * > > > > *Från:* Humphries, Graham <graham.humphr...@stategrowth.tas.gov.au> > *Skickat:* den 9 juni 2022 23:45 > *Till:* Mattias Andrén <mattias.and...@varberg.se>; > geoserver-users@lists.sourceforge.net > *Ämne:* RE: GeoServer 2.21 - Admin and Proxy Base Url > > > > Hi Mattias, > > > > > > FYI I have deployed Geoserver 2.21.0 into my test environment. This has a > similar setup to what you describe, except the reverse proxying is handled > by Apache HTTPD running on Unix. > > > > To stop the admin pages being redirected I removed the Global setting for > the Proxy base URL and have only applied it in the individual workspace > settings. > > > > Cheers, > > Graham > > > > *From:* Mattias Andrén via Geoserver-users < > geoserver-users@lists.sourceforge.net> > *Sent:* Thursday, 9 June 2022 10:54 PM > *To:* geoserver-users@lists.sourceforge.net > *Subject:* [Geoserver-users] GeoServer 2.21 - Admin and Proxy Base Url > > > > Hi, > > > > I’m trying to upgrade from Geoserver 2.18 to 2.21 on my test server. I > have been using this version on my dev server without issue. > > > > I’m using IIS URL Rewrite as a reverse proxy. As a consequence I have set > the Proxy Base URL in the Geoserver Global Settings to match. > > 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.0 with this configuration. > > > > If I have the Proxy Base URL set 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. > > In previous version (i.e 2.18) the Admin interface did not apply the Proxy > Base URL and you could use the Admin interface on the server using > http://localhost:8080/geoserver > > > > Is it possible to alter this behavior and revert it back to how it worked > before? > > > > Se also the question posted by Graham Humphries > > https://sourceforge.net/p/geoserver/mailman/message/37250476/ > <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fgeoserver%2Fmailman%2Fmessage%2F37250476%2F&data=05%7C01%7Cmattias.andren%40varberg.se%7Cff3ec1b59b1f49245ec408da4a614342%7C7f8b8c7bffd84804914cfac1638c3f65%7C0%7C0%7C637904078873728030%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ridXOTAydSyxd3dKeJ%2FUtk1BIeB6C%2FPYooC4BNuozcY%3D&reserved=0> > > > > > > Regards > > *Mattias Andrén* > > > > > ------------------------------ > > > 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: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
