Skip to main content
Apply for a Cheap Website
Website explainer · 1:47

GET and POST Explained: Two Common HTTP Request Methods

Why do website requests have names such as GET and POST? The method communicates the kind of operation being requested.

Jersey Web video: GET or POST?

1:47 · No narration: the video shows each step as text on screen, and every step is written out below, with buttons that jump the video to it.

Download the on-screen text track (VTT)

The six points in the video

This is a silent video. The headings, explanations and labels below reproduce the information on screen.

  1. Step 1: GET retrieves information

    A GET request asks for a representation of a resource.

    On-screen labels: Resource address; Requested information; Returned representation.

  2. Step 2: GET should not change state

    The intended operation is retrieval, rather than a requested change.

    On-screen labels: Read operation; Expected behaviour; Suitable endpoint.

  3. Step 3: POST submits information

    A POST request sends data for the target resource to process.

    On-screen labels: Submitted data; Target resource; Processing action.

  4. Step 4: POST can have side effects

    Processing may create a record or cause another change.

    On-screen labels: Server processing; Possible state change; Recorded result.

  5. Step 5: The method is not encryption

    The GET or POST label does not itself protect the connection.

    On-screen labels: Request method; Connection protection; Separate concerns.

  6. Step 6: Check the result as well

    A submitted request still needs the expected response and outcome.

    On-screen labels: Request details; Response status; Intended result.

A practical check for your business

Use the API or application documentation to choose the supported method. Check where values are sent and how the server responds rather than assuming the method name alone protects the request.

Sources and further detail

Common questions

Why do website requests have names such as GET and POST?

The method communicates the kind of operation being requested. Check the intended operation and what the server actually returned.

Go further

Guide Read the practical guide More context for planning and maintaining your business website. 5 min read → Jargon Buster HTTP method explained Read the related Jargon Buster explanation. Read the explanation →

Check the intended operation and what the server actually returned.

Tell Jersey Web what your website needs to do and which part you want help with.

Talk to Jersey Web →

More video tips

All 205 videos →
Length 1:47 Website foundations

JSON Explained: A Common Format for Exchanging Website Data

JSON, explained.
Length 1:47 Website foundations

HTTP Headers Explained: Information Sent Alongside Website Requests and Responses

HTTP headers, explained.
Length 1:47 Website foundations

CORS Explained: Browser Rules for Reading Responses from Another Origin

CORS, explained.