WEBVTT

00:00:00.000 --> 00:00:06.000
Why do website requests have names such as GET and POST?

00:00:06.000 --> 00:00:13.000
The method communicates the kind of operation being requested.

00:00:13.000 --> 00:00:18.000
Read the method together with the resource and response.
6 GET and POST basics.

00:00:18.000 --> 00:00:30.000
GET retrieves information
A GET request asks for a representation of a resource.
Resource address · Requested information · Returned representation

00:00:30.000 --> 00:00:42.000
GET should not change state
The intended operation is retrieval, rather than a requested change.
Read operation · Expected behaviour · Suitable endpoint

00:00:42.000 --> 00:00:54.000
POST submits information
A POST request sends data for the target resource to process.
Submitted data · Target resource · Processing action

00:00:54.000 --> 00:01:06.000
POST can have side effects
Processing may create a record or cause another change.
Server processing · Possible state change · Recorded result

00:01:06.000 --> 00:01:18.000
The method is not encryption
The GET or POST label does not itself protect the connection.
Request method · Connection protection · Separate concerns

00:01:18.000 --> 00:01:30.000
Check the result as well
A submitted request still needs the expected response and outcome.
Request details · Response status · Intended result

00:01:30.000 --> 00:01:39.000
Your checklist
GET retrieves information · GET should not change state · POST submits information · POST can have side effects · The method is not encryption · Check the result as well

00:01:39.000 --> 00:01:47.000
Check the intended operation and what the server actually returned.
jerseyweb.je