Cannot require multiple headers in separate Trait or Headers definitions #1258
If I define two separate traits, each with a required header, such as:
Then use them both on an action,
Only the one mentioned first("version_required” in this case) will be required. The subsequent ones will be validated for data type if sent, but not required.
The same is true for headers added directly to the action.
Etag will be required, but X-Api-Version will not be.
If I require all headers in the same Trait or Headers definition, it does work as expected and requires them all.
The text was updated successfully, but these errors were encountered: