HTTP Request
↔ (process) to send/declare action to perform on Web Resource
aka HTTP-Verb, Request, Requests, HTTP-Requests, HTTP-Reqs, Reqs
HTTP Request defined by HTTP specification
CRUD
ops of HTTP Request
GET
HEAD
Request to test response (w/o respond body)
POST
to send data & Request to create new Resource on server
PUT
to Request update via entire object & Request create/update to existing Resource
PATCH
to Request update via part of object & Request update to existing Resource
DELETE
to send Request to delete Resource on Server
CONNECT
Request for Proxy to tunnel TCP connection to outlet
OPTIONS
Request to config comms prefs for target Resource
TRACE
Request to debug message loop-back to test Resource path
start line
HTTP Method + Request Target + HTTP version
HTTP Request Header
HTTP Request Body
References
CONNECT
↔ Request for Proxy to tunnel TCP connection to outletCreate
↔ (ability for Client) to create data ⇒POST
HTTP RequestRead
↔ (ability for Client_) _to read data ⇒GET
HTTP RequestUpdate
↔ (ability for Client) to edit/update data ⇒PUT
||PATCH
HTTP RequestDestroy
↔ (ability for Client) to delete/destroy data ⇒DELETE
HTTP Requestrequest()
↔http
Static Method to make a HTTP RequestPOST
↔ to send data & Request to create new Resource on serverPUT
↔ to Request update via entire object & Request create/update to existing ResourceTRACE
↔ Request to debug message loop-back to test Resource pathCollections
↔ to save/organize Requestsapp.post()
↔ to sendPOST
Requestuses [**_
HTTP Verb_**](http-request)
↔ REST use HTTP Request to perform actions & NOT specify action inside URLuses [**_
HTTP Verb_**](http-request)
↔ REST use HTTP Request to perform actions & NOT specify action inside URLPATCH
↔ to Request update via part of object & Request update to existing Resource[
CRUD](crud) ops of [**_
HTTP Request_**](http-request)
↔POST
GET
PUT
PATCH
DELETE
Polling
↔ (process) to sendGET
Request to check Server State changeRequest Timeout
↔ (process) to let Polling Request timeout when no Server State changeNGINX
↔ Backend Server gateway to Web, Reverse Proxy to handle Requests/Cache/load balanceRequest-Response model
↔ (model) to communicate between client-server via HTTP RequestsForward Proxy
↔ Proxy sit in front of Client as gateway to forward Reqs to InternetHTTP Caching
↔ (process) to store HTTP Response to reuse for subsequent ReqsHard Nav
↔ (feat) on nav, invalid HTTP Cache & Reqs Backend to re-render change in segmentFederated Search
↔ to send multiple searches in a single HTTP Request, to reduce RTT LatencyHTTP Flood
↔ DDoS spam lots of concurrent HTTP Reqs to overload server - camoflauge attacks by varying UA & IPsParallel Data Fetch
↔ to init Reqs ASAP & load Concurrently