Constellation Case Submission is throwing 400 Error with ifMatchHeader missing

Hi ,

We’re on Infinity 23.1.0, trying to build new case types using constellation. We’re hosted on-prem and using Pega static CDN for the constellation app static.

During this we’re seeing some errors in the case type processing, errors observed in the case type submission.

Issue observed is with DX API with Patch Method, where once the case is setup and trying to submit, it is failing with 400 status code and ifMatchHeader missing.

Anyone has seen this error?

Error: “Required parameter ifMatchHeader has no value”

Response: 400 http status code.

Resource: api/application/v2/ assignments/{assignmentID}/actions/{actionID}

Response Payload:

{
“errorClassification”: “Invalid inputs”,
“localizedValue”: “One or more inputs are invalid”,
“errorDetails”: [
{
“message”: “pyValueIsRequired\tifMatchHeader”,
“erroneousInputOutputFieldInPage”: “”,
“erroneousInputOutputIdentifier”: “”,
“errorClassification”: “”,
“localizedValue”: “Required parameter ifMatchHeader has no value.”,
“messageParameters”:
},
{
“message”: “Invalid inputs provided, e.g. missing required inputs, incorrect property types”,
“erroneousInputOutputFieldInPage”: “”,
“erroneousInputOutputIdentifier”: “”,
“errorClassification”: “”,
“localizedValue”: “Invalid inputs provided, e.g. missing required inputs, incorrect property types”,
“messageParameters”:
}
]
}

@MadhavaRaoJ updating a case must provide an etag that is unique and guarantee that the case is not stale - see Pegasystems Documentation

@RichardMarsot Thank you for response, we were able to identify the issue. In our Apache global configuration, we have a filter to remove eTag header. Looks like this was added for security reasons and this setting applies to all enterprise apps.

we worked with our internal middleware teams to remove filter for the Pega hosted apps.

Post to this change, we’re seeing the header is retaining and subsequent calls are going thru.