IntegrationsTopic number: 1676264800514

Key	Summary
	Custom-made interfaces/applications using Enterprise Imaging web services do not function as expected Description: Beginning in Enterprise Imaging 8.2.0.000, the HTTP transfer encoding that is used as part of the Enterprise Imaging web services, has been changed from data-length transfer encoding to chunked transfer encoding to improve web performance. This change may have a negative impact on custom-made interfaces developed using Enterprise Imaging web services. Though chunked transfer encoding was officially introduced in HTTP 1.1 (1997) and the specification was most recently updated in 2014, web services are not always developed to support both transfer encoding. It is highly recommended to test the compatibility with Enterprise Imaging 8.2.0.000 in a test environment prior to updating the production cluster. Workaround: None. Interfaces/applications that do not support chunked transfer encoding must be updated to support it.

Key

Summary

Custom-made interfaces/applications using Enterprise Imaging web services do not function as expected

Description:

Beginning in Enterprise Imaging 8.2.0.000, the HTTP transfer encoding that is used as part of the Enterprise Imaging web services, has been changed from data-length transfer encoding to chunked transfer encoding to improve web performance. This change may have a negative impact on custom-made interfaces developed using Enterprise Imaging web services.

Though chunked transfer encoding was officially introduced in HTTP 1.1 (1997) and the specification was most recently updated in 2014, web services are not always developed to support both transfer encoding.

It is highly recommended to test the compatibility with Enterprise Imaging 8.2.0.000 in a test environment prior to updating the production cluster.

Workaround: None. Interfaces/applications that do not support chunked transfer encoding must be updated to support it.