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

This file is a complement to "INSTALL", which contains instructions
that are specific to Mac OS X (Darwin).


Static linking for OS X using XCode
===================================

The most simple way of building Orthanc under OS X consists in
statically linking against all the third-party dependencies. In this
case, no package manager such as Homebrew or MacPorts is required.
The build tool (CMake) will download the sources of all the required
packages and automatically compile them.


Prerequisites
-------------

1) XCode must be installed.

2) CMake must be installed (http://www.cmake.org/).

3) It is assumed that Orthanc source code is placed in the folder
   "~/Orthanc" and that the binaries will be compiled to
   "~/OrthancBuild".


Prepare the build with CMake
----------------------------

# cd ~/OrthancBuild
# cmake -GXcode -DCMAKE_OSX_DEPLOYMENT_TARGET=10.8 -DSTATIC_BUILD=ON -DSTANDALONE_BUILD=ON -DALLOW_DOWNLOADS=ON ~/Orthanc

NB: Adapt the value of "CMAKE_OSX_DEPLOYMENT_TARGET" with respect to
your version of OS X. This version can obtained by typing:

# sw_vers


Build the Debug version of Orthanc
----------------------------------

# xcodebuild
# ./Debug/UnitTests

The binaries of Orthanc are located at "~/OrthancBuild/Debug/Orthanc".


Build the Release version of Orthanc
------------------------------------

# xcodebuild -configuration Release
# ./Release/UnitTests

The binaries of Orthanc are located at "~/OrthancBuild/Release/Orthanc".