You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At several places in rf_utility.py, the Basic Authentication Header is formed with a string "BASIC ".
The syntax in RFC1945 section 11.1 uses the string "Basic".
RFC2616 section 4.2 says Header Field names are case insensitive.
But does that apply to header values as well?
This is the first Redfish tool to use the full upper case BASIC string in this header.
Is this allowed? Is it good idea?
The text was updated successfully, but these errors were encountered:
"Note that both scheme and parameter names are matched case-insensitively."
In this context, "Basic" is the scheme name.
That said, the tool should not be trying to trip up services that don't properly do case insensitive matches. So it seems reasonable to me to change to the tool to use "Basic" like all the examples show.
At several places in rf_utility.py, the Basic Authentication Header is formed with a string "BASIC ".
The syntax in RFC1945 section 11.1 uses the string "Basic".
RFC2616 section 4.2 says Header Field names are case insensitive.
But does that apply to header values as well?
This is the first Redfish tool to use the full upper case BASIC string in this header.
Is this allowed? Is it good idea?
The text was updated successfully, but these errors were encountered: