Assertion: 6.4.32 fails on 204, expects 200 about redfish-service-conformance-check HOT 2 CLOSED

________________________________ From: Bill Dodd <[email protected]> Sent: Wednesday, January 3, 2018 5:08 PM To: DMTF/Redfish-Service-Conformance-Check Cc: Watts, John - Dell Team; Author Subject: Re: [DMTF/Redfish-Service-Conformance-Check] Assertion: 6.4.32 fails on 204, expects 200 (#62) Yes, looks like 204 should be fine. Seems like in most cases, any time a 200 response is OK, a 204 would also be OK. It wouldn't be OK of course in cases where a response is required. Thinking that the response_status_check() function in the tool should be modified to allow both 200 and 204 in the case where an explicit response code is not specified. - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#62 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACN_nsHMxmDra9iWux-xU-RLlclWDalAks5tHAh3gaJpZM4RSLMd>.