petkivim
commented
6 years ago X-Road Message Protocol v4.0 requires that all the header fields are present in the exact same order in both request and response messages. All the header fields includes all custom header fields too.
It seems that this request is actually about changing the X-Road Message Protocol rather than just updating the documentation. The proposed changes will be considered for future versions of the protocol.
Affected components: - Affected documentation: X-Road Message Protocol Estimated delivery: - External reference: -
Problem
In X-Road: Message Protocol v4.0 is sentence "When responding, the service MUST copy all the header fields from the request to the response in the exact same sequence with the exact same values." is too rigid
"exact same sequence" is technically complicated to comply and purpose is abstruse
"all the header fields from the request to the response" is too general. Perhaps "all identifier header fields (Table 1) ..." is clearer? There is no restrictions to add custom header fields.
Acceptance criteria