https://learn.staticvar.dev/courses/how-the-web-works/01-the-journey/Recent content in The journey of a request on Staticvar LearnHugo -- gohugo.ioen-ushttps://learn.staticvar.dev/courses/how-the-web-works/01-the-journey/01-a-url-is-a-plan/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/how-the-web-works/01-the-journey/01-a-url-is-a-plan/When you type an address into a browser, you are not simply naming a page. You are giving the browser a compact plan: how to communicate, where to go, and what to ask for. The parts of a URL Consider this address: https://learn.staticvar.dev/courses/web?mode=quick#dns Each part has a job: Part Example Meaning Scheme https The protocol and security expectations Host learn.staticvar.dev The named destination Path /courses/web The resource being requested Query mode=quick Optional inputs for the server Fragment dns A location within the returned page The fragment is special: browsers normally use it locally.https://learn.staticvar.dev/courses/how-the-web-works/01-the-journey/02-http-conversation/Mon, 01 Jan 0001 00:00:00 +0000https://learn.staticvar.dev/courses/how-the-web-works/01-the-journey/02-http-conversation/HTTP is the language browsers and web servers use to exchange messages. Its core pattern is deliberately simple: a client sends a request, and a server returns a response. A request has intent GET /courses/web HTTP/1.1 Host: learn.staticvar.dev Accept: text/html The method GET says what the client intends to do. The path identifies the resource. Headers add context such as the desired response format. A response reports an outcome HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Content-Length: 4280 <!