HTTP headers overwritten by library about python-redfish-library HOT 5 CLOSED

I think that sounds reasonable; only add the headers if not already specified by the user. Most users I would expect to never attempt to set these headers.

from python-redfish-library.

I can understand OData-Version being overwritten; anything other than "4.0" is outside scope of the Redfish spec and can result in undefined behavior.

Accept is a bit more problematic though; while the vast majority of Redfish will require "application/json", there are a handful of cases where that won't be the response (primarily $metadata as well as a few URIs that might result in application/octet-stream). I can understand overriding Accept in most cases though.

from python-redfish-library.

The problem is I can`t overwrite these values, so I cannot verify if a service reacts correctly on not expected headers values.
Do you have an idea how to continue?
Propose such change which would not overwrite these headers when are delivered by user?

from python-redfish-library.

Hi, pull request for this topic is created (#94).

from python-redfish-library.

PR merged

from python-redfish-library.