Mercurial > hg > orthanc
diff NEWS @ 5635:0e16e677fe64
fixed broken /instances/../tags after reconstructing studies when IngestTranscoding has changed
author | Alain Mazy <am@orthanc.team> |
---|---|
date | Tue, 21 May 2024 17:09:57 +0200 |
parents | 5db4ed395d81 |
children | b6a6179a2a69 |
line wrap: on
line diff
--- a/NEWS Tue May 21 12:28:21 2024 +0200 +++ b/NEWS Tue May 21 17:09:57 2024 +0200 @@ -11,14 +11,19 @@ in case you just want to update the MainDicomTags of that resource level only e.g. after you have updated the 'ExtraMainDicomTags' for this level. * The "requestedTags" GET argument was deprecated in favor of "requested-tags". +* Fixed broken /instances/../tags route after the calling + /studies/../reconstruct when changing the "IngestTranscoding". Plugins ------- * Multitenant DICOM plugin: added support for locales -* Housekeeper plugin: Added an option "LimitMainDicomTagsReconstructLevel" - (allowed values: "Patient", "Study", "Series", "Instance"). This can greatly speed - up the housekeeper process e.g. if you have only update the Study level ExtraMainDicomTags. +* Housekeeper plugin: + - Added an option "LimitMainDicomTagsReconstructLevel" + (allowed values: "Patient", "Study", "Series", "Instance"). This can greatly speed + up the housekeeper process e.g. if you have only update the Study level ExtraMainDicomTags. + - Fixed broken /instances/../tags route after running the Housekeeper + after having changed the "IngestTranscoding". * SDK: added OrthancPluginLogMessage() that is a new primitive for plugins to log messages. This new primitive will display the plugin name, the plugin file name, and the plugin line number in the @@ -43,13 +48,13 @@ * Monitoring of stable resources now also takes into consideration the resource type, not only the resource identifier identifier. * DICOM TLS: - * In prior versions, when "DicomTlsRemoteCertificateRequired" was set to false, Orthanc + - In prior versions, when "DicomTlsRemoteCertificateRequired" was set to false, Orthanc was still sending a client certificate request during the TLS handshake but was not triggering and error if the client certificate was not trusted (equivalent to the --verify-peer-cert DCMTK option) From this version, if this option is set to false, Orthanc will not send a client certificate request during the TLS handshake anymore (equivalent to the --ignore-peer-cert DCMTK option). - * When working with "DicomTlsEnabled": true and "DicomTlsRemoteCertificateRequired": false, + - When working with "DicomTlsEnabled": true and "DicomTlsRemoteCertificateRequired": false, Orthanc was refusing to start if no "DicomTlsTrustedCertificates" was provided. * Upgraded dependencies for static builds: - boost 1.85.0