Issue34

Title Orthanc shall return error details in the body of the HTTP 500 response
Priority wish Status resolved
Superseder Nosy List admin
Assigned To
Keywords Orthanc Core

Created on 2017-03-09.11:27:14 by admin, last changed by admin.

Messages
msg154 (view) Author: admin Date: 2017-03-09.11:27:14
[BitBucket user: Alain Mazy]
[BitBucket date: 2017-03-09.10:27:14]

When sending a study to a PACS, the transfer failed because one of the series was not supported by the PACS.  All we get from the API is a 500 response.
That would be nice to get the error details in the response.  Right now, the only way to get the error details is to look in the logs:
```
StoreScuCommand.cpp:78] Unable to forward to a modality in a Lua script (instance 2eaaae63-8eb016da-7c34fa6c-ed427b0b-6c213be3): DicomUserConnection: No acceptable presentation context for modality
ServerScheduler.cpp:122] Job has failed (HTTP request: Store-SCU to peer "destinationPacs")
```
msg155 (view) Author: admin Date: 2017-03-09.12:10:53
[BitBucket user: Alain Mazy]
[BitBucket date: 2017-03-09.11:10:53]

Note that, the right approach is probably to retrieve jobs id when issuing transfers and then poll the jobs status through a new API route.
msg156 (view) Author: admin Date: 2019-01-25.14:13:03
[BitBucket user: Sébastien Jodogne]
[BitBucket date: 2019-01-25.13:13:03]

Unable to reproduce.
History
Date User Action Args
2026-07-29 15:51:19admincreate