Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Response `Content-Type` header should include `transfer-syntax`

See original GitHub issue

Currently, the transfer syntax is missing from the response Content-Type header. If multiple Accept headers are supplied, without transfer syntax in the response Content-Type, the caller wouldn’t know which transfer syntax was used. More detail can be found here: http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_8.7.9.

We’ll need to add the transfer syntax to the RetrieveResourceResponse being returned in the core layer.

To Reproduce Steps to reproduce the behavior:

Store an image following these instructions
Retrieve the image
Inspect the Content-Type header of the response

Expected behavior The header should include a portion that reads transfer-syntax={value} where {value} is either a valid Transfer Syntax UID or the token *. This value should match the Accept header in the request.

Actual behavior This portion is not included.

Issue Analytics

State:
Created 2 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

2reactions

jovinson-mscommented, Oct 20, 2021

Closing as the PR has merged - thanks for working through the PR build issues with us @wbalbo!

1reaction

jovinson-mscommented, Oct 13, 2021

Thanks, @wbalbo! I’ll take a look tomorrow.

Top Results From Across the Web

How to set the Content-Type header for an HttpClient ...

Misused header name. Make sure request headers are used with HttpRequestMessage , response headers with HttpResponseMessage , and content ...

Shouldn't WADO-RS define Content-Type as "multipart ...

I'd like to start a discussion on the validity/desirability of defining the Content-Type for WADO-RS responses as "multipart/related".

6.6 STOW-RS Request/Response - DICOM Standard - NEMA

The first part in the multipart request will contain the following HTTP headers: Content-Type: application/dicom+xml; transfer-syntax={TransferSyntaxUID}.

DICOM Conformance Statement v1 - Azure

The following Accept header(s) for the response are supported: application/dicom+json. The following Content-Type header(s) are supported:.

Content-Type - HTTP - MDN Web Docs - Mozilla

In responses, a Content-Type header provides the client with the actual content type of the returned content. This header's value may be ignored ......