Correct Content-Type/Accept management in HTTPClient/SessionClient
Currently SessionClient.request never specifies Content-Type/Accept
headers in requests where HTTPClient.request always specifies json
Content-Type/Accept even with "--request-format xml" option ... requests
succeed because neutron deduces Content-Type/Accept from url suffix when
defined.
This change ensures HTTPClient/SessionClient define Content-Type/Accept
headers when needed and align them with --request-format option.
Reviewed: https:/ /review. openstack. org/121014 /git.openstack. org/cgit/ openstack/ python- neutronclient/ commit/ ?id=fb83043e152 e2181ed2431125b ba32d89e3908b7
Committed: https:/
Submitter: Jenkins
Branch: master
commit fb83043e152e218 1ed2431125bba32 d89e3908b7
Author: Cedric Brandily <email address hidden>
Date: Thu Sep 11 21:14:18 2014 +0200
Correct Content-Type/Accept management in HTTPClient/ SessionClient
Currently SessionClient. request never specifies Content-Type/Accept Type/Accept even with "--request-format xml" option ... requests
headers in requests where HTTPClient.request always specifies json
Content-
succeed because neutron deduces Content-Type/Accept from url suffix when
defined.
This change ensures HTTPClient/ SessionClient define Content-Type/Accept
headers when needed and align them with --request-format option.
Closes-Bug: #1368335 5870a28ebb0f171 812acca0745
Change-Id: I909e055e5e59fa