How a web server works
A web server waits on a port for requests and sends responses. Handlers, http.HandleFunc and ListenAndServe, and seeing the request in the browser.
Try it
- HTTP request builder – Choose a method, a path and a body, and see the exact request text and the response a pretend Go server would send.
Transcript
A web server is a program that waits for requests and sends back responses. It is the kitchen from the internet lessons, now written in Go. It listens on a port, which is a numbered door on the computer.
When a request arrives, the server runs a handler: a function that receives the request and writes the response.
In Go, http dot HandleFunc connects a path to a handler. Then http dot ListenAndServe starts the server on a port, like colon eight zero eight zero.
Run the program, and open localhost colon eight zero eight zero in the browser. The Network tab in DevTools shows the same request and response that your Go program handled.
Remember: a server listens on a port, a handler answers each request, and localhost is your own computer.
More in this series
1:3041Routes, methods and status codes
A route connects a path and a method to a handler. GET, POST and DELETE, the status codes 200, 201, 400, 404 and 500, and how Go answers 404.
1:1942A JSON API in Go
An API returns data instead of pages. A Go struct becomes JSON with struct tags, a handler writes it with json.NewEncoder, and the page loads it with fetch.
1:2143POST and saving data
A POST request carries data in its body. Decode the JSON into a struct, keep it in a slice (lost on restart), and protect the shared slice with a mutex.
1:1744What is a database?
A database keeps data in tables of rows and columns, like a strict spreadsheet. Primary keys, why data in a file survives a restart, and asking questions with SQL.
1:0145SQL basics
SQL is the language for asking a database: CREATE TABLE, INSERT INTO, SELECT with WHERE and ORDER BY, then UPDATE and DELETE (always with WHERE).
1:1446Go and databases
Go talks to a SQLite database with database/sql and a driver. Exec changes data, Query reads rows into structs, and ? placeholders pass values safely.
1:2047Input, validation and safety
Never trust a request: validate empty and too-long values and answer 400, why ? placeholders stop SQL injection, and keep secrets and database files out of Git.