d1db0c7363
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>
9 lines
492 B
YAML
9 lines
492 B
YAML
---
|
|
upgrade:
|
|
- The ``JSON_ENC`` and ``TXT_ENC`` option in the ``_error_checker``
|
|
section have been added with additional content-type which are
|
|
defined in RFC7231 but missing in the currnt rest_client.py file.
|
|
The lack of these additional content-type will cause defcore test
|
|
to fail for OpenStack public cloud which uses tomcat module in the
|
|
api gateway. The additions are ``application/json;charset=utf-8``,
|
|
``text/html;charset=utf-8``,``text/plain;charset=utf-8`` |