We are updating from ServiceStack 4.0.52 to 4.5.14, obviously realizing that this is a major upgrade we’ve thoroughly reviewed Release Notes and tested services extensively. One behavior that we’re seeing that we’re not able to explain is the following.
We use the builtin ?format=json URL param or .json extension instead of Accept header from some 3rd party clients where we cannot control the request headers. There are now exceptions being thrown like:
Exception: WARN: Property 'format' does not exist on type 'XX.Dto'
Similarly there are other URL params that we pass in POST request like “X-Client-Id” that are not a fields with DTOs but used globally to identify calling client, etc. These are throwing similar errors.
Example:
POST /note/add.json?X-Client_Id=123
with JSON body like
{
"id": 1,
"content":"foo"
}
This appears to be resulting in a 400 “Bad Request”. We’re seeing correlated errors like:
Message: Unable to bind to request 'Note'
Source: ServiceStack.Client
Has this behavior changed? Please advise. I know this is unrelated but we’ve already turned StrictMode=false for other reasons.