So a bit more info. This problem seems to occur at any point if the
tomcat Connector definition includes proxyName and proxyPort definitions
(even if they just point to localhost:x). Even if you access the
instance directly (not via proxy), and the proxy settings point to it
directly it happens. The issue shows up on all the 'Data' screens I
have tried.
Problems also occur is you try to save settings, which show an error like
*---------
*
*Type* Status Report
*Message* Origin does not correspond to request
*Description* The server cannot or will not process the request due to
something that is perceived to be a client error (e.g., malformed
request syntax, invalid request message framing, or deceptive request
routing).
---------
There are no relevant messages showing up in the tomcat or geoserver
logs at production logging level. If I turn on verbose logging I get
the following
2020-05-14 11:41:01,480 DEBUG
[security.IncludeQueryStringAntPathRequestMatcher] - Checking match of
request : 'Path:
/web/wicket/bookmarkable/org.geoserver.web.data.layer.layerpage,
QueryString:
16-2.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll&filter=false';
against '/web/**'
2020-05-14 11:41:01,480 DEBUG
[security.IncludeQueryStringAntPathRequestMatcher] - Matched Path:
/web/wicket/bookmarkable/org.geoserver.web.data.layer.layerpage,
QueryString:
16-2.IBehaviorListener.0-table-listContainer-selectAllContainer-selectAll&filter=false
with /web/**
2020-05-14 11:41:01,480 DEBUG [geoserver.ows] - Could not find a layer
group named web
2020-05-14 11:41:01,480 DEBUG [geoserver.ows] - Could not find a layer
group named web
2020-05-14 11:41:01,496 DEBUG [geoserver.ows] - Could not find a layer
group named web
2020-05-14 11:41:01,496 DEBUG [geoserver.ows] - Could not find a layer
group named web
2020-05-14 11:41:01,636 DEBUG [org.geoserver] - Thread 89 locking in
mode READ
On 5/14/2020 11:52 AM, Tom S wrote:
Glad to see this is reproducible (on a non-Windows platform even).
I'm still trying to track it down, but for me this seems to be related
to using a Apache HTTPD (latest version) proxy as a front end. From
that programs access logs I see
_______________________________________________
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
