# US 2022/0286494 A1 · Cached web probes for monitoring user experience

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0286494 A1
- Document ID: US20220286494A1
- Status: Published application
- Kind: A1
- Application number: 17/235,267
- Filed: 2021-04-20
- Published: 2022-09-08
- Earliest claimed: 2021-03-05
- Assignees: Zscaler, Inc.
- Applicants: Zscaler, Inc.
- Inventors: Chenglong Zheng; Srikanth Devarajan; Vikas Mahajan; Sandeep Kamath Voderbet
- Web page: https://patentgrep.com/patent/US20220286494A1

## CPC

- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 43/12: Network monitoring probes
- H04L 63/0281: {Proxies}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 67/561: Adding application-functional data or data for application control, e.g. adding metadata
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 67/5682: Policies or rules for updating, deleting or replacing the stored data
- H04L 67/61: taking into account QoS or priority requirements
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 63/0272: {Virtual private networks}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques for using web probes for monitoring user experience including use of caching to prevent a surge of web probes on destination servers and for detecting web probe traffic through a proxy including where the traffic is encrypted. A method implemented by a proxy includes receiving a response to a first web probe to a destination server; caching data associated with the response to the first web probe in a cache; receiving a request for a second web probe to the destination server; and serving a response to the second web probe utilizing the data in the cache in lieu of forwarding the second web probe to the destination server.

## Claims

### Claim 1

A method implemented by a proxy comprising:
receiving a response to a first web probe to a destination server;
caching data associated with the response to the first web probe in a cache, wherein the data includes unique entries created based on request properties;
receiving a request for a second web probe to the destination server;
serving a response to the second web probe utilizing the data in the cache in lieu of forwarding the second web probe to the destination server; and
applying all policies to the response served utilizing the data in the cache that are applied to regular traffic.

### Claim 2 (depends on 1)

The method of claim 1, further comprising
removing the data in the cache after a configurable time period.

### Claim 3 (depends on 1)

The method of claim 1, further comprising
receiving a request for the first web probe prior to the response; and
sending the first web probe to the destination server prior to the response.

### Claim 4 (depends on 1)

The method of claim 1, further comprising
receiving a third web probe while a response to a fourth web probe is outstanding;
queuing the third web probe until the response to the fourth web probe is cached;
recording the wait time in the queue; and
deducting the wait time from Time To First Byte (TTFB) and Time To Last Byte (TTLB) calculations.

### Claim 5 (depends on 1)

The method of claim 1, wherein the data in the cache includes how the first web probe is forwarded to the destination server.

### Claim 6 (depends on 1)

The method of claim 1, wherein the response to the second web probe includes truncated data.

### Claim 7 (depends on 1)

The method of claim 1, wherein the web probe is one of a Hypertext Transfer Protocol (HTTP) and HTTP-Secure (HTTPS) request to a Uniform Resource Locator (URL) of the destination server.

### Claim 8 (depends on 1)

The method of claim 1, wherein the data in the cache is stored as a hash table with a key being an identifier for a tenant plus a hash of the first web probe and a value is results.

### Claim 9

A non-transitory computer-readable storage medium having computer-readable code stored thereon for programming a proxy to perform steps of:
receiving a response to a first web probe to a destination server;
caching data associated with the response to the first web probe in a cache, wherein the data includes unique entries created based on request properties;
receiving a request for a second web probe to the destination server;
serving a response to the second web probe utilizing the data in the cache in lieu of forwarding the second web probe to the destination server; and
applying all policies to the response served utilizing the data in the cache that are applied to regular traffic.

### Claim 10 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the steps include
removing the data in the cache after a configurable time period.

### Claim 11 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the steps include
receiving a request for the first web probe prior to the response; and
sending the first web probe to the destination server prior to the response.

### Claim 12 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the steps include
receiving a third web probe while a response to a fourth web probe is outstanding;
queuing the third web probe until the response to the fourth web probe is cached;
recording the wait time in the queue; and
deducting that wait time from Time To First Byte (TTFB) and Time To Last Byte (TTLB) calculations.

### Claim 13 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the data in the cache includes how the first web probe is forwarded to the destination server.

### Claim 14 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the response to the second web probe includes truncated data.

### Claim 15 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the web probe is one of a Hypertext Transfer Protocol (HTTP) and HTTP-Secure (HTTPS) request to a Uniform Resource Locator (URL) of the destination server.

### Claim 16 (depends on 9)

The non-transitory computer-readable storage medium of claim 9, wherein the data in the cache is stored as a hash table with a key being an identifier for a tenant plus a hash of the first web probe and a value is results.

### Claim 17

A proxy comprising:
one or more processors and memory comprising instructions that, when executed, cause the one or more processors to
receive a response to a first web probe to a destination server;
cache data associated with the response to the first web probe in a cache, wherein the data includes unique entries created based on request properties;
receive a request for a second web probe to the destination server;
serve a response to the second web probe utilizing the data in the cache in lieu of forwarding the second web probe to the destination server; and
apply all policies to the response served utilizing the data in the cache that are applied to regular traffic.

### Claim 18 (depends on 17)

The proxy of claim 17, wherein the instructions that, when executed, cause the one or more processors to
remove the data in the cache after a configurable time period.

### Claim 19 (depends on 17)

The proxy of claim 17, wherein the instructions that, when executed, cause the one or more processors to
receive a request for the first web probe prior to the response; and
send the first web probe to the destination server prior to the response.

### Claim 20 (depends on 17)

The proxy of claim 17, wherein the instructions that, when executed, cause the one or more processors to
receive a third web probe while a response to a fourth web probe is outstanding;
queue the third web probe until the response to the fourth web probe is cached;
record the wait time in the queue; and
deduct the wait time from Time To First Byte (TTFB) and Time To Last Byte (TTLB) calculations.
