You may add an expiration date and/or time to the report request by including expires= as part of the URL or in a form field that POSTs to the ViewReport.aspx page. For example, the request below will return an expired message and will not show the report.
ViewReport.aspx?reportName=library.rpt&expires=08/18/2018ISO 8601, RFC 1123, and other formats are valid for the expires value. The following show date and time formats and the resulting interpreted value. Non-ISO formats may differ depending on your server’s region settings.
| Description | Value | Interpreted value using US format (MM/DD/YYYY) |
|---|---|---|
| Date and time | 08/18/2018 07:22:16 | 8/18/2018 7:22:16 AM |
| Date only | 08/18/2018 | 8/18/2018 12:00:00 AM |
| Month and year | 8/2018 | 8/1/2018 12:00:00 AM |
| ISO 8601 UTC | 2018-08-18T07:22:16.0000000Z | 8/18/2018 12:22:16 (assumes 5 hour UTC difference from server’s local time) |
| RFC 1123 | Sat, 18 Aug 2018 07:22:16 GMT | 8/18/2018 12:22:16 (assumes 5 hour UTC difference from server’s local time) |
| Date and time with time zone | 08/18/2018 07:22:16 -5:00 | 8/18/2018 5:22:16 AM (time dependent on server’s time zone) |
The expires value as plain text may be easily modified by users. When included as part of an encrypted request the value is not observable and is tamper resistant. For example, when encrypted the request
ViewReport.aspx?reportName=library.rpt&expires=08/18/2018becomes
ViewReportEncrypted.aspx?request=KCLffZ0JX9W7UBWtv9p%2boPpatu%2fUcI61YpF9Y1XruZnpuNv5ZgaYxPnosYYPBa0v
Last modified:
11 November 2021
Post your comment on this topic.