Fieldmark Documentation
Technical notes / Open reference
Contents ▾
CHAPTER 01 / ORIENTATION

Begin with a request.

Every page load is made of requests. Learning the basic shape of one helps explain the rest.

The round trip

A client selects a resource identifier, chooses a method and sends a request. The server returns a status and, when appropriate, a representation such as HTML, JSON or an image.

The same URL can legitimately behave differently for GET and HEAD. A response may also depend on explicit request headers, cache state or content negotiation.

Inspect before guessing

Start by examining the status line, Content-Type, Location and caching headers. A rendered browser page often hides redirect hops and conditional requests.

curl -I https://example.org/
curl -v https://example.org/guide/

A useful reading order

Read the core concepts, then the request walkthrough. Once responses make sense, move to cache validation and the worked examples.

Additional reference chapters

Conditional requests and the 304 response · Editorial team · . A reference for If-None-Match, If-Modified-Since and validating cached HTTP representations.

When one resource has several representations · Editorial team · . A guide to Accept, Vary and the cache implications of HTTP content negotiation.

Following redirects without losing the method · Editorial team · . A reference for redirect status codes, Location and testing multi-hop HTTP requests.