Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| applications:report-fetcher [2025/12/01 12:49] – [Usage] root | applications:report-fetcher [2026/03/20 09:38] (current) – add persist parameter details root | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| | start_date | 2025-12-25 | | | start_date | 2025-12-25 | | ||
| | end_date | 2026-01-25 | | | end_date | 2026-01-25 | | ||
| + | | persist | True | | ||
| For example: | For example: | ||
| Line 30: | Line 31: | ||
| The `product_name` parameter should contain just one name, if you wish to return data for multiple events, this should be passed as a list of CSVs to `product_names`. Only one of these should be used at a time. If you try to pass both `product_name` and `product_names` in the same query it will return an error. | The `product_name` parameter should contain just one name, if you wish to return data for multiple events, this should be passed as a list of CSVs to `product_names`. Only one of these should be used at a time. If you try to pass both `product_name` and `product_names` in the same query it will return an error. | ||
| + | |||
| + | The `persist` parameter is a new key implemented due to a change in the MSL authentication handling which means that auth cookies now expire in ~15 minutes. It's obviously not feasible to refresh the cookie every 15 minutes, so instead if `persist` is set to True, the system will store the auth token given, and every 10 minutes or so, refresh it. This new refreshed cookie is only stored in living memory, so if the application shuts down then the refreshed cookie will be lost and a new one will need to be provided. | ||