HTTP

The protocol web browsers and web servers use to send requests and responses.

In more detail

HTTP stands for hypertext transfer protocol. A client sends a request naming a method, such as GET, and a path; the server replies with a status code, headers and a body. HTTPS is HTTP carried over an encrypted TLS connection.

Examples

In AWS: The protocol web browsers and web services use to send requests and responses, such as GET /health.
The last lesson recommends HTTP rather than Kafka when a caller needs one immediate reply.
APIs, cookies, Server-Sent Events and the WebSocket handshake all ride on HTTP.
http.NewRequestWithContext(ctx, http.MethodGet, url, nil)
HTTP stands for Hypertext Transfer Protocol; HTTPS is the same protocol carried inside a TLS session. A request has a method, a target, headers and sometimes a body; the response has a status code, headers and an optional body. HTTP evidence only exists once the transport connection works, so check lower layers first.
HTTPS adds confidentiality, integrity and server authentication; it does not fix application flaws or protect hops after TLS termination.
Next.js streams pages over HTTP, and Server Actions are HTTP POST requests under the hood.
Prometheus scrapes over plain HTTP; OTLP can use HTTP on port 4318.
A CGI script prints a Content-type header, a blank line, then the HTML body of the response.
fetch sends an HTTP request from the browser and returns a Promise of the response.
fetch sends an HTTP request and returns a Promise of the HTTP response.
TAXII runs over HTTPS; beacons often hide in ordinary HTTPS traffic.
In this course: A real payment gateway client would make HTTP calls with a secret key and a timeout, which is exactly why tests replace it with a double. HTTPS is the same protocol encrypted, and a real gateway client would always use it.

Related terms

Taught in

References

Certification courses