melanie witt bc491817e1 Allow logging of Content-Type text/plain
Noticed this while doing some local testing, if a WSGI app replies with
a text/plain content type to communicate a server error, we aren't able
to see the error response message when passing --debug to the
openstackclient, example:

  RESP: [500] Date: Thu, 01 Oct 2020 23:54:15 GMT Server: Apache/2.4.18
  (Ubuntu) Content-Type: text/plain; charset=UTF-8 Connection: close
  Transfer-Encoding: chunked
  RESP BODY: Omitted, Content-Type is set to text/plain; charset=UTF-8.
  Only application/json responses have their bodies logged.

Change-Id: Ibfd46c7725bd0aa26f1f80b0e8fc6eda2ac2e090
2022-04-29 15:57:52 +00:00
2021-01-08 21:57:16 +00:00
2015-12-09 11:46:00 +11:00
2017-09-20 15:47:15 -05:00
2019-04-19 19:39:37 +00:00
2014-05-07 12:12:43 -07:00
2017-09-20 15:47:15 -05:00
2020-06-22 10:04:17 -05:00
2017-09-20 15:47:15 -05:00
2019-09-06 15:57:40 +08:00
2020-04-17 18:46:54 +02:00
2022-01-21 13:28:46 +01:00

Team and repository tags

image

keystoneauth

Latest Version

Downloads

This package contains tools for authenticating to an OpenStack-based cloud. These tools include:

  • Authentication plugins (password, token, and federation based)
  • Discovery mechanisms to determine API version support
  • A session that is used to maintain client settings across requests (based on the requests Python library)

Further information:

Description
OpenStack Identity Authentication Library
Readme 12 MiB
Languages
Python 100%