Create an Original Experience course

Enter a Content Area

Select Build Content > File

Upload or reuse a file

Enter the Content Collection

Find the File from step 4, select ▼ > Edit Settings

Under "Options", select Enable Tracking

Use the course as any other course

After a while, return to the content collection and again find the file from Step 4.

Select ▼ > 360° View

Under the "File Activity" section, review the "Tracking Data"

Browsers and other HTTP clients, such as WebDAV clients, usually cache content. When this occurs, the client avoids re-requesting the same data. For example it sends a header If-Modified-Since to indicate that the server should only send bytes if the file has been modified since that date. Since in most cases the file has not been modified, Xythos returns HTTP 304 and no bytes are read.

Another other reason which is specific to SaaS is that the term "read" means bytes from a blob are read directly by Xythos itself. However in SaaS this rarely happens. When possible, the application instead generates a S3 Pre-signed URL and sends an HTTP redirect response to the caller. The browser (or other client) then downloads bytes directly from S3 or the CDN and no bytes are ever read by Xythos. It is also impossible to know if this activity succeeded or failed and any bytes were read or not.