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
Match real Vuforia's reco counts report URL, expiry and not-ready response (#3570)
* Match real Vuforia's reco counts report URL, expiry and not-ready response
Closes#3364.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Keep report tests branch-free across hour boundaries and clear the target manager before Flask usage tests
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
The URL of a reco counts report now has the shape of the presigned cloud storage URL which real Vuforia returns.
2
+
The report file is named ``{date}-{hour}.csv`` for the current month and ``{month}.csv`` for the previous month, so two requests for the same month in the same hour name the same file and serve the report which the first request generated.
3
+
The URL carries the query parameters of a presigned URL, and the mock honors ``X-Amz-Date`` and ``X-Amz-Expires`` as real Vuforia's storage does, so a URL which is out of date or which has no query parameters gives the ``403`` XML error document which Amazon S3 gives.
4
+
A report which is not yet generated gives the ``404`` ``NoSuchKey`` XML error document which Amazon S3 gives, as real Vuforia has now been observed to do, rather than an empty body.
0 commit comments