HTTP Headers
Standardized HTTP headers
There are many common HTTP headers that are standardized and used universally. Very few of these headers affect Skip2, here are those that do:
alt-svc
Skip2 returns an alt-svc http header to indicate to clients that they can stop using TCP and start using UDP for transport (QUIC).
cache-control
Skip2 returns an alt-svc http header to indicate to clients that they can stop using TCP and start using UDP for transport (QUIC).
cache-status
Skip2 returns an alt-svc http header to indicate to clients that they can stop using TCP and start using UDP for transport (QUIC).
server
Skip2 returns an alt-svc http header to indicate to clients that they can stop using TCP and start using UDP for transport (QUIC).
etag
Skip2 returns an alt-svc http header to indicate to clients that they can stop using TCP and start using UDP for transport (QUIC).
Non-standardized or Custom HTTP headers
There are several headers that Skip2 uses for tracking data as it flows through our network to provide troubleshooting capabilities.
X-S2-Edge
The value of this contains the name of the edge node that served the request.
Example: us-chi-51.pop.skip2.net
```X-S2-Trace``
The value of this contains the Open Telemetry trace ID for the request.
Example: 5b8aa5a2d2c872e8321cf37308d69df2
X-S2-Proto
The value of this is the agreed-upon HTTP procol version.
Example: HTTP/3.0
X-S2-Cipher
The value of this is the agreed-upon TLS cipher.
Example: TLS_AES_128_GCM_SHA256
X-S2-Via
Example: .