Every section.io application proxy stack implicitly begins with the Edge proxy. The Edge proxy is the endpoint to which the User-Agent (eg web browser) connects and it has a few responsibilities:
- Performing the TLS handshake for HTTPS connections
- Routing requests to the corresponding application proxy stack
- Implementing the HTTP/2 protocol
- Request correlation
- Serving custom error pages
This enables a consistent experience on the section.io platform regardless of which proxies are in your application’s stack or in which sequence they appear.
When the Edge proxy handles each incoming request, a unique identifier is generated and is added to the request via a
section-io-id HTTP request header.
This request header then propagates through to each proxy in your application’s proxy stack and ultimately to your application’s configured origin web server. When the final response is returned from your application, via the proxy stack, to the User-Agent, the Edge proxy also inserts the same identifier as a
section-io-id HTTP response header.
section-io-id value is available in all the proxy logs provided by Aperture to enable easy correlation of log entries across the different proxies in the stack. You can also choose to log the
section-io-id request header on your origin server to aid with diagnostics.
By providing the identifier as a request header, its value can be consumed in your chosen proxies. For example, Varnish can refer to
req.http.section-io-id in the VCL.
The format of the
section-io-id identifier is subject to change without notice so it should be treated as an opaque string and no meaning should be inferred from its value.