-
Notifications
You must be signed in to change notification settings - Fork 39
Description
With previous builds of the geoserver image, the geowebcache status page was accessible. Now it is blocked.
It seems to be intentional as the web.xml contains the following lines :
<security-constraint> <web-resource-collection> <web-resource-name>BlockGWC</web-resource-name> <url-pattern>/gwc/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>BLOCKED</role-name> </auth-constraint> </security-constraint> <security-constraint> <web-resource-collection> <web-resource-name>AllowGWC_Demo</web-resource-name> <url-pattern>/gwc/demo/*</url-pattern> </web-resource-collection> </security-constraint> <security-constraint> <web-resource-collection> <web-resource-name>AllowGWC_Services</web-resource-name> <url-pattern>/gwc/service/*</url-pattern> </web-resource-collection> </security-constraint> <security-constraint> <web-resource-collection> <web-resource-name>AllowGWC_Rest</web-resource-name> <url-pattern>/gwc/rest/*</url-pattern> </web-resource-collection> </security-constraint>
Is there a reason ?
And how is the geoserver.war artefact built ( I have not changed the version that I am using : 24.4.4, so it seems that there is a build reproductibility problem as well ) ?