You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Geonetwork then parses this JSON response to display a warning popup or to show the healthcheck results in the admin console (geonetwork/srv/eng/admin.console#/dashboard).
But with Gateway default config, the ApplicationError filter rewrites the HTTP Response to:
Explicitely removing the ApplicationFilter from the default-filters remove this issue:
default-filters:
- SecureHeaders
- TokenRelay
- RemoveSecurityHeaders# AddSecHeaders appends sec-* headers to proxied requests based on the currently authenticated user
- AddSecHeaders
- PreserveHostHeader# - ApplicationError
- LoginParamRedirect
but it seems a bit excessive. Is there any way to exclude the ApplicationError filter for some specific routes?
The text was updated successfully, but these errors were encountered:
I think 0beae05 was trying to fix this, but the healthcheck request has an Accept: application/json, text/plain, */* header, meaning the following test:
I'm not sure if this is the right place for this issue on an interaction between GeoNetwork and Gateway. Feel free to move it if pertinent.
GeoNetwork warning (and I assume critical) healthchecks return an HTTP response with code 500 and a JSON body, for instance:
Geonetwork then parses this JSON response to display a warning popup or to show the healthcheck results in the admin console (geonetwork/srv/eng/admin.console#/dashboard).
But with Gateway default config, the ApplicationError filter rewrites the HTTP Response to:
causing a Javascript error trying to parse
healthCheck[o.name]
and breaking the template from the status dashboard.Explicitely removing the ApplicationFilter from the default-filters remove this issue:
but it seems a bit excessive. Is there any way to exclude the ApplicationError filter for some specific routes?
The text was updated successfully, but these errors were encountered: