Mercurial > hg > orthanc
view Resources/LinuxStandardBaseToolchain.cmake @ 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 | ded40a9e8cc8 |
children | 862d943115f9 |
line wrap: on
line source
INCLUDE(CMakeForceCompiler) SET(LSB_PATH $ENV{LSB_PATH}) SET(LSB_TARGET_VERSION "4.0") IF ("${LSB_PATH}" STREQUAL "") SET(LSB_PATH "/opt/lsb") ENDIF() message("Using the following Linux Standard Base: ${LSB_PATH}") IF (EXISTS ${LSB_PATH}/lib64) SET(LSB_TARGET_PROCESSOR "x86_64") SET(LSB_LIBPATH ${LSB_PATH}/lib64-${LSB_TARGET_VERSION}) ELSEIF (EXISTS ${LSB_PATH}/lib) SET(LSB_TARGET_PROCESSOR "x86") SET(LSB_LIBPATH ${LSB_PATH}/lib-${LSB_TARGET_VERSION}) ELSE() MESSAGE(FATAL_ERROR "Unable to detect the target processor architecture. Check the LSB_PATH environment variable.") ENDIF() SET(LSB_CPPPATH ${LSB_PATH}/include) SET(PKG_CONFIG_PATH ${LSB_LIBPATH}/pkgconfig/) # the name of the target operating system SET(CMAKE_SYSTEM_NAME Linux) SET(CMAKE_SYSTEM_VERSION LinuxStandardBase) SET(CMAKE_SYSTEM_PROCESSOR ${LSB_TARGET_PROCESSOR}) # which compilers to use for C and C++ SET(CMAKE_C_COMPILER ${LSB_PATH}/bin/lsbcc) CMAKE_FORCE_CXX_COMPILER(${LSB_PATH}/bin/lsbc++ GNU) # here is the target environment located SET(CMAKE_FIND_ROOT_PATH ${LSB_PATH}) # adjust the default behaviour of the FIND_XXX() commands: # search headers and libraries in the target environment, search # programs in the host environment SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)