Inspect the client request
Before creating a custom encryption rule, you must determine the format of the client request entering the Edge Encryption proxy server.
Before you begin
Role required: admin
About this task
Because encryption rules iterate over client requests and determine what, if anything, needs to be encrypted, you must understand the type of request you're creating a rule for. The format of the client request determines the structure of your encryption rule and the APIs available for use in the rule.
Procedure
Inspect the client request.
Depending on the source of the request, the following tools are available to inspect the request and determine the format.
| Source of request | Available tools |
|---|---|
| Client browser | Use the developer console in your browser to inspect the client request. Useful tools include: - Firefox Network Monitor - Chrome Network Panel |
| Third-party/external source | Use an HTTP protocol analyzer to inspect the request. Useful tools include: - Wireshark - HTTP Scoop Alternatively, you can often use documentation for the external source to determine the format of the request. |
From the client request, inspect the packet and determine:
- The client request method
- The URL path of the request
- The URL parameters
- The POST parameters, if any
- The format of the request body, if included
Client request example
Result
Inspecting the request provides an understanding of the fields you need to filter for and iterate over in your encryption rule. To understand the fields in the request object, see request.
Parent Topic:Define a custom encryption rule