-
Notifications
You must be signed in to change notification settings - Fork 70
A request journey
Song Zheng edited this page Mar 5, 2022
·
22 revisions
This document's goal is to help you understand the inner workings of the codebase by explaining what happens when a request is sent to https://c0d3.com.
- When you type https://c0d3.com/ (notice how
www
is not in the url) in your browser and hit enter, DNS resolution will resolve to our Digital Ocean application server, the same one that hosts our curriculum's demo apps. The request will be sent there- Our application server's caprover application has an nginx redirection (if you login to caprover, the redirection application is called redirect-to-www) to send back a
301
HTTP response code for https://www.c0d3.com.
- Our application server's caprover application has an nginx redirection (if you login to caprover, the redirection application is called redirect-to-www) to send back a
- Browser sends a request to https://www.c0d3.com (notice the
www
in the url). DNS resolution for this url will resolve to a server owned by Vercel, and the request will be sent to the vercel instance that hosts our application.