liveBook · Manning

HTTP GET

As explained in Grokking Software Architecture

An HTTP method that requests a representation of a resource without requesting a state change.

GET requests a resource representation at a URL. In REST, GET /products/123 returns the product, usually with more fields than a caller may need. Query parameters can filter fields, such as ?fields=name,price. section 6.4.1

A safe repeat

GET /orders/1 reads an order. Repeating the request does not change it, so GET is idempotent. section 6.4.1

Listing 6.1 REST Response
// REST Response: #A
{
  "id": "123",
  "name": "Salt & Vinegar Chips",
  "price": 1.50,
  "calories": 250,
  "ingredients": [ "Potatoes", "Oil", "Salt"... ],
  "manufacturer": { "name": "SnackCorp", "address": "123 Food Lane" }
}

See a REST response with fields such as name, price, calories, and ingredients—a concrete example of receiving more than a narrow request may need. section 6.4.1

How Grokking Software Architecture covers it

How deep it goes
Defines GET through resource retrieval and idempotency, with examples but no detailed request-syntax treatment.
Examples
Uses GET /products/123, GET /orders/1, and a product response containing more fields than a price lookup needs.
What you can do after
Understand GET as a repeatable read that does not change the resource.
How it connects
Connects GET to REST, idempotency, cacheability, and over-fetching.

Also explained in

Compare how 17 books explain HTTP GET →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.