Mercurial > hg > orthanc
view Resources/Samples/Lua/ParseDoseReport.lua @ 2248:69b0f4e8a49b
Escape multipart type parameter value in Content-Type header
## Summary
Multipart responses do not quote/escape the value of their type
parameter (the subtype) even though it always contains at least one
special character (the slash "/"), which confuses standard-compliant
HTTP clients.
## Details
The Content-Type header in HTTP is in RFC 7231, Section 3.1.1.5:
https://tools.ietf.org/html/rfc7231#section-3.1.1.5
The section defers to the media type section (3.1.1.1) for the syntax of
the media type:
https://tools.ietf.org/html/rfc7231#section-3.1.1.1
This states that a parameter value can be quoted:
parameter = token "=" ( token / quoted-string )
A parameter value that matches the token production can be transmitted
either as a token or within a quoted-string. The quoted and unquoted
values are equivalent.
Tokens are defined in RFC 7230, Section 3.2.6 (via RFC 7231, appendix
C):
https://tools.ietf.org/html/rfc7231#appendix-C
https://tools.ietf.org/html/rfc7230#section-3.2.6
Here we observe that tokens cannot contain a slash "/" character:
token = 1*tchar
tchar = "!" / "#" / "$" / "%" / "&" / "'" / "*"
/ "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
/ DIGIT / ALPHA
; any VCHAR, except delimiters
Delimiters are chosen from the set of US-ASCII visual characters not
allowed in a token (DQUOTE and "(),/:;<=>?@[\]{}").
However, the current implementation does not quote/escape the value of
the type parameter:
multipart/related; type=application/dicom
Instead, it should be:
multipart/related; type="application/dicom"
All of this also seems to apply to the MIME Content-Type header
definition, even though it is a little different:
https://www.iana.org/assignments/message-headers
https://tools.ietf.org/html/rfc2045#section-5.1
https://tools.ietf.org/html/rfc2387
author | Thibault Nélis <tn@osimis.io> |
---|---|
date | Mon, 16 Jan 2017 13:07:11 +0100 |
parents | 1e6fbb2dcc6f |
children |
line wrap: on
line source
-- Sample Lua script that demonstrates how to extract DICOM tags -- related to dose reports. In this example, the value of the DLP -- (Dose Length Product), the value of the mean CTDI volume (Computed -- Tomography Dose Index), and the number of "IntervalsRejected" are -- extracted and printed. Furthermore, these values are saved as -- metadata that is attached to their parent DICOM instance for -- further processing by external software. function ExploreContentSequence(instanceId, tags) if tags then for key, value in pairs(tags) do -- Recursive exploration ExploreContentSequence(instanceId, value['ContentSequence']) local concept = value['ConceptNameCodeSequence'] local measure = value['MeasuredValueSequence'] if concept and measure then local value = measure[1]['NumericValue'] local code = concept[1]['CodeValue'] if type(value) == 'string' and type(code) == 'string' then -- If the field contains the DLP, stores it as a metadata. -- "DLP" is associated with CodeValue 113838. -- ftp://medical.nema.org/medical/dicom/final/sup127_ft.pdf if code == '113838' then print('DLP = ' .. value) RestApiPut('/instances/' .. instanceId .. '/metadata/2001', value) end -- Extract the mean CTDI volume if code == '113830' then print('CTDI = ' .. value) RestApiPut('/instances/' .. instanceId .. '/metadata/2002', value) end -- Other values can be extracted here end end end end end function StoreTagToMetadata(instanceId, tags, name, metadata) if tags then for key, value in pairs(tags) do if type(value) ~= 'string' then -- Recursive exploration StoreTagToMetadata(instanceId, value, name, metadata) elseif key == name then print(name .. ' = ' .. value) if metadata then RestApiPut('/instances/' .. instanceId .. '/metadata/' .. metadata, value) end end end end end function OnStoredInstance(instanceId, tags) StoreTagToMetadata(instanceId, tags, 'IntervalsRejected', 2000) ExploreContentSequence(instanceId, tags['ContentSequence']) end