Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21c33d48c683a24

Jump to content

// Workers AI · dad joke modeWhat did the variant object say? I'm a little different.

From Wikipedia, the free encyclopedia

Variant objects in the context of HTTP are objects served by an Origin Content Server in a type of transmitted data variation (i.e. uncompressed, compressed, different languages, etc.).

HTTP/1.1 (1997–1999)[1][2] introduces Content/Accept headers. These are used in HTTP requests and responses to state which variant the data is presented in.[citation needed]

Example scenario

[edit]

Client:

GET /encoded_data.html HTTP/1.1
Host: www.example.com
Accept-Encoding: gzip

Server:

HTTP/1.1 200 OK 
Server: http-example-server
Content-Length: 23
Content-Encoding: gzip

<23 bytes of gzip compressed data>

See also

[edit]

References

[edit]
  1. Fielding, Roy T.; Gettys, Jim; Mogul, Jeffrey C.; Nielsen, Henrik Frystyk; Berners-Lee, Tim (January 1997). Hypertext Transfer Protocol -- HTTP/1.1. IETF. doi:10.17487/RFC2068. RFC 2068. Retrieved 2009-10-24.
  2. Fielding, Roy T.; Gettys, James; Mogul, Jeffrey C.; Nielsen, Henrik Frystyk; Masinter, Larry; Leach, Paul J.; Berners-Lee, Tim (June 1999). Hypertext Transfer Protocol -- HTTP/1.1. IETF. doi:10.17487/RFC2616. RFC 2616. Retrieved 2009-10-24.
[edit]