[Geoserver-users] What cause PROXY_BASE_URL to be unset?

I have verbose logging on geoserver whilst configuring it to get it in shape for production.
There are logging messages i don’t understand and if i should be worried about them.

I get a lot Found Java environment variable: ‘xx’ to be unset. In particular for PROXY_BASE_URL but also found for several other.
But in my docker-compose (see snipper bellow) it is defined and appear to be working. Is something broken? I cannot tell by the logg.

image.png

services:
geoserver:
image: docker.osgeo.org/geoserver:2.25.0


environment:

I noticed that EXTRA_GEOSERVER_OPTS="-DGEOSERVER_CSRF_WHITELIST is not working. mydomain are still not going through. The only reason it works at the moment is because I disabled CSRF altogether. Is there a reason why Whitelist would not work. I have tried adding just one domain as well. If CSRF is enabled i get a 400 error.

Hello Kristian,

GEOSERVER_PROXY_BASE is in the user manual; it is an optional application property that can be defined as environmental variable, system property, or web context parameter (or using the user interface…). The value is used a lot, and TRACE is telling you about checking all the locations it …

TRACE happily tells you about the correct functioning of the application in painful detail. So nothing is wrong and it wants to tell you about it.

I recently added a list of some of the environmental variables here: https://docs.geoserver.org/latest/en/user/configuration/properties/index.html

If you spot any I missed please make an update to the documentation.

···


Jody Garnett