Inside a web browser, a document can point to another document using links.
A link is composed by a first part that determines the protocol and the server address, either through a domain name or an IP.
This part is not unique to HTTP, of course.
Then there’s the document part. Anything appended to the address part represents the document path.
For example, this document address is https://thevalleyofcode.com/the-web/2-hyperlinks:
httpsis the protocol.thevalleyofcode.comis the domain name that points to my server/the-web/2-hyperlinksis the document URL relative to the server root path.
The web server is responsible for interpreting the request and, once analyzed, serving the correct response.
Lessons in this unit:
| 0: | Introduction |
| 1: | The HTTP protocol |
| 2: | ▶︎ Hyperlinks |
| 3: | What is a Web server |
| 4: | What is a Web browser |
Are you intimidated by Git? Can’t figure out
merge vs rebase? Are you afraid of screwing up
something any time you have to do something in
Git? Do you rely on ChatGPT or random people’s
answer on StackOverflow to fix your problems?
Your coworkers are tired of explaining Git to
you all the time? Git is something we all need
to use, but few of us really master it. I
created this course to improve your Git (and
GitHub) knowledge at a radical level. Launching
May 21, 2024. Join the waiting list!