12月 10, 2021

Forge Data Management API now enable compression for “application/vnd.api+json”

Follow @JohnOnSoftware

 

Previously, For Forge Data Management API, content type of “application/vnd.api+json” will not be enabled compression even if “Accept-Encoding: gzip” is set in the header of client side, and this makes the response payload very large for some Forge DM API.

Size comparation

 

To improve the performance, we enabled the compression for content type of “application/vnd.api+json”, now if “Accept-Encoding: gzip” is set in the header of client side, the response payload will be compressed, this change happened starting from 22th, Nov 2021. 

What does this change impact to your existing Forge Apps?
 
1.    If you are using Forge SDK, include NodeJS and .NET SDK, then no impact, all should be already taken care of already.
2.    But if you are calling Forge DM API directly, and set “Accept-Encoding: gzip” in the header, now you will get compressed response instead, please process the compressed content at your client side, or simply remove “Accept-Encoding: gzip” if you don’t want to handle the compressed content. 
 

If you still see any other issues or questions, please don't hesitate to contact us directly at forge.help@autodesk.com.

 

Posted by

Developer Advocate

Zhong Wu started his career in Autodesk since 2006 on AutoCAD Architecture as a software developer with more than 6 years working experience. After that, Zhong moved to Autodesk Development Network(now is renamed to Forge Partner Development) team as a Developer Advocate mainly focus on the API support/consultant for Maya/MotionBuilder, and started to contribute in Forge evangelism and support with the growing of...

Related Posts