tree c950ef80312c0ba7d583c9a2a6116ad1112f8a66
parent fc5a3733df149ddc5a6356915eeca2ad4d7bbcfb
author zhipengh <huangzhipeng@huawei.com> 1487670007 -0500
committer zhipengh <huangzhipeng@huawei.com> 1487909404 -0500

Add content-type without spaces

In public cloud implementation, the tomcat module
(specifically tomcat-coyote) used by the api-gateway
will eliminate the space within the content-type,
e.g ret = ret + ";charset=" + this.characterEncoding;

In the current rfc7231 standard, all the following
content-type are permissible and equivalent:
test/html;charset=utf-8
test/html;charset=UTF-8
test/HTML;Charset="utf-8"
test/html; charset="utf-8"
(https://tools.ietf.org/html/rfc7231#section-3.1.1.1)

However in the current tempest rest_client setting,
there is no content-type without space defined in
JSON_ENC and TXT_ENC. This results in defcore test
failure for public cloud since after tomcat module
eliminates the space, the content-type will not be
recognized as a legitimate one.

This patch intends to solve this problem by providing
additional content-type without spaces as allowed in
rfc7231 to JSON_ENC and TXT_ENC so that defcore test
won't be blocked for public cloud implementation.

Change-Id: I718ef0e3ddae513cb911aca38985162027274001
Signed-off-by: zhipengh <huangzhipeng@huawei.com>