tempest/releasenotes/notes/16/16.0.0-add-content-type-without-spaces-b2c9b91b257814f3.yaml
Masayuki Igawa 7ba22721e5
Use inline literal markup for options in releasenotes
This commit makes the releasenotes to use 'inline literal markup[0]
because it would be accurate rendering for commandline
options. Otherwise, dashes are changed into an en/em dash entity. And
this commit also fixes some inline literal markups which I
noticed. Ideally, we should fix like that things in one
patch. However, it's a bit hard to find them all..

[0] http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#roles

Change-Id: I8f7691b3ff40ccde051620f44217dab244d76960
2018-05-31 11:31:02 +09:00

10 lines
495 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 current 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``