Loading...

XML

Word

Printable

Steps to Reproduce:
Hide

Create ApiVersion 1.0

Add Transfer Quota Policy with following configuration

quota of 10 B of upload data per API per minute

Publish the ApiVersion 1.0

Policy works as expected

Create ApiVersion 2.0 without policy

Create ClientApp with Transfer Quota Policy (same configuration as above)

Create contract: ApiVersion 2.0 <-> ClientApp

Policy on ClientApp works as expected, but policy on ApiVersion 1.0 starts acting weird:

Repeatedly POST one byte on ApiVersion 1.0

values of X-TransferQuota-Remaining are unexpected - 9, 9, 8, 7, 6, 9, 5, 4, 3, 2, 1, 0, 0, 5, 4, 3, 0 ...
Show
Create ApiVersion 1.0 Add Transfer Quota Policy with following configuration quota of 10 B of upload data per API per minute Publish the ApiVersion 1.0 Policy works as expected Create ApiVersion 2.0 without policy Create ClientApp with Transfer Quota Policy (same configuration as above) Create contract: ApiVersion 2.0 <-> ClientApp Policy on ClientApp works as expected, but policy on ApiVersion 1.0 starts acting weird: Repeatedly POST one byte on ApiVersion 1.0 values of X-TransferQuota-Remaining are unexpected - 9, 9, 8, 7, 6, 9, 5, 4, 3, 2, 1, 0, 0, 5, 4, 3, 0 ...