Message 351 - Orthanc issue tracker

Author	admin
Recipients
Date	2017-12-13.10:22:22

Content
[BitBucket user: Alain Mazy] [BitBucket date: 2017-12-13.09:22:22] any http error leads to the same error message: ``` E1207 14:13:26.928478 22906 StorePeerCommand.cpp:76] Unable to send resource xxx to peer "https://xxx.xxx.xxx/" E1207 14:13:26.935878 22906 StorePeerCommand.cpp:85] Unable to forward to an Orthanc peer in a Lua script (instance xxx, peer https://xxx.xxx.xxx/): Error in the network protocol ``` We can not differentiate the error. -> We should at least log the curl error code. If possible, instead of receiving an 'empty' 400 status code, that would be nice if the curl error code as also included in the HTTP response returned by Orthanc so it can be used by the client making the request.

[BitBucket user: Alain Mazy]
[BitBucket date: 2017-12-13.09:22:22]

any http error leads to the same error message:
```
E1207 14:13:26.928478 22906 StorePeerCommand.cpp:76] Unable to send resource xxx to peer "https://xxx.xxx.xxx/"
E1207 14:13:26.935878 22906 StorePeerCommand.cpp:85] Unable to forward to an Orthanc peer in a Lua script (instance xxx, peer https://xxx.xxx.xxx/): Error in the network protocol
```

We can not differentiate the error.  -> We should at least log the curl error code.  If possible, instead of receiving an 'empty' 400 status code, that would be nice if the curl error code as also included in the HTTP response returned by Orthanc so it can be used by the client making the request.

History
Date	User	Action	Args
2026-07-29 15:51:21	admin	link	issue78 messages
2026-07-29 15:51:21	admin	create