Notice
Recent Posts
Recent Comments
Link
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |
Tags
- docker
- 리눅스
- 1일1문장
- 끈기
- Sequence
- Linux
- Andrew Ng
- multer
- 우선순위
- ES6
- HTTP
- nodejs
- scope
- 러닝자바스크립트
- 데이터전송
- 클로저
- Til
- 자바스크립트
- 자료구조
- 객체
- Machine Learning
- React
- javascript
- 스파르타코딩클럽
- CSS
- 회고
- reactnative
- 개발공부
- coursera
- NextJS
Archives
- Today
- Total
해나아부지 개발일지
what happen to input url on the browser? 본문
- The browser first parses the URL to identify the protocol (e.g. HTTP, HTTPS), the domain name (e.g. www.example.com), and the path to the resource (e.g. /index.html).
- Next, the browser checks its cache to see if it has a cached copy of the resource. If it does, and the cached copy is still valid, it will be used instead of making a new request to the server.
- If the resource is not cached or the cached copy is not valid, the browser will send a request to the server identified in the URL, asking for the resource specified in the path.
- The server will then process the request and send back a response containing the requested resource, typically in the form of HTML, CSS, JavaScript, images, or other content.
- The browser then receives the response and begins rendering the content according to the instructions in the HTML and CSS.
- If the response contains any embedded resources (such as images or JavaScript files), the browser will send additional requests for those resources and repeat the above steps to retrieve and render them.
- Finally, once all resources have been retrieved and rendered, the website will be displayed in the browser for you to interact with.
'Developers > Coding Question' 카테고리의 다른 글
네트워크 환경에서 데이터가 오가는 과정을 이해하는 것과 프론트엔드 업무 연관성 (0) | 2023.03.07 |
---|---|
네트워크 환경에서 데이터가 오가는 과정을 이해하는 것이 왜 중요한 이유 (0) | 2023.03.07 |
UTF-8 (0) | 2020.10.08 |
비대칭 암호화란 (0) | 2020.09.03 |
Cashe란? (0) | 2020.08.07 |
Comments