You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the latest SDK 2.1.1. It seems that if I set ConnectionPolicy's connection mode to be DirectHttps, RequestOptions' AccessCondition (type: IfMatch) will no longer be enforced. Request with non matching AccessCondition would succeed. My expectation is that such request would get a 412 with {"Errors":["One of the specified pre-condition is not met"]} just like the Gateway connection mode, but it doesn't behave like that. This is a nasty bug, please fix it.
The text was updated successfully, but these errors were encountered:
Hi @dyzwang , Can you please add a repro here or raise a ticket with [email protected] ?
I checked the behavior locally, and it looks to be working correctly.
I'm using the latest SDK 2.1.1. It seems that if I set
ConnectionPolicy
's connection mode to beDirectHttps
,RequestOptions
'AccessCondition
(type:IfMatch
) will no longer be enforced. Request with non matchingAccessCondition
would succeed. My expectation is that such request would get a 412 with {"Errors":["One of the specified pre-condition is not met"]} just like theGateway
connection mode, but it doesn't behave like that. This is a nasty bug, please fix it.The text was updated successfully, but these errors were encountered: