FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
JNDias
Staff
Staff
Article Id 250992

Description

 

This article describes how buffering and streaming affect the way a FortiGate's 'Category Usage Quota' time is counted.

 

Scope

 

FortiGate 7.2.4 and earlier.

FortiGate WebFilter.

Proxy-based mode.

 

Solution

 

The 'time' quota type only counts time when data is being downloaded. When the buffer is full, it stops counting. When the buffer ends, the browser requests a new block of data, resulting in more time being counted.

 

Buffering

 

Example:

 

Untitled picture.png

- With a typical video clip, a large buffer is created. As a result, the time is only measured by how long it takes for that block of data to download.

- It downloads 10 MB of data in 2 seconds where the user can watch for 1 minute. When this buffer ends, it will download a large block of data again in 2 seconds with some more watching time. In the end, was only 4 seconds of the time quota were used.

 

Streaming

 

Untitled picture2.png

- In a 'live stream' the browser is constantly requesting data, thereby increasing the time quota.

- However, the quota will not exactly match the playtime because requests will come in durations of between 1 to 10 seconds (creating a small buffer).

- On a stream of 1 min, the stream time quota may be a few seconds less.

 

Related documentation

- Docs Usage quota

- External Link website - Buffers and Streams Explained in NodeJs

Contributors