view Resources/Samples/Lua/CallImageJ.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 34c8954544e8
children
line wrap: on
line source

-- This sample shows how to invoke an ImageJ script on every DICOM
-- image received by Orthanc. The ImageJ script is generated by the
-- "Initialize()" function at the startup of Orthanc. Whenever a new
-- instance is received, its DICOM file is stored into a temporary
-- file, and a system call to ImageJ is triggered.

SCRIPT = 'ImageJScript.txt'

function Initialize()
   local target = assert(io.open(SCRIPT, 'w'))

   -- This is a sample ImageJ script that display the size of the DICOM image
   target:write('if (getArgument=="") exit ("No argument!");\n')
   target:write('open(getArgument);\n')
   target:write('print(getTitle + ": " + getWidth + "x" + getHeight);\n')

   target:close()
end

function OnStoredInstance(instanceId)
   -- Retrieve the DICOM instance from Orthanc
   local dicom = RestApiGet('/instances/' .. instanceId .. '/file')

   -- Write the DICOM content to some temporary file
   local path = instanceId .. '.dcm'
   local target = assert(io.open(path, 'wb'))
   target:write(dicom)
   target:close()

   -- Call ImageJ
   os.execute('imagej -b ' .. SCRIPT .. ' ' .. path)

   -- Remove the temporary DICOM file
   os.remove(path)
end