Roll out of optimized CaaS filter responses beginning February 5th

Peter_Jodeleit
Crownpeak employee
Crownpeak employee
0 0 18

Starting on the 5th of February on DEV and QA environments we will roll out a change in our CaaS backend service.

Responses for collection requests currently include collection meta data if no format parameter is specified or the format=HAL is requested. This part of the response payload is usually not needed.

With the new version rolled out on 5th of February on CaaS DEV and QA environments requests containing a filter parameter the response will no longer include this meta data.

This change will be rolled out to the PROD environments five weeks later, on the 13th of March.

Additional hints:

  • for requesting only the collection meta request the document /_meta
  • for an even more streamlined response format the request parameters rep=s could be utilized
  • the new format is the same as if the parameter np (for “no properties”) has been included