ETag Change in WMS Acquisitions API

An upcoming change included in the November 9th WMS release

We wanted to provide you with some more information about the ETag change in the WMS Acquisitions API we posted about for the November 9th release.
We removed the ETag Filter (configuration) from this API to address a performance problem. This will have the greatest impact in searches as they usually return a lot of data. Because we’re removing ETags from the search response, we anticipate you’ll see improved performance.
When you’re working with a single object in GET/UPDATE requests, ETags are still supported and the ETag validation itself is not changed.
Read methods will no longer return the code 304 „Not Changed“ and will instead always return data and 200, even if the data has not changed.

Please let us know if you have any questions.