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
Calls to publish_featuretype result in 404 exceptions in the REST API; code review suggests GETs are triggered by the serialization of the post data payload --> data=feature_type.message() ... to populate the various FeatureType attributes marked as an xml_property.
org.geoserver.rest.ResourceNotFoundException 404 NOT_FOUND: No such feature type ...
The publish call is successful & the feature type gets created OK (200 for the resulting POST) but the 404 exceptions are untidy in the server logs.
Is it possible to suppress these either thru creation of some other resource in advance, or by somehow setting the quietOnNotFound parameter exposed by the REST interface?
The text was updated successfully, but these errors were encountered:
Calls to publish_featuretype result in 404 exceptions in the REST API; code review suggests GETs are triggered by the serialization of the post data payload --> data=feature_type.message() ... to populate the various FeatureType attributes marked as an xml_property.
org.geoserver.rest.ResourceNotFoundException 404 NOT_FOUND: No such feature type ...
The publish call is successful & the feature type gets created OK (200 for the resulting POST) but the 404 exceptions are untidy in the server logs.
Is it possible to suppress these either thru creation of some other resource in advance, or by somehow setting the quietOnNotFound parameter exposed by the REST interface?
The text was updated successfully, but these errors were encountered: