Videos / Web Dev

Episode 6 of 16 · Web development, end to end

HTTP and Express: what a request actually is

Chapters

1. Text on a socket0:00
2. The first line0:15
3. Headers, gap, then body0:30
4. The same shape back0:47
5. What a method promises1:03
6. The server forgets1:20
7. The first digit1:38
8. Three kinds of success1:53
9. Permanent, or just visiting2:09
10. The four hundreds2:25
11. The five hundreds2:43
12. The three that get misused3:01
13. The envelope, not the letter3:19
14. Where the body stops3:35
15. What a cache is told3:53
16. Asking without downloading4:09
17. A cookie is a header4:24
18. CORS is a browser rule4:42
19. One signature, repeated5:02
20. Order is the program5:18
21. Next makes it a chain5:34
22. Three things it can do5:50
23. After next is not later6:06
24. Routers nest the stack6:24
25. A route is a filter6:41
26. Params, query, strings6:58
27. The fall-through 4047:16
28. The body needs a parser7:33
29. Four arguments means error7:53
30. The async hole8:12
31. One lane at a time8:30
32. Frames and streams8:48
33. Headers get a table9:05
34. The blocking moved down9:22
35. QUIC, on top of UDP9:40
36. What did not change9:57
37. The whole thing10:15

HTTP and Express: what a request actually is. Open a connection to a web server, type a few lines of text, and press enter twice. That is a request. H T T P is not a mystery format. It is plain text with a shape, and the shape

Mark as watchedSaved in this browser only.